Overview of app management and governance in Teams admin center

You manage apps for your organization in Teams apps page in the Teams admin center portal. Use the Manage apps page to view and manage all Teams apps in your organization's app catalog, cater to prominent use cases for app management, define access to apps using policies, and more.

Screenshot of the Manage apps page.

To manage apps, you use policies to control permissions for users, installation of apps, and upload of custom apps created within your organization. To understand policies, see Overview of app policies.

To use Teams admin center, you must have a Global Admin or Teams Administrator role. For details, see Teams administrator roles and Microsoft 365 administrator roles.

Note

The Manage apps page isn't available in Microsoft 365 Government Community Cloud High (GCCH) or Department of Defense (DoD) deployments of Teams.

During the creation of an app, the developers create and add an app ID to the manifest file. You can view this external app ID on the Manage apps page after you enable the column External app ID from the column settings. You can also view it on the app details page of a custom app. The ID is applicable for custom apps only.

App management use cases and the available interfaces

The options to accomplish most of app management use cases are available in Teams admin center. In addition, some options are available in other portals or different pages in the Teams admin center.

App management tasks that are supported in admin center are in the table below.

App management use cases Link to the interface Documentation
Control which apps are available to users in your organization by allowing and blocking apps. You can also upload and approve custom apps. After managing apps on this page, you can use app permission and app setup policies to configure what apps are available for specific users in your organization's app store. Manage apps in Teams admin center Current article
App permission policies control what apps you want to make available to Teams users in your organization. You can use the Global (Org-wide) default policy and customize it, or you can create one or more policies to meet the needs of your organization. Permission policies Manage app permission policies
App setup policies control how apps are made available to a user with the Teams app. Use the Global (Org-wide default) policy and customize it or create custom policies and assign them to a set of users. Setup policies Manage app setup policies
You can develop and upload custom apps as app packages and make them available in your organization's app store. Org-wide app settings in Manage apps Manage custom app policies
You can customize the Teams app store with your organization's logo, custom background, or color. Customize store Customize your organization's app store
The Teams app usage report provides information about which apps in use, active users, and other app usage information. Usage reports Teams app usage report
Your users can add apps when they host meetings or chats with guests. They can also use apps shared by guests when they join meetings or chats hosted externally. The data policies of the hosting user's organization, and the data sharing practices of any third-party apps shared by that user's organization, are applied. External access App behavior depending on types of users
With guest access, you can provide access to applications and other Teams functionality to people outside your organization, while maintaining control over your corporate data. Guest access Guest access in Teams
Teams update policies are used to manage Teams and Office preview users that can see pre-release or preview features in the Teams app. Teams update policies Teams public preview

App management tasks that are supported on other portals are in the table below.

App management use cases Link to the interface Documentation
Manage licenses and subscriptions of third-party apps in Microsoft 365 admin center Microsoft 365 admin center Manage third-party app subscriptions
Audit Teams app events on Microsoft Purview compliance portal. Audit Teams activities
Applications can be granted permissions to your organization and its data by three methods: an admin consents to the application for all users, a user grants consent to the application, or an admin integrating an application and enabling self-service access or assigning users directly to the application. Verify the Graph permissions for apps. Verify the permissions that users provided or that the admins delegated. Azure AD portal Review permissions granted to applications

Allow and block apps

As an admin, you control access to all types of apps that are used across all context by all your users. Teams provides granular controls to configure access for each app and for each user.

To allow an app, all the following settings must be done. To block an app, block it via any one of the following settings.

  • Org-wide app settings: Use this setting to allow use of apps in your org. You decide which specific apps are used.
  • Allow an individual app: Use this setting to allow a specific app in your org. You decide which users can use the app.
  • App permission policy: Use policies to allow all or allow specific users to use an app. You decide access on a per-user and per-app basis.

The Manage apps page is where you allow or block individual apps at the org level. The page displays all the available app and their current org-level app status. To allow or block an app, follow these steps:

  1. Sign in to the Teams admin center and access Teams apps > Manage apps
  2. Locate an app and select it.
  3. Select Allow or Block option.

To allow an app for specific users, see app permission policies.

Manage org-wide app settings

Use org-wide app settings to control whether users with an F license get the tailored frontline app experience, whether users can install third-party apps, and whether users can upload or interact with custom apps in your organization.

Note

To learn how to use org-wide app settings in Microsoft 365 Government - Government Community Cloud High GCCH and Department of Defense (DoD) deployments of Teams, see Manage app permission policies in Teams.

  1. On Manage apps page, select Org-wide app settings. You can then configure the settings you want in the pane.

    Screenshot of the Org-wide app settings pane on the Manage apps page

  2. Under Tailored apps, turn off or turn on Show tailored apps. When this setting is on, users with an F license get the tailored frontline app experience. This experience pins the most relevant apps in Teams for frontline workers. To learn more, see Tailor Teams apps for your frontline workers.

    This feature is available for F licenses. Other license types will be supported in the future.

  3. Under Third-party apps, turn off or turn on these settings to control access to third-party apps:

    • Allow third-party apps: This controls whether users can use third-party apps. If you turn off this setting, your users won't be able to install or use any third-party apps and the app status of these apps is displayed as Blocked org-wide in the table.

      Note

      When Allow third-party apps is off, outgoing webhooks are still enabled for all users, but you can control them at the user level by allowing or blocking the Outgoing Webhook app through app permission policies. Note that if you have existing app permission policies for Microsoft apps that use the Allow specific apps and block all others setting, and you want to enable outgoing webhooks for users, add the Outgoing Webhook app to the list.

      Note

      Teams users can add apps when they host meetings or chats with people from other organizations. They can also use apps shared by people in other organizations when they join meetings or chats hosted by those organizations. The data policies of the hosting user's organization, as well as the data sharing practices of any third-party apps shared by that user's organization, are applied.

    • Allow any new third-party apps published to the store by default: This controls whether new third-party apps that are published to the Teams app store become automatically available in Teams. You can only set this option if you allow third-party apps.

  4. Under Custom apps, turn off or turn on Allow interaction with custom apps. This setting controls whether users can interact with custom apps. To learn more, see Manage custom app policies and settings in Teams.

  5. Select Save. The settings take effect after a few hours.

Manage org-wide app settings for Microsoft 365 Government

In a Microsoft 365 Government - GCC, GCCH and DoD deployment of Teams, all third-party apps are blocked by default. In GCCH and DOD clouds, the third-party apps aren't available. Additionally, in GCC, you 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 GCCH and DoD.

Use org-wide app settings to control whether users can install third-party apps. Org-wide app settings govern the behavior for all users and override any other app permission policies assigned to users.

For GCC clouds

  1. On the Teams Apps > Manage apps page, select Org-wide app settings. You can then configure the settings you want in the panel.

    Screenshot that shows the Org-wide app settings in GCC.

  2. Under Third-party apps, turn off or turn on these settings to control access to third-party apps:

    • Allow third-party apps: This option controls whether users can use third-party apps. If you turn off this setting, your users won't be able to install or use any third-party apps. In a Microsoft 365 Government - GCCH and DoD deployment of Teams, this setting is off by default.
    • Allow any new third-party apps published to the store by default: This option controls whether new third-party apps that are published to the Teams app store become automatically available in Teams. You can only set this option if you allow third-party apps.
  3. Under Blocked apps, add the apps you want to block across your organization. In a Microsoft 365 Government - GCCH and DoD deployment of Teams, all third-party apps are added to this list by default. For any third-party app you want to allow in your organization, remove the app from this blocked apps list. When you block an app org-wide, the app is automatically blocked for all your users, regardless of whether it's allowed in any app permission policies.

  4. Select Save for org-wide app settings to take effect.

To allow third-party apps, either edit and use the global (Org-wide default) policy or create and assign an admin-created policy.

For GCCH and DoD clouds

  1. Sign in to the Teams admin center and access Teams Apps > Permission policies.

  2. Select Org-wide app settings. Under Blocked apps, add the apps you want to block across your organization. In a Microsoft 365 Government - GCCH and DoD deployment of Teams, all third-party apps are added to this list by default. When you block an app org-wide, the app is automatically blocked for all your users, regardless of whether it's allowed in any app permission policies.

    Screenshot of org-wide app settings in GCCH and DoD.

  3. Select Save for org-wide app settings to take effect.

Allow the apps that are blocked by the developers

When a developer publishes an app to the Teams store, some apps might need an admin to configure the app. The admins make the app available to the end-users when the app is set up.

For example, Contoso Electronics is an app developer that created a help desk app for Microsoft Teams. Contoso Electronics wants its customers to set up certain properties of the app so that when users interact with the app, it functions as expected. Before an admin allows the application, it will show as Blocked by publisher in the Teams admin center and is hidden from end-users by default. After following the publisher's guidance to set up the app, you can make it available to users by changing the status to Allowed.

Screenshot of blocked by publisher status in Teams admin center.

For information about how developers block an app by default, see enable apps to be blocked until an admin allows it.

Related article