Skip to content

[Doc Improvement] [Rename Bot framework/Bot Framework SDK to Microsoft 365 Agents SDK] #13348

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 5 commits into from
Closed

[Doc Improvement] [Rename Bot framework/Bot Framework SDK to Microsoft 365 Agents SDK] #13348

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
aa5e047
Updated
KirtiJha-MSFT Sep 16, 2025
c027163
Merge branch 'main' into kirtijha-MSFT/renaming-bot-framework26
KirtiJha-MSFT Sep 19, 2025
bb454b4
Updated
KirtiJha-MSFT Sep 19, 2025
3fe5b47
Updated
KirtiJha-MSFT Sep 19, 2025
2d1b334
Revert "Updated"
KirtiJha-MSFT Sep 19, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ The following table provides the features and description of an Incoming Webhook

> [!NOTE]
>
> * Teams bots, message extensions, Incoming Webhook, and the Bot Framework support Adaptive Cards. Adaptive Card is an open cross-card platform framework that is used in all platforms such as Windows, Android, and iOS. [Teams connectors](../../webhooks-and-connectors/how-to/connectors-creating.md) don't support Adaptive Cards. However, it is possible to create a [flow](https://flow.microsoft.com/blog/microsoft-flow-in-microsoft-teams/) that posts Adaptive Cards to a Teams channel.
> * Teams bots, message extensions, Incoming Webhook, and the Microsoft 365 Agents SDK (previously known as Bot Framework SDK) support Adaptive Cards. Adaptive Card is an open cross-card platform framework that is used in all platforms such as Windows, Android, and iOS. [Teams connectors](../../webhooks-and-connectors/how-to/connectors-creating.md) don't support Adaptive Cards. However, it is possible to create a [flow](https://flow.microsoft.com/blog/microsoft-flow-in-microsoft-teams/) that posts Adaptive Cards to a Teams channel.
> * For more information on cards and webhooks, see [Adaptive Cards and Incoming Webhooks](~/task-modules-and-cards/what-are-cards.md#adaptive-cards-and-incoming-webhooks).

## Create an Incoming Webhook
Expand Down
5 changes: 3 additions & 2 deletions msteams-platform/webhooks-and-connectors/how-to/add-outgoing-webhook.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ The following table provides the features and description of Outgoing Webhooks:
| ------- | ----------- |
| Scoped configuration| Webhooks are scoped at the team level. Mandatory setup process for each adds an Outgoing Webhook. |
| Reactive messaging| Users must use **@mention** for the webhook to receive messages. The users can only message an Outgoing Webhook in public channels and not within the personal or private scope. |
|Standard HTTP message exchange|Responses appear in the same chain as the original request message and can include any Bot Framework message content. For example, rich text, images, cards, and emojis. Although Outgoing Webhooks can use cards, they can't use any card actions except for `openURL`.|
|Standard HTTP message exchange|Responses appear in the same chain as the original request message and can include any Microsoft 365 Agents SDK (previously known as Bot Framework SDK) message content. For example, rich text, images, cards, and emojis. Although Outgoing Webhooks can use cards, they can't use any card actions except for `openURL`.|
| Teams API method support|Outgoing Webhooks sends an HTTP POST to a web service and gets a response. They can't access any other APIs, such as retrieve the roster or list of channels in a team.|

## Create Outgoing Webhooks
Expand Down Expand Up @@ -78,7 +78,8 @@ The following scenario provides the details to add an Outgoing Webhook:

**Create a URL on your app's server to accept and process a POST request with a JSON payload**

Your service receives messages in a standard Azure bot service messaging schema. The Bot Framework connector is a RESTful service that empowers to process the interchange of JSON formatted messages through HTTPS protocols as documented in the [Azure Bot Service API](/bot-framework/rest-api/bot-framework-rest-connector-api-reference). Alternatively, you can follow the Microsoft Bot Framework SDK to process and parse messages. For more information, see [overview of Azure Bot Service](/azure/bot-service/bot-service-overview-introduction).
Your service receives messages in a standard Azure bot service messaging schema. The Microsoft 365 Agents SDK (previously known as Bot Framework SDK) connector is a RESTful service that empowers to process the interchange of JSON formatted messages through HTTPS protocols as documented in the [Azure Bot Service API](/bot-framework/rest-api/bot-framework-rest-connector-api-reference). Alternatively, you can follow the Microsoft 365 Agents SDK (previously known as Bot Framework SDK)
to process and parse messages. For more information, see [overview of Azure Bot Service](/azure/bot-service/bot-service-overview-introduction).

Outgoing Webhooks are scoped to the `team` level and are visible to all the team members. Users need to **@mention** the name of the Outgoing Webhook to invoke it in the channel.

Expand Down
2 changes: 1 addition & 1 deletion msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,7 @@ Before you start to learn how to build Incoming Webhooks, you may also want to k
| Send a welcome message | Yes | Yes | No |
| Trigger supported |All triggers are supported. | All triggers are supported. <br> If you use Agents Toolkit, you can quickly get a template project with the following triggers: <br> • Time trigger hosted on Azure functions. <br> • Express HTTP trigger hosted on Azure app service. <br> • HTTP trigger hosted on Azure Functions.| All triggers are supported.|
| Building Tools |[Quick start - Microsoft Graph](https://developer.microsoft.com/graph/quick-start) | • [Agents Toolkit Overview for Visual Studio Code](../toolkit/agents-toolkit-fundamentals.md) <br> • [Agents Toolkit Overview for Visual Studio](../toolkit/toolkit-v4/agents-toolkit-fundamentals-vs.md) <br> • [Microsoft 365 Agents Toolkit CLI](../toolkit/microsoft-365-agents-toolkit-CLI.md) <br> • [TeamsFx SDK](../toolkit/TeamsFx-SDK.md) | No tools are required. |
| Cloud resource required | Microsoft Entra app | Azure Bot Framework | No resources are required. |
| Cloud resource required | Microsoft Entra app | Microsoft 365 Agents SDK (previously known as Bot Framework SDK) | No resources are required. |
| Tutorial | • [Send activity feed notifications to users in Microsoft Teams](/graph/teams-send-activityfeednotifications) <br> • [Send activity feed notification](../sbs-graphactivity-feedbroadcast.yml) | [Build notification bot with JavaScript](../sbs-gs-notificationbot.yml) | [Incoming Webhook notification sample](https://github.com/OfficeDev/TeamsFx-Samples/tree/dev/incoming-webhook-notification) |

### Connectors for Microsoft 365 Groups
Expand Down