Extend Teams apps across Microsoft 365
With the latest releases of Microsoft Teams JavaScript client library (TeamsJS version 2.0.0 and later), app manifest (previously called Teams app manifest) (version 1.13 and later), and Teams Toolkit, you can build and update Teams apps to run in other high-usage Microsoft 365 products and publish them to the Microsoft commercial marketplace (Microsoft AppSource) or your organization's private app store.
Extending your Teams app across Microsoft 365 provides a streamlined way to deliver cross-platform apps to an expanded user audience: from a single codebase, you can create app experiences tailored for Teams, Outlook, and Microsoft 365 app environments. End users don't have to leave the context of their work to use your app, and administrators benefit from a consolidated management and deployment workflow.
The Teams app platform continues to evolve and expand holistically into the Microsoft 365 ecosystem. Here's the current support of Teams app platform elements across Microsoft 365 (Teams, Outlook, and Microsoft 365 as application hosts):
Teams app features | App manifest element | Teams support | Outlook support | Microsoft 365 app support | Notes |
---|---|---|---|---|---|
Tabs-personal scope | staticTabs |
Web, Desktop, Mobile | Web, Desktop, Mobile (Android, iOS) | Web, Desktop, Mobile (Android, iOS) | Channel and group scopes aren't supported for Microsoft 365. For more information, see Teams JavaScript client library. |
Meeting apps | configurableTabs |
Web, Desktop, Mobile | Desktop | - | Meeting Stageview isn't supported in Outlook. See notes. |
Message extensions-search-based | composeExtensions |
Web, Desktop, Mobile | Web, Desktop | - | For limitations and troubleshooting, see notes. |
Action-based message extensions | composeExtensions |
Web, Desktop, Mobile | Web | - | Viewable/actionable (not composable) in Teams/Outlook mobile preview (iOS, Android). For limitations and troubleshooting, see notes. |
Link unfurling (including Stageview) | composeExtensions.messageHandlers |
Web, Desktop | Web, Desktop | - | See notes on link unfurling and Stageview |
Adaptive Card Loop components | composeExtensions.messageHandlers |
Web, Desktop | Web, Desktop (only for new Outlook) | - | Viewable (not composable) in Teams/Outlook mobile preview (iOS, Android). See notes. |
Stageview | composeExtensions.messageHandlers |
Web, Desktop, Mobile | Web (preview), Desktop (preview) | - | Viewable/actionable (not composable) in Outlook mobile preview (iOS, Android). See notes. |
Outlook Add-ins | extensions |
- | Web, Desktop | - | See notes. |
Enrollment to Microsoft 365 Targeted Release and Microsoft 365 Apps update channel requires admin opt-in for the entire organization or selected users. Update channels are device specific and apply only to installations of Microsoft 365 running on Windows.
Note
Apps with app manifest version below 1.13 are limited to Teams. However, apps with app manifest version 1.13 or above are compatible with Teams, Outlook, and Microsoft 365 app.
- For more information on admin guidance and options for managing your extended Teams app, see Teams apps that work on Outlook and Microsoft 365.
- For more information on app manifest, TeamsJS versioning, and Teams platform capability support across Microsoft 365, see Teams JavaScript client library overview.
Reach your users where they are, right in the context of their work by extending your web app as a Teams personal tab application that also runs in both Outlook and Microsoft 365 app. Teams personal tabs built and hosted with SharePoint Framework (SPFx) version 1.16 and later are also supported in Outlook and Microsoft 365 app.
On mobile, you can test and debug your Teams personal tab running on Microsoft 365 for iOS and Android app, in addition to Outlook for iOS and Android app.
You can extend your Teams message extensions to Outlook on the web and Windows in addition to Microsoft Teams clients.
Link unfurling works in Outlook web and Windows environments the same way it does in Microsoft Teams without any further work than using the app manifest version 1.13 or later. You can also unfurl links with cards that launch Stageview.
Build your app with the latest app manifest and Teams JavaScript client library to benefit the latest consolidated Microsoft 365 app development process. Then deliver a streamlined deployment, installation, and admin experience for your customers that expands the reach and usage of your app.
Users can discover and use your meeting app right in the flow of their work when you extend your meeting app to Outlook for Windows.
With an aim toward simplifying and streamlining the Microsoft 365 developer ecosystem, we're continuing to expand the app manifest into other areas of Microsoft 365 with the following.
You can now define and deploy Outlook Add-ins in version 1.17 and later of the app manifest.
For more information, see app manifest for Office Add-ins.
To create an app within the Microsoft 365 ecosystem, consider how it helps your users to perform their work and complete their daily tasks. By being thoughtful in your app planning and design, you can create an experience that is more integrated and introduces less friction for users with their app.
To get started with apps extended across Microsoft 365, see app playbooks and Microsoft 365 UI Kit (Figma) preview.
Actions aim to integrate your app into your user's workflow by enabling easy discoverability and seamless interaction with their content. By directing users to your app with their intent and contextual content, Actions enable efficient task completion. This integration enhances the visibility and engagement of your app with minimal development effort.
For more information, see Actions in Microsoft 365
Join the growing number of production Teams apps in the Microsoft commercial marketplace (Microsoft AppSource) store with expanded support for Outlook and Microsoft 365 audiences. The app submission process for Teams apps enabled for Outlook and Microsoft 365 is the same as for traditional Teams apps. The only difference is to use app manifest version 1.13 or later in your app package, which introduces support for Teams apps that run across Microsoft 365.
After your app is published as a Microsoft 365-enabled Teams app, your app will be discoverable as an installable app in the Outlook and Microsoft 365 app stores, in addition to the Microsoft Teams Store. When running in Outlook and Microsoft 365 app, your app uses the same permissions granted in Teams. Teams admins can manage access to Teams apps across Microsoft 365 for users in their organization.
For more information, see publish Teams apps for Microsoft 365.
Set up your dev environment to build Teams apps for Microsoft 365:
Platform Docs feedback
Platform Docs is an open source project. Select a link to provide feedback: