

Teams APIs that previously took a callback parameter have been updated to return a JavaScript Promise object. The getTabInstances API isn't implemented on Teams mobile. Updating your app manifest to version 1.13 or later.įor more info, see Extend Teams apps across Microsoft 365.
IFRAME CHATID CODE
Modifying existing application code according to the required changes described in this article, and Teams apps running across Microsoft 365Įnabling an existing Teams app to run in Outlook and Microsoft 365 requires all of the following:ĭependency on TeamsJS version 2.x.x ( or later, In the meantime, the v.1 to v.2 API translation layer provides backwards compatibility, ensuring your existing Teams app continues to work in TeamsJS version 2.0.
IFRAME CHATID UPDATE
Once you're able, the next step is to update existing application code with the changes described in this article. TeamsJS v.1.12 will continue to be supported, but no new features or improvements will be added. Teams-only appsĮven if you intend your app to only run in Teams (and not Microsoft 365 app and Outlook), best practice is to start referencing the latest TeamsJS ( v.2.0 or later) as soon as convenient, in order to benefit from the latest improvements, new features, and support (even for Teams-only apps). Once you start referencing (or later) from an existing Teams app, you'll see deprecation warnings for any code calling APIs that have changed.Īn API translation layer (mapping v.1 to v.2 TeamsJS API calls) is provided to enable existing Teams apps to continue working in Teams until they're able to update application code to use the TeamsJS v.2 API patterns. You can use the Teams Toolkit extension for Microsoft Visual Studio Code to simplify the TeamsJS v.2.0 update process for an existing Teams app. Each namespace represents a separate capability. You can think of capabilities as logical groupings of APIs that provide similar functionality, such as authentication, dialog, chat, and calendar. Most functions with callback parameters in TeamsJS v.1.12 have been modernized to return a JavaScript Promise object for improved handling of asynchronous operations and code readability.ĪPIs are now organized into capabilities. There are two significant changes between TeamsJS 1.x.x versions and v.2.0.0 and later:Ĭallback functions now return Promise objects. For a summary of host support for Teams apps, see TeamsJS capability support across Microsoft 365. Currently, other Microsoft 365 application hosts (including Microsoft 365 app and Outlook) for Teams apps support a subset of the application types and capabilities you can build for the Teams platform. TeamsJS v.2.0 introduces the ability for certain types of Teams apps to run across the Microsoft 365 ecosystem. Microsoft 365 support (running Teams apps in Microsoft 365 and Outlook) The remainder of this article will walk you through the structure and latest updates to the TeamsJS library. For more information, see TeamsJS library. The 1.12 and 1.13 schemas are otherwise the same. TeamsJS v.1.12 continue to be supported, however, no new features or improvements will be added. * Use the latest TeamsJS (v.2.0 or later) whenever possible, in order to leverage from the latest improvements and new feature support including Teams-only apps. Understand TeamsJS backwards compatibility and Update to TeamsJS v.2.0Ĭreate a new Teams app using Teams Toolkit

Update to TeamsJS v.2.0 when possible (v.1.12 is still supported*) Teams apps extended to Microsoft 365 / OutlookĮxtend a Teams app to run across Microsoft 365 or Create a new Microsoft 365 app Here's the current versioning guidance for various app scenarios: From a functional perspective, the latest version of TeamsJS supports all existing (v.1.x.x) Teams app functionality while adding the optional ability to host Teams apps in Outlook and Microsoft 365 app. Starting with version 2.0.0, the existing TeamsJS library ( or simply TeamsJS) has been refactored to enable Teams apps to run in Outlook and Microsoft 365 app, in addition to Microsoft Teams. The library is helpful for developing apps with the following Teams capabilities: The Microsoft Teams JavaScript client library (TeamsJS) can help you create hosted experiences in Teams, Microsoft 365 app, and Outlook, where your app content is hosted in an iFrame.
