Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
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
4 changes: 2 additions & 2 deletions msteams-platform/m365-apps/teamsjs-support-m365.md
Original file line number Diff line number Diff line change
Expand Up @@ -1317,7 +1317,7 @@ Preview. Subcapability for interacting with Adaptive Card dialogs.

[Reference](/javascript/api/@microsoft/teams-js/dialog.adaptivecard.bot) | [Known issues](https://github.com/OfficeDev/microsoft-teams-library-js/issues?q=is%3Aissue+dialog.adaptiveCard.bot)

Preview. Subcapability for interaction with Adaptive Card dialogs that need to communicate with the Bot Framework.
Preview. Subcapability for interaction with Adaptive Card dialogs that need to communicate with the Agents SDK.

### `dialog.update`

Expand All @@ -1335,7 +1335,7 @@ Preview. Subcapability for interacting with HTML-based dialogs.

[Reference](/javascript/api/@microsoft/teams-js/dialog.url.bot) | [Known issues](https://github.com/OfficeDev/microsoft-teams-library-js/issues?q=is%3Aissue+dialog.url.bot)

Preview. Subcapability for interacting with HTML-based dialogs that need to communicate with the Bot Framework.
Preview. Subcapability for interacting with HTML-based dialogs that need to communicate with the Agents SDK.

## `geoLocation`

Expand Down
Original file line number Diff line number Diff line change
@@ -1,19 +1,19 @@
---
title: Build Bot-based Message Extensions
author: surbhigupta
description: Learn about Bot-based message extension using Bot Framework to interact with your web service from different locations in the Teams client.
description: Learn about Bot-based message extension using Agents SDK to interact with your web service from different locations in the Teams client.
ms.localizationpriority: medium
ms.topic: overview
ms.author: anclear
ms.owner: slamba
ms.date: 09/16/2024
---

# Build message extensions using Bot Framework
# Build message extensions using Agents SDK

Message extensions built using Bot Framework (Bot-based) use a web service as a bot. You can use message extensions to enable users to interact with your web service from different locations in the Teams client, such as the compose message area, the command box, or directly from a message and send back structured data, such as cards.
Message extensions built using Agents SDK (Bot-based) use a web service as a bot. You can use message extensions to enable users to interact with your web service from different locations in the Teams client, such as the compose message area, the command box, or directly from a message and send back structured data, such as cards.

Bot-based message extension takes advantage of the Bot Framework's messaging schema and secure communication protocol. The bot is defined in the app manifest for the Teams app and you can also define different types of commands for your message extension, such as action commands or search commands.
Bot-based message extension takes advantage of the Agents SDK's messaging schema and secure communication protocol. The bot is defined in the app manifest for the Teams app and you can also define different types of commands for your message extension, such as action commands or search commands.

There are two types of message extension commands, action command and search command. The message extension command type defines the UI elements and interaction flows available to your web service. You can use a search command or an action command to interact with your web service through a bot in Teams.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -669,7 +669,7 @@ The following code section is an example to `fetchTask` response with an Adaptiv

# [C#/.NET](#tab/dotnet)

This sample uses the [AdaptiveCards NuGet package](https://www.nuget.org/packages/AdaptiveCards) in addition to the Bot Framework SDK.
This sample uses the [AdaptiveCards NuGet package](https://www.nuget.org/packages/AdaptiveCards) in addition to the Agents SDK.

```csharp
protected override async Task<MessagingExtensionActionResponse> OnTeamsMessagingExtensionFetchTaskAsync(ITurnContext<IInvokeActivity> turnContext, MessagingExtensionAction action, CancellationToken cancellationToken)
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@ The following image displays the locations from where message extensions can be

## Understand how message extensions work

A message extension is composed of a web service hosted by you and an app manifest that defines the location where your web service is invoked within the Teams client. The web service utilizes the Bot Framework's messaging schema and secure communication protocol, so you must register your web service as a bot in the Bot Framework.
A message extension is composed of a web service hosted by you and an app manifest that defines the location where your web service is invoked within the Teams client. The web service utilizes the Agents SDK's messaging schema and secure communication protocol, so you must register your web service as a bot in the Agents SDK.

> [!NOTE]
> Though it's possible to manually create the web service, we recommend to use [Bot Framework SDK](https://github.com/microsoft/botframework-sdk) to work with the protocol.
Expand Down Expand Up @@ -93,7 +93,7 @@ To build a message extension, if you don't already have one, there are two ways:

* **Build message extensions using API (API-based)**: You can easily create a message extension from an existing API. An OpenAPI Description (OAD) document is required for this method.

* **Build message extensions using Bot Framework (Bot-based)**: If you want a one-on-one conversational experience, you can create a new message extension from a bot.
* **Build message extensions using Agents SDK (Bot-based)**: If you want a one-on-one conversational experience, you can create a new message extension from a bot.

The following table helps you select a message extension type to get started:

Expand All @@ -114,7 +114,7 @@ The following table helps you select a message extension type to get started:
**Bot-based message extension**</br>

* More flexible.
* Message extension uses a Bot Framework.
* Message extension uses a Agents SDK.
* Can use the full capabilities of a bot.
* Ideal for scenarios where the message extension needs to communicate with multiple services, manage complex logic or user interactions, or maintain state across sessions.
* Supports action commands, search commands, and link unfurling.
Expand All @@ -133,7 +133,7 @@ The following table helps you select a message extension type to get started:
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :::image type="content" source="../assets/images/Copilot/build-message-extension-api-tile.png" alt-text="Screenshot shows the OpenAPI icon tile." link="api-based-overview.md" border="false":::
:::column-end:::
:::column span="4":::
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;:::image type="content" source="../assets/images/Copilot/build-message-extension-bot-tile.png" alt-text="Screenshot shows the Bot Framework tile." link="build-bot-based-message-extension.md" border="false":::
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;:::image type="content" source="../assets/images/Copilot/build-message-extension-bot-tile.png" alt-text="Screenshot shows the Agents SDK tile." link="build-bot-based-message-extension.md" border="false":::
:::column-end:::
:::row-end:::

Expand Down