This blog is part of a series on Teams. For more articles, check back often.
Written: 25/08/2019 | Updated: N/A
There may be an app your Team frequently uses. For the purpose of this article lets take this app to be Microsoft Flow where the Team is repeatedly adding Flows between apps such as Forms and SharePoint and Twitter and Powerapps across multiple Teams. They could always add Flow as a Tab to a particular Team, but with the increasing amount of Teams this wouldn’t make much sense as the Team members would have to remember what Team, or – as is more likely – they are now adding Flow Tabs across multiple Teams which is littering Teams with Tabs which don’t necessarily need to be there.
Cue an app setup policy – which can ensure particular Team members see the app in the app bar (the dark bar on the left of the Teams client) by default when they start Teams.
WHY WOULD WE DO IT?
- To ensure an app appears in the left navigation upon startup
- To ensure easy access to an app which needs to be used frequently
- To speed up access to the required app
- Teams Licence
- Teams Service Administrator Role
Teams Licence will usually come in an Office/Microsoft 365 subscription. The user does not have to be a global admin, but the minimum requirement is to have a Teams Service Administrator role as this functionality is configured in the Teams Admin Centre
1.) Login to https://login.microsoftonline.com
2.) Select Admin
3.) Select Teams
4.) Select Teams Apps then Setup Policies
5.) Select Add
6.) Name the Custom App Policy (Here called My Team) and add the required App (Here Flow) to the list of apps via Add Apps. Sort and remove any apps not required. Select save once completed and the custom policy should now be displayed under the App Setup policies
7.) Go to Users. Select the Display Name of the chosen user (Here Lidia Holloway)
8.) Select Policies then Edit (next to assigned policies)
8.) Change the app setup policy to the one just created (here My Team) and then select apply
Our work here is done. Repeat the change in the policy for as many members of the Team who need it. The policy change can take up to 48 hours to propagate.
Have the user periodically log in to check the change has taken place.
- If the change is to implemented across the whole organisation it is recommended to change the Global Org Wide Default as opposed to create a custom policy
- Custom apps can be uploaded and used in app setup policies per this article