Address doc issue

.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
       }
     ]
 }

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

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)
+* [Get context for your tab](../tabs/how-to/access-teams-context.md)

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.

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
 

msteams-platform/tabs/how-to/access-teams-context.md

@@ -384,4 +384,3 @@ The following image shows the dark theme option in the Teams:
 * [Microsoft Teams Connect shared channels](../../concepts/build-and-test/shared-channels.md)
 * [App manifest schema for Teams](/microsoft-365/extensibility/schema/)
 * [Use dialogs in tabs](../../task-modules-and-cards/task-modules/task-modules-tabs.md)
-* [Introducing the new Teams client](../../resources/teams-updates.md)

msteams-platform/tabs/how-to/create-tab-pages/content-page.md

@@ -111,9 +111,6 @@ You can access additional content by using TeamsJS to interact with Teams, creat
 
 * **Dialogs**: A dialog is a modal pop-up experience that you can trigger from your tab. Use dialogs in a content page to present forms for gathering additional information, displaying the details of an item in a list, or presenting the user with additional information. The dialogs themselves can be additional content pages or created completely using Adaptive Cards. For more information, see [using dialogs in tabs](~/task-modules-and-cards/task-modules/task-modules-tabs.md).
 
-    > [!NOTE]
-    > The `window.alert`, `window.confirm`, and `window.prompt` APIs aren't supported in the new Teams client. Use a [Fluent V9 dialog](https://react.fluentui.dev/?path=/docs/components-dialog--default) or a TeamsJS dialog instead. For more information, see [new Teams client limitations](~/resources/teams-updates.md#limitations).
-
 * **Valid domains**: Ensure that all URL domains used in your tabs are included in the `validDomains` array in your [app manifest](~/concepts/build-and-test/apps-package.md). For more information, see [validDomains](/microsoft-365/extensibility/schema/root#validdomains).
 
 > [!NOTE]

msteams-platform/tabs/how-to/using-teams-client-library.md

@@ -306,7 +306,7 @@ The `pages` namespace includes functionality for running and navigating webpages
 ##### *dialog* namespace
 
 > [!NOTE]
-> The `window.alert`, `window.confirm`, and `window.prompt` APIs used to display a dialog aren't supported in the new Teams Client. We recommended you to 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 `<iframe>`. For a complete list of unsupported features, see [new Teams client limitations](~/resources/teams-updates.md#limitations).
+> We recommended you to 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 `<iframe>`.
 
 The TeamsJS *tasks* namespace is renamed to *dialog*, and the following APIs are renamed:
 

msteams-platform/tabs/what-are-tabs.md

@@ -13,7 +13,6 @@ Tabs are client-aware webpages embedded in Microsoft Teams, Outlook, and Microso
 > [!IMPORTANT]
 >
 > * Custom tabs are available in Government Community Cloud (GCC), GCC High, Department of Defense (DoD), and Teams operated by 21Vianet.
-> * Adaptive Card tabs aren't supported in the new Teams client. If your app uses Adaptive Card tabs, rebuild it as a web-based tab. For more information, see [new Teams client limitations](../resources/teams-updates.md#limitations).
 
 There are two types of tabs, static and configurable tabs. These tabs can be utilized in three distinct scopes: `personal`, `groupchat`, and `teams`. [Personal (static) tabs](~/tabs/how-to/create-personal-tab.md), along with personal-scoped bots, are part of the personal apps that are scoped to a single user and pinned to the left navigation bar for easy access. Personal (static) tabs in personal scope continue to work the same way. However, you can now [extend static tabs](~/tabs/how-to/create-personal-tab.md#extend-static-tabs-to-group-chat-channels-and-meetings) to group chats, channels, or meetings with a [customizable experience.](~/tabs/how-to/create-personal-tab.md#customizing-your-static-tab-in-chats-or-meetings)
 
@@ -157,7 +156,6 @@ Now let's build your tab. But first select your choice of tab to build:
 * [Design your tab for Microsoft Teams](design/tabs.md)
 * [Tabs on mobile](design/tabs-mobile.md#tabs-on-mobile)
 * [Extend tab app with Microsoft Graph permissions and scopes](how-to/authentication/tab-sso-graph-api.md)
-* [Microsoft Teams updates](../resources/teams-updates.md)
 * [Grant tab device permission in Teams](~/sbs-tab-device-permissions.yml)
 * [Agents Toolkit for Visual Studio Code](../toolkit/agents-toolkit-fundamentals.md)
 * [Agents Toolkit for Visual Studio](../toolkit/visual-studio-overview.md)