[Doc Improvement][New Teams client updates][4184435]

msteams-platform/resources/teams-updates.md

@@ -1,16 +1,16 @@
 ---
 title: The New Microsoft Teams Client
 description: Learn about the new Microsoft Teams, advantages, timelines, rollout, limitations, versions, deprecated features, and latest updates.
-author: v-ypalikila
+author: surbhigupta
 ms.author: lajanuar
 ms.localizationpriority: medium
 ms.topic: reference
-ms.date: 01/23/2025
+ms.date: 01/27/2025
 ---
 # Introducing the new Microsoft Teams client
 
 > [!IMPORTANT]
-> The Classic Teams client has been deprecated on March 31, 2024.
+> The Classic Teams client has been deprecated on March 31, 2024. 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.
 
@@ -26,7 +26,7 @@ You can use the following property to identify your app usage in the new Teams o
 * 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.
+> 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.
 
@@ -43,10 +43,6 @@ To ensure a smooth transition, a phased rollout of the new platform is planned.
 > * The new Teams client is supported in Windows and Mac clients and Government Community Cloud (GCC) and GCC High environments.
 > * We recommend you to test the functionality of apps, tabs, messaging extensions, bots, and link unfurling on Windows and Mac clients and GCC and GCC High environments after switching from the Classic Teams client to the new Teams client.
 
-The following Teams features aren't supported in the new Teams client:
-
-* [Generating a deep link to share content to stage in meetings](~/concepts/build-and-test/share-in-meeting.md#generate-a-deep-link-to-share-content-to-stage-in-meetings) isn't supported in the new Teams client.
-
 The following Teams features are deprecated and aren't supported in the new Teams client:
 
 * [Adaptive Card tabs](../tabs/how-to/build-adaptive-card-tabs.md) aren't supported in the new Teams client. The Classic Teams client has been deprecated on March 31, 2024. If your app is using Adaptive Card tabs, we recommend you rebuild the tab as a web-based tab. For more information, see [build tabs for Teams](../tabs/what-are-tabs.md).
@@ -63,3 +59,6 @@ If your app is working fine in the Classic Teams client but has issues in the ne
 
 * [Teams app that fits](../overview.md)
 * [Get context for your tab](../tabs/how-to/access-teams-context.md#handle-theme-change)
+* [New Teams for Web - Overview and prerequisites](/microsoftteams/new-teams-web)
+* [Features that are changing in the new Microsoft Teams](/microsoftteams/new-teams-whats-changing)
+* [The new Microsoft Teams](/microsoftteams/new-teams-desktop-admin)