PWA Provisioning Strategies

If you order your first project online subscription, a project web app is automatically created in the background. The instance gets the following url: https://<yourtenant>.sharepoint.com/sites/pwa and inherits the language of your O365 tenant. This PWA is also linked to the project online tile, which everyone with a valid subscription can see. But, what if the PWA has the wrong language? Or the wrong URL? What if I want to enable the users an easy access vehicle to multiple PWAs (e.g. test, dev environment)? You‘ll get the answers in this blog post.

Change the primary language and url of the default PWA

There‘s no way to change the primary language and url of the default PWA other than deleting and recreating the PWA. Why? Because all the standard field like rbs, department, project team, etc. are firstly created in the primary language of the O365 tenant.

What happens with the project online tile (linked to the /sites/pwa url), if I delete the default PWA?

Nothing! It is still linked to this url. This cannot be changed. The good news: You can create a new PWA or SharePoint site collection with the same url with your desired language settings. The deleted PWA will still be in the recycle bin, due to the grace period, so you may get a warning during the recreation that the old one is going to be irrecoverable deleted.

What access strategies exist, when I have more than one PWA?

  1. Create a custom tile for each PWA
    This is suitable for tenants where most of the users are using Project Online and the number of system environments is limited.Open the O365 admin center and navigate to the Organization profile (-> Settings). Go to the section add custom tiles for your organization
    Just enter the tile name, url, description and image url for the tile. The image should be 60×60 pixels and be available to everyone in your organization. You can put it in a library on a SharePoint site and generate an anonymous guest link to use as the URL. 
    The tile will appear in the section new. Every user, even the administrator, needs to pin the tile manually to home. 
  2. Create a PWA hub with a SharePoint team site:
    This method is awesome, if you have more than just one PWA and if you want to enable access with the default project online tile. Delete the default PWA and create a private SharePoint site collection (e.g. a team site) with the url which is linked to the project online tile. 
    Next go to the site contents of your new PWA hub and add the app promoted links. Give it a name, e.g. PWA hub. Once you’ve created it, add an item for each PWA. Optional: Configure permissions on an item level, to define who will be able to see which PWA url.Edit the look & feel of the pwa hub by inserting your promoted links webpart to the homepage.
    My final page looks like this:
    Last but not least share the site with everyone without sending an email. The users can access the PWA hub by clicking on the defauft project online tile.
Facebooktwittergoogle_plusredditpinterestlinkedinmailby feather

Leave a Comment

Your email address will not be published. Required fields are marked *