[Doc Improvement][Remove classic Teams instances][3968740]

msteams-platform/apps-in-teams-meetings/build-apps-for-teams-meeting-stage.md

@@ -203,7 +203,7 @@ The following table includes the query parameter:
 > [!NOTE]
 >
 > * Only In-tenant or guest and external users with presenter or organizer role can initiate a sharing session.
-> * Share to stage using screen share isn't supported on Mac, classic Teams, mobile, web and VDI.
+> * Share to stage using screen share isn't supported on Mac, mobile, web, and VDI Teams clients.
 > * In Teams, you can't share your screen and share to the stage at the same time.
 
 Users can screen share content to the meeting Stage in Teams using the screen sharing architecture. When a user shares an app to the meeting stage, the app is rendered only on the presenter’s device and then the screen is shared or mirrored to all other attendees in a new window. After the app content is shared in a meeting, all the participants can view the content, but only the presenter has the ability to interact with the content, which provides a multi-player viewing experience.

msteams-platform/apps-in-teams-meetings/teams-live-share-faq.md

@@ -72,7 +72,7 @@ Yes! Live Share supports chat and channel content contexts, including configurab
 
 <summary><b>Will Live Share's media package work with DRM content?</b></summary>
 
-Yes, DRM is supported in the new Teams desktop, web, iOS, and Android clients. The classic Teams client doesn't support DRM. To enable DRM encryption for Teams desktop, enable the `media` device permission in your app manifest.
+Yes, DRM is supported in Teams desktop, web, iOS, and Android clients. To enable DRM encryption for Teams desktop, enable the `media` device permission in your app manifest.
 
 <br>
 

msteams-platform/messaging-extensions/how-to/action-commands/define-action-command.md

@@ -25,7 +25,7 @@ First, you must decide the location from where your action command must be invok
 
     Commands context = `compose`
 
-* Command box: By using / in the command box. For example, **/your-app-name**. If you're using the classic Teams, action command is invoked by @mentioning in the command box. For example, **@your-app-name**.
+* Command box: By using / in the command box. For example, **/your-app-name**.
 
     Commands context = `commandBox`
 
@@ -100,7 +100,7 @@ To create an action-based message extension using Developer Portal for Teams, fo
    :::image type="content" source="../../../assets/images/Copilot/bot-based-me-tdp-type.png" alt-text="Screenshot shows API Message extension is already in use disclaimer when a user switches from API to bot message extension type.":::
 
 1. If you don't have an existing bot, select **Existing bot** or if you have a bot ID, select **Enter Bot ID**.
-   
+
    1. If you don't have a bot ID, select **Create a bot**, to create a new bot and enter the bot ID of the new bot that you created.
 
 1. Select the required scopes.
@@ -110,7 +110,7 @@ To create an action-based message extension using Developer Portal for Teams, fo
    A command details page appears.
 
 1. In the Command details page, select **Action** and then select parameter type.
-    
+
 1. Select **Action** as the type of command and update the following fields:
    * Command ID
    * Command title
@@ -141,7 +141,7 @@ To create an action-based message extension using Developer Portal for Teams, fo
 
    :::image type="content" source="../../../assets/images/tdp/add-parameter.PNG" alt-text="Screenshot shows how to add additional parameters for your message extension."lightbox="../../../assets/images/tdp/add-a-parameters.PNG":::
 
-1. Select **Save**   
+1. Select **Save**
 
 A bot-based action message extension is created.
 

msteams-platform/messaging-extensions/how-to/search-commands/define-search-command.md

@@ -13,7 +13,7 @@ ms.owner: slamba
 The search command is invoked from any one or both of the following locations:
 
 * Compose message area: The buttons at the bottom of the compose message area.
-* Command box: By using / in the command box. For example, **/your-app-name**. If you're using the classic Teams, search command is invoked by @mentioning in the command box. For example, **@your-app-name**.
+* Command box: By using / in the command box. For example, **/your-app-name**.
 
 When a search command is invoked from the compose message area, the user sends the results to the conversation. When a search command invoked from the command box, the user interacts with the resulting card, or copies it for use elsewhere.
 

msteams-platform/resources/dev-preview/developer-preview-intro.md

@@ -29,8 +29,6 @@ Using an app that contains developer preview features might cause clients that d
 > [!NOTE]
 > If your tenant is enrolled for [Microsoft 365 Targeted Releases](/microsoft-365/admin/manage/release-options-in-office-365), developer preview is automatically enabled and the developer preview switch isn't available.
 
-# [New Teams client](#tab/new-teams-client)
-
 To enable the public developer preview on Teams desktop or web client:
 
 1. Enable custom app upload for your developer tenant. For more information, see [enable custom app upload](../../concepts/build-and-test/prepare-your-o365-tenant.md#enable-custom-teams-apps-and-turn-on-custom-app-uploading).
@@ -40,20 +38,6 @@ To enable the public developer preview on Teams desktop or web client:
 
 :::image type="content" source="../../assets/images/teams-enable-developer-preview.png" alt-text="Screenshot shows the Public preview checkbox option in About Teams section in Teams settings.":::
 
-# [Classic Teams](#tab/classic-teams)
-
-To enable the public developer preview on Teams desktop or web client:
-
-1. Enable custom app upload for your developer tenant. For more information, see [enable custom app upload](../../concepts/build-and-test/prepare-your-o365-tenant.md#enable-custom-teams-apps-and-turn-on-custom-app-uploading).
-1. Select the **Settings and more** (**...**) next to your user profile.
-1. Select **About** > **Developer preview**.
-
-   :::image type="content" source="../../assets/images/classic-teams-developer-preview.png" alt-text="Screenshot shows the Developer preview option in the About section in Classic Teams.":::
-
-1. Select **Switch to developer preview**.
-
----
-
 ### Mobile client
 
 To enable the public developer preview on Teams mobile client:

msteams-platform/sbs-gs-msgext.yml

@@ -360,10 +360,6 @@ items:
 
         The app opens in the command box and you can use it to run a query.
 
-        > [!NOTE]
-        > * Using **/** to open your message extension app from the command box only works in the new Teams client.
-        > * Use **@** to open your message extension app from the command box in the classic Teams client.
-
    </details>
 
    <br>

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

@@ -200,7 +200,7 @@ Starting with TeamsJS v.2.0, APIs are defined as functions in a JavaScript names
 
 You can check for host support of a given capability at runtime by calling the `isSupported()` function on that capability (namespace). It returns `true` if it's supported and `false` if not, and you can adjust app behavior as appropriate. This allows your app to light up UI and functionality in hosts that support it, while continuing to run for hosts that don't.
 
-The host name where your app operates is displayed as a [HostName](/javascript/api/%40microsoft/teams-js/hostname) enum value of the `Context` interface (`app.Context.app.host.name`). You can query this at runtime by invoking `getContext`. For the Classic Teams client, this value might return as *unknown* or *undefined*. In this case, map these values to Classic Teams.
+The host name where your app operates is displayed as a [HostName](/javascript/api/%40microsoft/teams-js/hostname) enum value of the `Context` interface (`app.Context.app.host.name`). You can query this at runtime by invoking `getContext`.
 
 The `{hostName}` [URL placeholder value](./access-teams-context.md#get-context-by-inserting-url-placeholder-values) is also available. However, we recommend using the *hostName* mechanism with discretion.
 

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md

@@ -49,7 +49,7 @@ To add an Incoming Webhook to a Teams channel, follow these steps:
 
 # [New Teams](#tab/newteams)
 
-1. In the New Teams client, select **Teams** :::image type="icon" source="../../assets/images/teams-icon.png" border="false"::: and navigate to the channel where you want to add an Incoming Webhook.
+1.Select **Teams** :::image type="icon" source="../../assets/images/teams-icon.png" border="false"::: and navigate to the channel where you want to add an Incoming Webhook.
 
 1. Select **More options** ••• on the right side of the channel name.
 
@@ -94,45 +94,6 @@ The following graphical representation provides the steps to create an Incoming
 
 :::image type="content" source="../../assets/images/create-incoming-webhook.gif" alt-text="The graphical representation shows the steps to create an Incoming Webhook.":::
 
-# [Classic Teams](#tab/classicteams)
-
-1. In the Classic Teams client, select **Teams** :::image type="icon" source="../../assets/images/teams-icon.png" border="false"::: and navigate to the channel where you want to add an Incoming Webhook.
-
-1. Select **More options** ••• from the upper-right corner.
-
-1. Select **Connectors** from the dropdown menu.
-
-   :::image type="content" source="../../assets/images/connectors_1.png" alt-text="Screenshot shows how to select connector.":::
-
-1. Search for **Incoming Webhook** and select **Add**.
-
-   :::image type="content" source="../../assets/images/search-add-webhook.png" alt-text="Screenshot shows the Add option to add an Incoming Webhook.":::
-
-    The Incoming Webhook dialog appears.
-
-1. Select **Add**.
-
-    :::image type="content" source="../../assets/images/add-incoming-webhook.png" alt-text="Screenshot shows the Add option in the Incoming Webhook dialog." lightbox="../../assets/images/add-incoming-webhook-lightbox.png":::
-
-    > [!NOTE]
-    > If you’ve already added an Incoming Webhook, the **Configure** option appears. Select **Configure** to create an Incoming Webhook.
-
-1. Provide a name for the webhook and upload an image if necessary.
-
-1. Select **Create**.
-
-   :::image type="content" source="../../assets/images/create-incoming-webhook.png" alt-text="Screenshot shows the name and image fields to be filled to create the webhook.":::
-
-1. Copy and save the unique webhook URL present in the dialog. The URL maps to the channel and you can use it to send information to Teams.
-
-1. Select **Done**.
-
-   :::image type="content" source="../../assets/images/url_1.png" alt-text="Screenshot shows the unique webhook URL.":::
-
-The webhook is now available in the Teams channel.
-
----
-
 > [!IMPORTANT]
 > You can build a notification bot Teams app using [Microsoft 365 Agents Toolkit](../../toolkit/agents-toolkit-fundamentals.md) (previously known as Teams Toolkit) other than an Incoming Webhook. They perform similarly but notification bot has more functionalities. For more information, see [Build notification bot with JavaScript](../../sbs-gs-notificationbot.yml) or [Incoming Webhook notification sample](https://github.com/OfficeDev/TeamsFx-Samples/tree/dev/incoming-webhook-notification).
 
@@ -223,7 +184,7 @@ To remove an Incoming Webhook from a Teams channel, follow these steps:
 
 # [New Teams](#tab/newteams)
 
-1. In the New Teams client, select the Teams icon :::image type="icon" source="../../assets/images/teams-icon.png" border="false"::: and navigate to the channel where you want to remove an Incoming Webhook.
+1. Select the Teams icon :::image type="icon" source="../../assets/images/teams-icon.png" border="false"::: and navigate to the channel where you want to remove an Incoming Webhook.
 
 1. Select **More options** ••• on the right side of the channel name.
 
@@ -259,35 +220,6 @@ To remove an Incoming Webhook from a Teams channel, follow these steps:
 
 The webhook is now removed from the Teams channel.
 
-# [Classic Teams](#tab/classicteams)
-
-1. In the Classic Teams client, select the Teams icon :::image type="icon" source="../../assets/images/teams-icon.png" border="false"::: and navigate to the channel where you want to remove an Incoming Webhook.
-1. Select **More options** ••• from the upper-right corner.
-1. Select **Connectors** from the dropdown menu.
-1. In the left pane, select **Configured**.
-1. Under Incoming Webhook, select **1 Configured**.
-
-   :::image type="content" source="../../assets/images/configured_1-new-teams.png" alt-text="The screenshot shows how to configure to see list of your connectors.":::
-
-1. Select **Manage**.
-
-   :::image type="content" source="../../assets/images/manage_1.png" alt-text="Screenshot shows how to manage for connector that you want to remove.":::
-
-1. Select **Remove**.
-
-   :::image type="content" source="../../assets/images/Select_Remove.png" alt-text="Select remove"lightbox="../../assets/images/Select_Remove.png":::
-
-   The Remove Configuration dialog appears.
-
-1. Select the required checkboxes.
-1. Select **Remove**.
-
-   :::image type="content" source="../../assets/images/finalremove_1.png" alt-text="Screenshot shows how to remove an Incoming Webhook from Teams channel.":::
-
-The webhook is now removed from the Teams channel.
-
----
-
 ## Code sample
 
 | Sample name | Description | .NET | Node.js |