Manage your apps in the Microsoft Teams admin center

As an admin, the Manage apps page in the Microsoft Teams admin center is where you view and manage all Teams apps in your organization's app catalog. Here, you can see the org-level status and properties of apps, upload new custom apps to your tenant app catalog, block or allow apps at the org level, and manage org-wide app settings.

The Manage apps page gives you a view into all available apps in your tenant catalog, providing you with the information you need to decide which apps to allow or block across your organization. You can then use app permission policies, app setup policies, and custom app policies and settings to configure the app experience for specific users in your organization.

In the left navigation of the Microsoft Teams admin center, go to Teams apps > Manage apps. You must be a global admin or Teams service admin to access the page.

View apps in your tenant app catalog

You can view every app in your tenant app catalog including the following information about each app.

Screenshot of the Managed apps page

  • Name: The app name. Click the app name to see more information about the app. This includes a description of the app, whether it's allowed or blocked, version, categories that apply to the app, certification status, supported capabilities, and app ID. Here's an example:
    Screenshot of the apps details page for an app
  • Certification: If the app has gone through certification, you'll see either Microsoft 365 certified or Publisher attestation. Click the link to view certification details for the app. If you see "--", we don't have certification information for the app. To learn more about certified apps in Teams, read Microsoft 365 App Certification program.
  • Categories: Categories that apply to the app.
  • App status: Status of the app at the org level, which can be one of the following:
    • Allowed: The app is available for all users in your organization.
    • Blocked: The app is blocked and not available for any users in your organization.
      It's important to know that this column represents the allowed and blocked status of apps that were formerly on the Org-wide settings pane. You now view, block, and allow apps at the org-wide on the Manage apps page.
  • Version: App version.

To see the information that you want in the table, click Edit Column in the upper-right corner to add or remove columns to the table.

Upload a new app

You can use your app catalog to test and distribute line-of-business applications that are built specifically for your organization. A Teams app package is created by using Teams App Studio. When you have the app package, you can add it to the your app catalog. While all users in your organization can view the app catalog, only global admins and Teams service admins can publish and manage it.

To upload a new custom app to your tenant app catalog, click Upload new app to upload your app package in .zip format. The app isn't highlighted after it's uploaded so you'll need to search your app catalog to find it.

To update an app after it's uploaded, in the list of apps on the Manage apps page, click the app name, and then click Update. Doing this replaces the existing app in your app catalog and all app permission policies and app setup policies remain enforced for the updated app.

To learn more, see Manage your line-of-business apps in Teams.

Allow and block apps

The Manage apps page is where you allow or block individual apps at the org level. It shows every available app and its current org-level app status. (Blocking and allowing apps at the org level has moved from the Org-wide app settings pane to here.)

To allow or block an app, select it, and then click Allow or Block. When you block an app, all interactions with that app are disabled and the app doesn't appear in Teams for any users in your organization.

When you block or allow an app on the Manage apps page, that app is blocked or allowed for all users in your organization. When you block or allow an app in a Teams app permission policy, it's blocked or allowed for users who are assigned that policy. For a user to be able to install and interact with any app, you must allow the app at the org level on the Manage apps page and in the app permission policy that's assigned to the user.

Manage org-wide app settings

Use org-wide app settings to control whether users can install third-party apps and whether users can upload or interact with custom apps in your organization. Org-wide app settings govern the behavior for all users and override any other app permission policies assigned to users. You can use them to control malicious or problematic apps.

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

    Screenshot of org-wide app settings

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

    • Allow third-party apps in Teams: 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. For apps that you allowed, the status shows as Allowed but disabled org-wide.

      Note

      In a Microsoft 365 Government - GCC deployment of Teams, the Allow third-party apps in Teams setting is off by default.

      When Allow third-party apps in Teams is off, outgoing webhooks are disabled, which means that users can't create them. When this setting is on, outgoing webhooks are enabled for all users regardless of whether the setting is on or off in the users' app permission policy.

    • 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.

  3. 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.

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