Manage app permission policies in Microsoft Teams

As an admin, you can use app permission policies to control what apps are available to Microsoft Teams users in your organization. You can allow or block all apps or specific apps published by Microsoft, third-parties, and your organization. When you block an app, users who have the policy are unable to install it from the Teams app store. You must be a global admin or Teams service admin to manage these policies.

You manage app permission policies in the Microsoft Teams admin center. You can use the global (Org-wide default) policy or create and assign custom policies. Users in your organization will automatically get the global policy unless you create and assign a custom policy. After you edit or assign a policy, it can take a few hours for changes to take effect.

Screenshot of app permission policy

Note

Org-wide app settings override the global policy and any custom policies that you create and assign to users.

If your organization is already on Teams, the app settings you configured in Tenant-wide settings in the Microsoft 365 admin center are reflected in org-wide app settings on the Manage apps page. If you're new to Teams and just getting started, by default, all apps are allowed in the global policy. This includes apps published by Microsoft, third-parties, and your organization.

Say, for example, you want to block all third-party apps and allow specific apps from Microsoft for the HR team in your organization. First, you would go to the Manage apps page and make sure that the apps that you want to allow for the HR team are allowed at the org level. Then, create a custom policy named HR App Permission Policy, set it to block and allow the apps that you want, and assign it to users on the HR team.

Note

If you deployed Teams in a Microsoft 365 Government - GCC environment, see App permission policies for GCC to learn more about third-party app settings that are unique to GCC.

Create a custom app permission policy

If you want to control the apps that are available for different groups of users in your organization, create and assign one or more custom app permission policies. You can create and assign separate custom policies based on whether apps are published by Microsoft, third-parties, or your organization. It's important to know that after you create a custom policy, you can't change it if third-party apps are disabled in org-wide app settings.

  1. In the left navigation of the Microsoft Teams admin center, go to Teams apps > Permission policies.

  2. Click Add.
    Screenshot of new app permission policy

  3. Enter a name and description for the policy.

  4. Under Microsoft apps, Third-party apps, and Custom apps, select one of the following:

    • Allow all apps
    • Allow specific apps and block all others
    • Block specific apps and allow all others
    • Block all apps
  5. If you selected Allow specific apps and block others, add the apps that you want to allow:

    1. Select Allow apps.
    2. Search for the apps that you want to allow, and then click Add. The search results are filtered to the app publisher (Microsoft apps, Third-party apps, or Custom apps).
    3. When you've chosen the list of apps, click Allow.
  6. Similarly, if you selected Block specific apps and allow all others, search for and add the apps that you want to block, and then click Block.

  7. Click Save.

Edit an app permission policy

You can use the Microsoft Teams admin center to edit a policy, including the global policy and custom policies that you create.

  1. In the left navigation of the Microsoft Teams admin center, go to Teams apps > Permission policies.
  2. Select the policy by clicking to the left of the policy name, and then click Edit.
  3. From here, make the changes that you want. You can manage settings based on the app publisher and add and remove apps based on the allow/block setting.
  4. Click Save.

Assign a custom app permission policy to users

You can assign a policy directly to users, either individually or at scale through a batch assignment (if supported for the policy type), or to a group that the users are members of (if supported for the policy type).

To learn about the different ways that you can assign policies to users, see Assign policies to your users in Teams.

App permission policies for GCC

In a Microsoft 365 Government - GCC deployment of Teams, it's important to know the following about third-party app settings, which are unique to GCC.

In GCC, all third-party apps are blocked by default. Additionally, you'll see the following note about managing third-party apps on the app permission policies page in the Microsoft Teams admin center.

Screenshot of app permission policy in GCC

To enable a third-party app for a user or a set of users in your organization, do the following:

  1. In the left navigation of the Microsoft Teams admin center, go to Teams apps > Manage apps, and then in the list of apps, confirm that the third-party app that you want to allow for a set of users is set to Blocked at the org level.

  2. In the left navigation of the Microsoft Teams admin center, go to Teams apps > Permission policies, and then edit the global policy to block the third-party app. To do this:

    1. On the App permission policies page, click Global (Org-wide default), and then click Edit.
    2. Under Third-party apps, select Block specific apps and allow all others, add the app, and then click Save.

    Note

    It's important to do this before you go to the next step to allow the app at the org level. This is because if the third-party app isn't blocked in the global app permission policy, all users that the global policy applies to will be able to access the third-party app when you allow it at the org level.

  3. Allow the third-party app at the org level. To do this, in the left navigation, go to Teams apps > Manage apps. In the list of apps, click to the left of the app name to select the app, and then select Allow.

  4. Create a custom app permission policy to allow the app, and then assign the policy to the users you want.

FAQ

Working with app permission policies

What app interactions do permission policies affect?

Permission policies govern app usage by controlling installation, discovery, and interaction for end users. Admins can still manage apps in the Microsoft Teams admin center regardless of the permission policies assigned to them.

Can I control line of business (LOB) apps?

Yes, you can use app permission policies to control the rollout and distribution of custom (LOB) apps. You can create a custom policy or edit the global policy to allow or block custom apps based on the needs of your organization.

How do app permission policies relate to pinned apps and app setup policies?

You can use app setup policies together with app permission policies. Pre-pinned apps are selected from the set of enabled apps for a user. Additionally, if a user has an app permission policy that blocks an app in their app setup policy, that app won't appear in Teams.

Can I use app permission policies to restrict uploading custom apps?

You can use org-wide settings on the Manage apps page, or app setup policies to restrict uploading custom apps for your organization.

To restrict specific users from uploading custom apps, use custom app policies. To learn more, see Manage custom app policies and settings in Teams.

Does blocking an app apply to Teams mobile clients?

Yes, when you block an app, that app is blocked across all Teams clients.

User experience

What does a user experience when an app is blocked?

Users can't interact with a blocked app or its capabilities, such bots, tabs, and messaging extensions. In a shared context, such as a team or group chat, bots can still send messages to all participants of that context. Teams indicates to the user when an app is blocked.

For example, when an app is blocked, users can't do any of the following:

  • Add the app personally or to a chat or team
  • Send messages to the app’s bot
  • Perform button actions that send information back to the app, such as actionable messages
  • View the app’s tab
  • Set up connectors to receive notifications
  • Use the app’s messaging extension

The legacy portal allowed controlling apps at the organization level, which means when an app is blocked, it's blocked for all users in the organization. Blocking an app on the Manage apps page works exactly the same way.

For app permission policies assigned to specific users, if an app with bot or connector capability was allowed and then blocked, and if the app is then allowed only for some users in a shared context, members of a group chat or channel that don't have permission to that app can see the message history and messages that were posted by the bot or connector, but can't interact with it.

Admin settings for apps in Teams

Assign policies to your users in Teams