MicrosoftDocs · KirtiJha-MSFT · Sep 14, 2025
diff --git a/msteams-platform/concepts/deploy-and-publish/apps-upload.md b/msteams-platform/concepts/deploy-and-publish/apps-upload.md
@@ -22,7 +22,7 @@ You can upload Microsoft Teams apps without having to publish to your organizati
 > * App upload and installation are supported in Teams for desktop and web (availability depends on your organization’s app setup policies and cloud environment)
 > * We recommend you to avoid multiple uploads of your message extension app to Teams, as it results in multiple instances of the message extension.
 
-Users can't chat with bots that aren't connected to a Microsoft Teams app such as Azure bots created through the Bot Framework or Power Virtual Agents. We recommend you to create a new Teams app connected to the Azure Bot using the [Developer Portal](../build-and-test/manage-your-apps-in-developer-portal.md#configure), publish it to Teams, and allow users to install the app using the [app permission policies](/microsoftteams/teams-app-permission-policies#edit-an-app-permission-policy).
+Users can't chat with bots that aren't connected to a Microsoft Teams app such as Azure bots created through the Agents SDK or Power Virtual Agents. We recommend you to create a new Teams app connected to the Azure Bot using the [Developer Portal](../build-and-test/manage-your-apps-in-developer-portal.md#configure), publish it to Teams, and allow users to install the app using the [app permission policies](/microsoftteams/teams-app-permission-policies#edit-an-app-permission-policy).
 
 If you want to test the app, you can assign users an [app setup policy](/microsoftteams/teams-app-setup-policies#manage-app-setup-policies) that allows uploading custom apps and chat with the Azure bot through a direct link to a chat.
 

diff --git a/...cepts/deploy-and-publish/appsource/prepare/teams-store-validation-guidelines.md b/...cepts/deploy-and-publish/appsource/prepare/teams-store-validation-guidelines.md
@@ -499,7 +499,7 @@ App packages must be correctly formatted and include all required information an
 The app manifest defines your app's configuration.
 
 * Your app manifest must conform to a publicly released app manifest schema. For more information, see [app manifest reference](~/resources/schema/manifest-schema.md). Don't submit your app using a preview version of the app manifest.
-* If your app includes a bot or message extension, details in the app manifest must be consistent with Bot Framework metadata including bot name, logo, privacy policy link, and terms of service link.
+* If your app includes a bot or message extension, details in the app manifest must be consistent with Agents SDK metadata including bot name, logo, privacy policy link, and terms of service link.
 * If your app uses Microsoft Entra ID for authentication, include the Microsoft Entra Application (client) ID in the app manifest. For more information, see the [app manifest reference](~/resources/schema/manifest-schema.md#webapplicationinfo).
 
 ### Uses of latest app manifest schema
@@ -1360,7 +1360,7 @@ Apps that consist of notification only bots provide user value by triggering use
 
 <details><summary>Bot metadata information</summary>
 
-* Bot information in the app manifest (bot name, logo, privacy link, and terms of service link) must be consistent with the Bot Framework metadata. [*Must fix*]
+* Bot information in the app manifest (bot name, logo, privacy link, and terms of service link) must be consistent with the Agents SDK metadata. [*Must fix*]
 
 * Ensure that the bot ID in the app manifest matches with bot ID in the last Teams Store published version of your app. Changing bot IDs in an app update leads to permanent loss of all user interaction history with the bot for existing users of your app and starts a new conversation chain with the new Bot ID. [*Must fix*]
 

diff --git a/msteams-platform/get-started/glossary.md b/msteams-platform/get-started/glossary.md
@@ -43,10 +43,10 @@ Common terms and definitions used in Microsoft Teams developer documentation.
 | [Bot](../bots/what-are-bots.md) | A bot is an app or service that executes programmed repetitive tasks. <br> **See also**: [Conversational bot](#c); [Chat bot](#c) |
 | Bot Builder SDK | It's an open-source SDK hosted on GitHub to help build dialogs within your Node.js- or C#-based bot. |
 | [Bot Emulator](../bots/how-to/debug/locally-with-an-ide.md#use-the-bot-emulator) | A desktop application that lets you test and debug bots, either locally or remotely. |
-| [Bot Framework](../bots/bot-features.md) | A rich SDK used to create bots using C#, Java, Python, and JavaScript. If you have a bot that is based on the Bot Framework, you can modify it to work in Teams. <br> [Bot Framework Token Service](#b); [Bot Framework Schema](#b) |
+| [Bot Framework](../bots/bot-features.md) | A rich SDK used to create bots using C#, Java, Python, and JavaScript. If you have a bot that is based on the Agents SDK, you can modify it to work in Teams. <br> [Bot Framework Token Service](#b); [Bot Framework Schema](#b) |
 | [Bot handle](../bots/how-to/authentication/bot-sso-register-aad.md) | A bot handle is a unique identifier for your bot. A bot handle represents a bot's registration with the online Azure Bot Service. This registration is associated with an HTTP webhook endpoint and registration with channels. <br> **See also**: [SSO](#s); [Bot resource](#b); [Microsoft Entra ID](#a) |
-| Bot Framework Schemas | Bot Framework Schemas are specifications for JSON data. They define the shape of the data and can be used to validate JSON. <br> **See also**: [Bot Framework](#b) |
-| [Bot Framework Token Service](../bots/how-to/authentication/bot-sso-overview.md) | It's a feature of Bot Framework that facilitates a bot app to use the OAuth protocol for acquiring and storing access token. <br> **See also**: [Bot Framework](#b); [SSO](#s); [Access token](#a); [Identity token](#i) <br> For more information, see [Bot Framework Token Service](/azure/bot-service/bot-builder-concept-authentication#about-the-bot-framework-token-service) |
+| Agents SDK Schemas | Agents SDK Schemas are specifications for JSON data. They define the shape of the data and can be used to validate JSON. <br> **See also**: [Bot Framework](#b) |
+| [Bot Framework Token Service](../bots/how-to/authentication/bot-sso-overview.md) | It's a feature of Agents SDK that facilitates a bot app to use the OAuth protocol for acquiring and storing access token. <br> **See also**: [Bot Framework](#b); [SSO](#s); [Access token](#a); [Identity token](#i) <br> For more information, see [Bot Framework Token Service](/azure/bot-service/bot-builder-concept-authentication#about-the-bot-framework-token-service) |
 | [Bot ID](../bots/how-to/authentication/bot-sso-register-aad.md) | A unique identifier of your bot app that is generated at the time you register your app in Microsoft Entra ID. <br> **See also**: [Bot handle](#b) |
 | [Bot resource](../bots/how-to/authentication/bot-sso-register-aad.md) | The Azure Bot resource (bot resource) allows you to register your bot with Azure Bot Services and to connect your bot to channels. <br> **See also**: [SSO](#s); [Microsoft Entra ID](#a) |
 

diff --git a/msteams-platform/get-started/tool-options-and-code-samples.md b/msteams-platform/get-started/tool-options-and-code-samples.md
@@ -52,7 +52,7 @@ To start building your Teams app, you can select the tools and SDKs based on you
 | App capabilities | User interactions | Recommended tools | SDKs | Languages |
 |--------|-------------|--------|--------|--------|
 | **Tabs** | A full-screen embedded web experience. | VS Code or Visual Studio with Agents Toolkit extension, or [Microsoft 365 Agents Toolkit CLI](../toolkit/Microsoft-365-Agents-Toolkit-CLI.md) (previously known as TeamsFx CLI) if you prefer using CLI | [Teams JavaScript client library](/javascript/api/overview/msteams-client#microsoft-teams-javascript-client-library) for UI functionalities, SharePoint Framework (SPFx), and Microsoft Graph SDK | C#, TypeScript, and JavaScript (including React) |
-| **Bots** | A chat bot that converses with members. |VS Code or Visual Studio with Agents Toolkit extension, or [Agents Toolkit CLI](../toolkit/Microsoft-365-Agents-Toolkit-CLI.md) if you prefer using CLI | [TeamsFx SDK](/javascript/api/@microsoft/teamsfx), [Bot Framework SDK](https://dev.botframework.com/), [Teams AI library](../bots/how-to/teams-conversational-ai/teams-conversation-ai-overview.md), and Microsoft Graph SDK | C#, TypeScript, and JavaScript |
+| **Bots** | A chat bot that converses with members. |VS Code or Visual Studio with Agents Toolkit extension, or [Agents Toolkit CLI](../toolkit/Microsoft-365-Agents-Toolkit-CLI.md) if you prefer using CLI | [TeamsFx SDK](/javascript/api/@microsoft/teamsfx), [Agents SDK](https://dev.botframework.com/), [Teams AI library](../bots/how-to/teams-conversational-ai/teams-conversation-ai-overview.md), and Microsoft Graph SDK | C#, TypeScript, and JavaScript |
 | **Message extensions** | Shortcuts for inserting external content into a conversation or taking action on messages. | VS Code or Visual Studio with Agents Toolkit extension, or [Agents Toolkit CLI](../toolkit/Microsoft-365-Agents-Toolkit-CLI.md) if you prefer using CLI | [TeamsFx SDK](/javascript/api/@microsoft/teamsfx), [Bot Framework SDK](https://dev.botframework.com/), [Teams AI library](../bots/how-to/teams-conversational-ai/teams-conversation-ai-overview.md), and Microsoft Graph SDK | C#, TypeScript, and JavaScript |
 
 > [!NOTE]