How to have a Teams Admin push the Chime V5 app to pilot groups or org-wide

If you are in the process of onboarding, please make sure you have gone through and considered or completed these two steps:

Authorize Chime V5 Teams App in Microsoft Teams Admin Center >>

Steps to Customize (Apply Branding) Teams App in Teams Admin >>


Once you are ready to start deploying the Chime V5 app either for your small pilot testing or when pushing to it to your organization, this guide will help to lay out the steps to follow to get the app pushed as well as cover some of the customization options to consider before pushing to groups of users.


Teams Admin configures user group permissions

Navigate to Permission Policies in the Teams Admin Center. You will now need to configure policies to allow the Chime V5 Teams app to only to be accessible for the small group that is to take part in the small pilot group. Typically, this is a new custom App Permission policy that you will create and name to indicate it is for the Chime pilot testing.

Additionally, you may want to automatically install and pin the Chime V5 app in the Teams client for users in the pilot. To do this you would want to update the app setup policies in the Setup Policies tab of Teams Admin Center and create a new policy for the Chime V5 pilot.

Here is some additional documentation from Microsoft on managing permission policies and setup policies:

Use app permission policies to control user access to apps

Use app setup policies to pin and auto install apps for users


Once you are happy with the testing in a small POC group, you will want to test adding additional members to the pilot group. In this stage you will want to test out applying the pilot policies to a broader set of users and ensure that you can properly scale up the app to more users.

Here is some Microsoft documentation on best practices for assigning policies:

Assign policies to users and groups

Teams Admin pushes Chime V5 app org-wide or to specific user groups

At this point you will want to know if Chime V5 is an app that you will want to add into the Global (Org-wide default) permission group, or if only certain user groups are going to have access to use the app, and if you want the app to be installed and pinned for all users in your organization. When you are done with POC testing, push the app to all end users who will be supported by Chime V5.

Before pushing the app to the whole tenant, here are a few things to consider for the end user experience:

  • Users may have the app install and pinned to the left side of their Teams client. If there are any branding updates you want to make for this app icon or name, it is better to make them before pushing the app.

  • All users will receive a message from the app when it is first installed for them. To customize this message, navigate to Admin > Chime Settings > Tenant Settings > Chat Commands and Events and update the adaptive card for Guest Install Welcome Message

Previous
Previous

Guide for Creating Links in FAQ Articles and Tips to Make Sure They Open in Teams Correctly

Next
Next

Graph API permission needed to enable Azure AD/Entra login for the Chime V5 web application