Developer Portal for Teams

Developer Portal for Teams (previously known as App Studio) is the primary tool for configuring, distributing, and managing your Microsoft Teams apps. With Developer Portal, you can collaborate with colleagues on your app, set up runtime environments, and much more.

Screenshot shows the home page of Developer Portal.

Note

  • Developer Portal for Government Community Cloud (GCC) is supported only as an app in Teams and not as a standalone website.
  • Developer Portal isn't available for GCC-High and Department of Defense (DOD) tenants. However, you can use a regular tenant to build an app in Developer Portal, download the app, and upload the app using Microsoft Graph to a national cloud. For more information, see national cloud deployments.

Register an app

Developer Portal provides the following ways to register a Teams app:

Create and register a brand new app

Developer Portal allows you to create a brand new app:

  1. Sign in to Developer Portal and select Apps from the left pane.

    Screenshot shows the home page of Developer Portal with the Apps option highlighted in red.

  2. Select + New app.

    Screenshot shows how to create a brand new app in Developer Portal.

  3. Enter app name and select Add.

    The screenshot shows how to create a brand new app in Developer Portal.

Now you've successfully created a brand new app and you can see all the basic information of the new app.

Screenshot shows the basic information of the app you created in Developer Portal.

Import an existing app

Follow the steps to import and manage your existing app in Developer Portal:

  1. In Developer Portal, select Apps from the left pane.

  2. Select Import app.

    Screenshot shows how to import your existing app in Developer Portal to manage your apps.

  3. Select the app manifest file, and then select Open.

    Note

    You can receive an error message such as Provided add-in package was not understood. Ensure that the file being submitted is a valid Office add-in package, if there are nested folders or missing files in the app package folder.

  4. Select Import.

    • Developer Portal creates a unique app ID and locks the ID for your registered Teams app. You can’t edit or provide an ID of your choice, which prevents to have duplicate app IDs for multiple apps.

    • If you create an app using the Microsoft Teams Toolkit for Visual Studio Code, you can manage your app in Developer Portal.

    • You can import an existing app to Developer Portal that was created in App Studio. If an app in your tenant doesn't have an owner, the Teams Tenant admin or Global admin can take ownership of the app from Teams Developer Portal.

      Screenshot shows an example of a tenant admin taking ownership of an app in Teams Developer Portal.

Steps to import a published app that's not registered in Developer Portal

You might have published apps in Teams Store that wasn't registered in Developer Portal. If you want to monitor app analytics or validate your app, you must import your app into Developer Portal. While importing your published app, you might face the following error:

Screenshot shows an example of error message when you import an existing app in Teams Developer Portal.

To resolve this error, we recommend that you raise a support ticket to Microsoft with the following details:

  • App ID
  • Tenant ID
  • Your email ID
  • Screenshot of the email from Partner Center when the app was published.

This information is required to verify the app owner's identity, who raises the ticket and to allow them to import an app.

Changelog for Developer Portal

Changelog for Developer Portal allows you to stay engaged with the latest updates in Teams. You can view the updates about features, recent changes in APIs, and important bug fixes.

To view Changelog, sign in to Developer Portal and select Changelog from the left pane.

Screenshot shows the Changelog in the Developer Portal highlighted in red.

The updates for Changelog in Developer Portal are categorized based on the following:

  • Added: Updates on a service or feature that's a new feature or capability.
  • Changed: Updates on a service or API that's modified.
  • Removed: Updates on a service or API that's removed and may be replaced with a new and updated service.
  • Fixed: Updates on a service or API that was previously identified as a high-priority or breaking-change issue that's fixed or mitigated.
  • Deprecated: Updates on a service or API at the end of its life and deprecated.
  • Security: Updates on important and critical security patch.

Next step

See also