diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json index 87e5abf8c65..b5338a0adfa 100644 --- a/.openpublishing.redirection.json +++ b/.openpublishing.redirection.json @@ -1590,6 +1590,11 @@ "source_path": "msteams-platform/agents-in-teams/build-first-agent.md", "redirect_url": "quickstart-create-agent-teams-sdk", "redirect_document_id": false + }, + { + "source_path": "msteams-platform/resources/teams-updates.md", + "redirect_url": "/microsoftteams/platform/overview", + "redirect_document_id": false } ] } diff --git a/msteams-platform/TOC.yml b/msteams-platform/TOC.yml index 041469be2ed..b9a5d04b875 100644 --- a/msteams-platform/TOC.yml +++ b/msteams-platform/TOC.yml @@ -945,12 +945,9 @@ - name: Troubleshoot your Microsoft Teams app href: resources/troubleshoot.md displayName: DevTools, Cache-Control, authentication issues, app uploading error - - name: Know about New Microsoft Teams client - href: resources/teams-updates.md - displayName: Classic Teams, new Teams client, Teams 2.1 - name: Extend Microsoft 365 Copilot - href: messaging-extensions/how-to-extend-copilot.md - displayName: message extension, plugin, Copilot, Microsoft 365 Copilot + href: messaging-extensions/how-to-extend-copilot.md + displayName: message extension, plugin, Copilot, Microsoft 365 Copilot - name: Tutorials and code samples items: - name: Tutorials diff --git a/msteams-platform/apps-in-teams-meetings/build-apps-for-anonymous-user.md b/msteams-platform/apps-in-teams-meetings/build-apps-for-anonymous-user.md index 9ff7db0cf83..0e30dff93bc 100644 --- a/msteams-platform/apps-in-teams-meetings/build-apps-for-anonymous-user.md +++ b/msteams-platform/apps-in-teams-meetings/build-apps-for-anonymous-user.md @@ -24,9 +24,6 @@ To enable anonymous users to interact with the apps in Teams meetings, ensure to ## App manifest update for anonymous users -> [!NOTE] -> The `supportsAnonymousGuestUsers` property in the app manifest schema v1.16 is supported only in [new Teams client](/microsoftteams/platform/resources/teams-updates). - To allow anonymous users to interact with the tab app, update the `supportsAnonymousGuestUsers` property to `true` in your app manifest schema v1.16 or later. Following is an example of the manifest: ```json @@ -254,4 +251,4 @@ Anonymous users can view and interact with Adaptive Cards in the meeting chat. A * [Build apps for Teams meeting stage](build-apps-for-teams-meeting-stage.md) * [Meeting apps APIs](meeting-apps-apis.md) * [How Microsoft Teams bots work](/azure/bot-service/bot-builder-basics-teams) -* [Get context for your tab](../tabs/how-to/access-teams-context.md) \ No newline at end of file +* [Get context for your tab](../tabs/how-to/access-teams-context.md) diff --git a/msteams-platform/concepts/build-and-test/deep-link-application.md b/msteams-platform/concepts/build-and-test/deep-link-application.md index 9d4e4b5694c..0a72f575bb4 100644 --- a/msteams-platform/concepts/build-and-test/deep-link-application.md +++ b/msteams-platform/concepts/build-and-test/deep-link-application.md @@ -252,9 +252,6 @@ else {/*Handle situation where capability isn't supported*/} --- -> [!NOTE] -> The tab app navigation is supported only in [new Teams client](/microsoftteams/platform/resources/teams-updates). - #### Configure back button navigation When an app has multiple tabs, a user can use the Microsoft 365 host app's back button to go backwards through the navigational history. However, the history doesn't include the actions a user performs within a tab. If you want to enhance the back button experience, you can maintain your own internal navigation stack and configure a custom handler for back button selections. This can be accomplished through the `registerBackButtonHandler()` function in the [`pages.backStack`](/javascript/api/@microsoft/teams-js/pages.backstack) namespace. diff --git a/msteams-platform/concepts/device-capabilities/location-capability.md b/msteams-platform/concepts/device-capabilities/location-capability.md index 4324c74162d..44ca971f63c 100644 --- a/msteams-platform/concepts/device-capabilities/location-capability.md +++ b/msteams-platform/concepts/device-capabilities/location-capability.md @@ -66,7 +66,6 @@ Update your Teams app [manifest.json](/microsoft-365/extensibility/schema/root#d > > * The **Request Permissions** prompt is automatically displayed when a relevant Teams API is initiated. For more information, see [request device permissions](native-device-permissions.md). > * Device permissions are different in the browser. For more information, see [browser device permissions](browser-device-permissions.md). -> * The Location API isn't supported in the [new Teams client](../../resources/teams-updates.md#limitations). We recommend you to use HTML5 `geolocation`. For a complete list of unsupported features, see [new Teams client limitations](../../resources/teams-updates.md#limitations). ## Location APIs diff --git a/msteams-platform/resources/teams-updates.md b/msteams-platform/resources/teams-updates.md deleted file mode 100644 index 425c4caa65a..00000000000 --- a/msteams-platform/resources/teams-updates.md +++ /dev/null @@ -1,82 +0,0 @@ ---- -title: The New Microsoft Teams Client -description: Learn about the new Microsoft Teams, advantages, timelines, rollout, limitations, versions, deprecated features, and latest updates. -ms.author: lajanuar -ms.localizationpriority: medium -ms.topic: reference -ms.date: 02/12/2025 ---- - -# Know about New Microsoft Teams client - -> [!IMPORTANT] -> The Classic Teams client reaches end of availability on July 1, 2025. For more information, see [end of availability for Classic Teams client](/microsoftteams/teams-classic-client-end-of-availability). - -[The new Microsoft Teams client](https://www.microsoft.com/en-us/microsoft-365/blog/2023/03/27/welcome-to-the-new-era-of-microsoft-teams/) is reimagined from the ground up with performance in mind. It's faster, simpler, smarter, and flexible to provide better experience for your apps and users. The new Teams client supports all the existing Teams app capabilities except Adaptive Card tabs. If you have an app that runs inside Classic Teams, the app likely runs in the new Teams client without any issues. - -The following are the advantages of the new Teams client: - -* The new Teams client uses the Evergreen version of Microsoft Edge WebView2 to ensure Teams client is always up to date with the latest fixes and improvements available in Microsoft Edge and Chromium. - -* The new Teams client has been rebuilt from the ground up with performance in mind and includes all the platform infrastructure responsible for bootstrapping your app and powering the SDK APIs that it uses. - -You can use the following property to identify your app usage in the new Teams or Classic Teams client: - -* For TeamsJS v1.x: [`hostName`](/javascript/api/@microsoft/teams-js/context?view=msteams-client-js-latest&preserve-view=true#@microsoft-teams-js-context-hostname) -* For TeamsJS v2.x: [`AppHostInfo`](/javascript/api/@microsoft/teams-js/app.appinfo?view=msteams-client-js-latest&preserve-view=true#@microsoft-teams-js-app-appinfo-host) - -> [!NOTE] -> If `hostName` isn't defined, then assume that your app is running in the Classic Teams client. - -The Classic Teams client is represented using the `teams` field and the new Teams client is represented using the `teamsModern` field. - -## Timelines and rollout - -To ensure a smooth transition, a phased rollout of the new platform is planned. - -**Availability of all platform features from Classic Teams**: All apps are available in the new Teams Client. All platform features except the features listed under [limitations](#limitations) are now available. - -## Limitations - -> [!IMPORTANT] -> Review the following limitations before you design or develop your Teams app. These features are deprecated and aren't supported in the new Teams client. For more details on known issues, see [new Microsoft Teams known issues](/microsoftteams/new-teams-desktop-admin?tabs=teams-admin-center#known-issues). - -### Adaptive Card tabs - -Adaptive Card tabs aren't supported in the new Teams client. If your app uses Adaptive Card tabs, rebuild the tab as a web-based tab. For more information, see [build tabs for Teams](../tabs/what-are-tabs.md). - -If you try to configure or use an Adaptive Card tab in a personal app context, you receive the error **Platform Personal App Tab Type not supported**. - -**Affected features:** - -* [Tabs overview](../tabs/what-are-tabs.md) -* [Create a personal tab](../tabs/how-to/create-personal-tab.md) -* [Content pages in tabs](../tabs/how-to/create-tab-pages/content-page.md) - -### `window.alert`, `window.confirm`, and `window.prompt` APIs - -The `window.alert`, `window.confirm`, and `window.prompt` APIs aren't supported in the new Teams client. Render a dialog within your own frame, for example, using the [Fluent V9 dialog](https://react.fluentui.dev/?path=/docs/components-dialog--default) or use the Microsoft Teams JavaScript client library (TeamsJS) to display a [Teams dialog](../tabs/what-are-tabs.md) using Adaptive Card or a nested `