[Doc Improvement] [Rename Bot framework/Bot Framework SDK to Agent SDK]

msteams-platform/resources/bot-v3/bot-conversations/bots-conversations.md

@@ -40,7 +40,7 @@ Bots also support event-style messages. For more information, see [Handle bot ev
 
 Messages are usually the same in across all scopes, but there are differences in how the bot is accessed in the UI and differences behind the scenes, which you need to know about.
 
-Basic conversation is handled through the Bot Framework Connector, a single REST API to enable your bot to communicate with Teams and other channels. The Bot Builder SDK provides easy access to this API, additional functionality to manage conversation flow and state, and simple ways to incorporate cognitive services such as natural language processing (NLP).
+Basic conversation is handled through the  Microsoft 365 Agents SDK (previously known as Bot Framework SDK) Connector, a single REST API to enable your bot to communicate with Teams and other channels. The Bot Builder SDK provides easy access to this API, additional functionality to manage conversation flow and state, and simple ways to incorporate cognitive services such as natural language processing (NLP).
 
 ## Message content
 
@@ -54,7 +54,7 @@ Your bot can send rich text, pictures, and cards. Users can send rich text and p
 | Emojis | ✖ | ✔ | Teams supports emojis via UTF-16 such as, U+1F600 for grinning face. |
 |
 
-For more information on the types of bot interaction supported by the Bot Framework, which bots in teams are based on, see the Bot Framework documentation on [conversation flow](/azure/bot-service/dotnet/bot-builder-dotnet-manage-conversation-flow?view=azure-bot-service-3.0&preserve-view=true) and related concepts in the documentation for [the Bot Builder SDK for .NET](/azure/bot-service/dotnet/bot-builder-dotnet-overview?view=azure-bot-service-3.0&preserve-view=true) and [the Bot Builder SDK for Node.js](/azure/bot-service/nodejs/bot-builder-nodejs-overview?view=azure-bot-service-3.0&preserve-view=true).
+For more information on the types of bot interaction supported by the  Microsoft 365 Agents SDK (previously known as Bot Framework SDK), which bots in teams are based on, see the  Microsoft 365 Agents SDK (previously known as Bot Framework SDK)documentation on [conversation flow](/azure/bot-service/dotnet/bot-builder-dotnet-manage-conversation-flow?view=azure-bot-service-3.0&preserve-view=true) and related concepts in the documentation for [the Bot Builder SDK for .NET](/azure/bot-service/dotnet/bot-builder-dotnet-overview?view=azure-bot-service-3.0&preserve-view=true) and [the Bot Builder SDK for Node.js](/azure/bot-service/nodejs/bot-builder-nodejs-overview?view=azure-bot-service-3.0&preserve-view=true).
 
 ## Message formatting
 
@@ -89,7 +89,7 @@ Your bot receives a payload that contains the user message `Text` and other info
 
 * `timestamp` The date and time of the message in Coordinated Universal Time (UTC).
 * `localTimestamp` The date and time of the message in the time zone of the sender.
-* `channelId` Always "msteams". This refers to a bot framework channel, not a teams channel.
+* `channelId` Always "msteams". This refers to an  Microsoft 365 Agents SDK (previously known as Bot Framework SDK) channel, not a teams channel.
 * `from.id` A unique and encrypted ID for that user for your bot; suitable as a key if your app needs to store user data. It's unique for your bot and can't be directly used outside your bot instance in any meaningful way to identify that user.
 * `channelData.tenant.id` The tenant ID for the user.
 
@@ -199,7 +199,7 @@ To reply to an existing message, call [`ReplyToActivity`](/dotnet/api/microsoft.
 
 If you choose to use the REST API, you can also call the [`/v3/conversations/{conversationId}/activities/{activityId}`](/azure/bot-service/rest-api/bot-framework-rest-connector-send-and-receive-messages?view=azure-bot-service-3.0&preserve-view=true) endpoint.
 
-The message content itself can contain simple text or some of the Bot Framework supplied [cards and card actions](~/task-modules-and-cards/cards/cards-actions.md).
+The message content itself can contain simple text or some of the  Microsoft 365 Agents SDK (previously known as Bot Framework SDK) supplied [cards and card actions](~/task-modules-and-cards/cards/cards-actions.md).
 
 Please note that in your outbound schema you should always use the same `serviceUrl` as the one you received. Be aware that the value of `serviceUrl` tends to be stable but can change. When a new message arrives, your bot should verify its stored value of `serviceUrl`.
 

msteams-platform/resources/messaging-extension-v3/create-extensions.md

@@ -1,6 +1,6 @@
 ---
 title: Action-based Message Extensions
-description: Learn how to create and configure action-based message extensions for Microsoft Teams using Bot Framework SDK to allow users to trigger external services.
+description: Learn how to create and configure action-based message extensions for Microsoft Teams using  Microsoft 365 Agents SDK (previously known as Bot Framework SDK) to allow users to trigger external services.
 ms.localizationpriority: medium
 ms.topic: how-to
 ms.date: 04/02/2023

msteams-platform/resources/messaging-extension-v3/search-extensions.md

@@ -1,6 +1,6 @@
 ---
 title: Build Search-based Message Extensions
-description: Learn how to create search based message extensions for Microsoft Teams using v3 Bot Framework SDK, handle queries, event handlers, authentication, and SDK support.
+description: Learn how to create search based message extensions for Microsoft Teams using v3  Microsoft 365 Agents SDK (previously known as Bot Framework SDK), handle queries, event handlers, authentication, and SDK support.
 ms.topic: how-to
 ms.localizationpriority: medium
 ms.date: 04/02/2023
@@ -176,7 +176,7 @@ Every request to your message extension is done via an `Activity` object that is
 
 ### Receive user requests
 
-When a user performs a query, Microsoft Teams sends your service a standard Bot Framework `Activity` object. Your service should perform its logic for an `Activity` that has `type` set to `invoke` and `name` set to a supported `composeExtensions` type, as shown in the following table.
+When a user performs a query, Microsoft Teams sends your service a standard  Microsoft 365 Agents SDK (previously known as Bot Framework SDK) `Activity` object. Your service should perform its logic for an `Activity` that has `type` set to `invoke` and `name` set to a supported `composeExtensions` type, as shown in the following table.
 
 In addition to the standard bot activity properties, the payload contains the following request metadata:
 

msteams-platform/resources/schema/manifest-schema-dev-preview.md

@@ -394,7 +394,7 @@ This version string must follow the [semver](http://semver.org/) standard (MAJOR
 
 **Required** – Microsoft app ID
 
-The unique Microsoft-generated identifier for this app. The format of the ID is GUID. If you've registered a bot through Microsoft Bot Framework, or your tab's web app already signs in with Microsoft, then you might already have an ID and must enter it here. Otherwise, you must generate a new ID at the Microsoft Application Registration Portal ([My Applications](https://apps.dev.microsoft.com)), enter it here, and then reuse it when you [add a bot](~/bots/how-to/create-a-bot-for-teams.md).
+The unique Microsoft-generated identifier for this app. The format of the ID is GUID. If you've registered a bot through  Microsoft 365 Agents SDK (previously known as Bot Framework SDK), or your tab's web app already signs in with Microsoft, then you might already have an ID and must enter it here. Otherwise, you must generate a new ID at the Microsoft Application Registration Portal ([My Applications](https://apps.dev.microsoft.com)), enter it here, and then reuse it when you [add a bot](~/bots/how-to/create-a-bot-for-teams.md).
 
 ## developer
 
@@ -599,7 +599,7 @@ The object is an array (maximum of 16 elements) with all elements of the type `o
 |`entityId`|String|64 characters|✔️|A unique identifier for the entity that the tab displays.|
 |`name`|String|128 characters||The display name of the tab.|
 |`contentUrl`|String|2048 characters||The *https://* URL that points to the entity UI to be displayed in the Teams canvas.|
-|`contentBotId`|String| | | The Microsoft Teams app ID specified for the bot in the Bot Framework portal. |
+|`contentBotId`|String| | | The Microsoft Teams app ID specified for the bot in the  Microsoft 365 Agents SDK (previously known as Bot Framework SDK) portal. |
 |`websiteUrl`|String|2048 characters||The *https://* URL to point at if a user opts to view in a browser.|
 |`scopes`|Array of enum|3|✔️|Static tabs support the `personal`, `team`, and `groupChat` scopes, which means it can be provisioned as part of the personal, group chat, and channel meetings experience.|
 |`searchUrl`|String|2048 characters||The *https://* URL to direct a user's search queries.|
@@ -636,7 +636,7 @@ The object is an array (maximum of only 1 element— only one bot is allowed
 
 |Name| Type| Maximum size | Required | Description|
 |---|---|---|---|---|
-|`botId`|String| |✔️|The unique Microsoft app ID for the bot as registered with the Bot Framework. The ID can be the same as the overall [app ID](#id).|
+|`botId`|String| |✔️|The unique Microsoft app ID for the bot as registered with the  Microsoft 365 Agents SDK (previously known as Bot Framework SDK). The ID can be the same as the overall [app ID](#id).|
 |`needsChannelSelector`|Boolean|||Describes whether the bot utilizes a user hint to add the bot to a specific channel. <br>Default value: `false`|
 |`isNotificationOnly`|Boolean|||Indicates whether a bot is a one-way, notification-only bot, as opposed to a conversational bot. <br>Default value: `false`|
 |`supportsFiles`|Boolean|||Indicates whether the bot supports the ability to upload/download files in personal chat. <br>Default value: `false`|
@@ -718,7 +718,7 @@ The object is an array (maximum of 1 element) with all elements of type `object`
 |Name| Type | Maximum Size | Required | Description|
 |---|---|---|---|---|
 |`id`|String||| Unique identifier for the message extension. Used when defining one-way and mutual app capability dependencies under [elementRelationshipSet](#elementrelationshipset).|
-|`botId`|String|||The unique Microsoft app ID for the bot that backs the message extension, as registered with the Bot Framework. The ID can be the same as the overall [app ID](#id).|
+|`botId`|String|||The unique Microsoft app ID for the bot that backs the message extension, as registered with the Microsoft 365 Agents SDK (previously known as Bot Framework SDK). The ID can be the same as the overall [app ID](#id).|
 |`composeExtensionType`|String|||Type of the message extension. Enum values are `botBased` and `apiBased`.|
 |`authorization`|Object|2||Authorization related information for the API-based message extension|
 |`authorization.authType`|String|||Enum of possible authorization types. Supported values are `none`, `apiSecretServiceAuth`, and `microsoftEntra`.|
@@ -1574,7 +1574,7 @@ Defines the content source of a given dashboard card.
 
 |Name| Type| Maximum size | Required | Description|
 |---|---|---|---|---|
-|`botId`| String | | | The unique Microsoft app ID for the bot as registered with the Bot Framework. The ID must be a GUID. |
+|`botId`| String | | | The unique Microsoft app ID for the bot as registered with the Microsoft 365 Agents SDK (previously known as Bot Framework SDK). The ID must be a GUID. |
 
 ## intuneInfo