| Service | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| platform | Bot Basics | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/bots/bot-basics.md | To implement your logic for Teams specific activity handlers, you must override The code snippets for Teams activity handlers: -`OnTeamsChannelCreatedAsync` +`onTeamsChannelCreated` ```javascript onTeamsChannelCreated(async (channelInfo, teamInfo, context, next) => { }); ``` -`OnTeamsChannelDeletedAsync` +`onTeamsChannelDeleted` ```javascript onTeamsChannelDeleted(async (channelInfo, teamInfo, context, next) => { }); ``` -`OnTeamsChannelRenamedAsync` +`onTeamsChannelRenamed` ```javascript onTeamsChannelRenamed(async (channelInfo, teamInfo, context, next) => { }); ``` -`OnTeamsTeamRenamedAsync` +`onTeamsTeamRenamed` ```javascript onTeamsTeamRenamedAsync(async (teamInfo, context, next) => { }); ``` -`OnTeamsMembersAddedAsync` +`onTeamsMembersAdded` ```javascript onTeamsMembersAdded(async (membersAdded, teamInfo, context, next) => { }); ``` -`OnTeamsMembersRemovedAsync` +`onTeamsMembersRemoved` ```javascript The list of Teams activity handlers called from the `OnInvokeActivityAsync` Team | fileConsent/invoke | `OnTeamsFileConsentAcceptAsync` | This method is invoked when a file consent card is accepted by the user. | | fileConsent/invoke | `OnTeamsFileConsentAsync` | This method is invoked when a file consent card activity is received from the connector. | | fileConsent/invoke | `OnTeamsFileConsentDeclineAsync` | This method is invoked when a file consent card is declined by the user. |-| actionableMessage/executeAction | `OnTeamsO365ConnectorCardActionAsync` | This method is invoked when an Office 365 connector card action activity is received from the connector. | +| actionableMessage/executeAction | `OnTeamsO365ConnectorCardActionAsync` | This method is invoked when a connector card for Microsoft 365 Groups action activity is received from the connector. | | signin/verifyState | `OnTeamsSigninVerifyStateAsync` | This method is invoked when a signIn verify state activity is received from the connector. | | task/fetch | `OnTeamsTaskModuleFetchAsync` | This method can be overridden in a derived class to provide logic when a task module is fetched. | | task/submit | `OnTeamsTaskModuleSubmitAsync` | This method can be overridden in a derived class to provide logic when a task module is submitted. | The `TeamsActivityHandler` extends the list of handlers in the core Bot Framewor | Event | Handler | Description | | :-- | :-- | :-- |-| channelCreated | `OnTeamsChannelCreatedAsync` | This method can be overridden to handle a Teams channel being created. For more information, see [channel created](https://aka.ms/azure-bot-subscribe-to-conversation-events#channel-created) in [conversation update events](https://aka.ms/azure-bot-subscribe-to-conversation-events). | -| channelDeleted | `OnTeamsChannelDeletedAsync` | This method can be overridden to handle a Teams channel being deleted. For more information, see [channel deleted](https://aka.ms/azure-bot-subscribe-to-conversation-events#channel-deleted) in [conversation update events](https://aka.ms/azure-bot-subscribe-to-conversation-events).| -| channelRenamed | `OnTeamsChannelRenamedAsync` | This method can be overridden to handle a Teams channel being renamed. For more information, see [channel renamed](https://aka.ms/azure-bot-subscribe-to-conversation-events#channel-renamed) in [conversation update events](https://aka.ms/azure-bot-subscribe-to-conversation-events). | -| teamRenamed | `OnTeamsTeamRenamedAsync` | `return Task.CompletedTask;` This method can be overridden to handle a Teams team being renamed. For more information, see [team renamed](https://aka.ms/azure-bot-subscribe-to-conversation-events#team-renamed) in [conversation update events](https://aka.ms/azure-bot-subscribe-to-conversation-events). | -| MembersAdded | `OnTeamsMembersAddedAsync` | This method calls the `OnMembersAddedAsync` method in `ActivityHandler`. The method can be overridden to handle members joining a team. For more information, see [team members added](https://aka.ms/azure-bot-subscribe-to-conversation-events#team-members-added) in [conversation update events](https://aka.ms/azure-bot-subscribe-to-conversation-events). | -| MembersRemoved | `OnTeamsMembersRemovedAsync` | This method calls the `OnMembersRemovedAsync` method in `ActivityHandler`. The method can be overridden to handle members leaving a team. For more information, see [team members removed](https://aka.ms/azure-bot-subscribe-to-conversation-events#team-members-removed) in [conversation update events](https://aka.ms/azure-bot-subscribe-to-conversation-events). | +| channelCreated | `onTeamsChannelCreated` | This method can be overridden to handle a Teams channel being created. For more information, see [channel created](https://aka.ms/azure-bot-subscribe-to-conversation-events#channel-created) in [conversation update events](https://aka.ms/azure-bot-subscribe-to-conversation-events). | +| channelDeleted | `onTeamsChannelDeleted` | This method can be overridden to handle a Teams channel being deleted. For more information, see [channel deleted](https://aka.ms/azure-bot-subscribe-to-conversation-events#channel-deleted) in [conversation update events](https://aka.ms/azure-bot-subscribe-to-conversation-events).| +| channelRenamed | `onTeamsChannelRenamed` | This method can be overridden to handle a Teams channel being renamed. For more information, see [channel renamed](https://aka.ms/azure-bot-subscribe-to-conversation-events#channel-renamed) in [conversation update events](https://aka.ms/azure-bot-subscribe-to-conversation-events). | +| teamRenamed | `onTeamsTeamRenamed` | `return Task.CompletedTask;` This method can be overridden to handle a Teams team being renamed. For more information, see [team renamed](https://aka.ms/azure-bot-subscribe-to-conversation-events#team-renamed) in [conversation update events](https://aka.ms/azure-bot-subscribe-to-conversation-events). | +| MembersAdded | `onTeamsMembersAdded` | This method calls the `OnMembersAddedAsync` method in `ActivityHandler`. The method can be overridden to handle members joining a team. For more information, see [team members added](https://aka.ms/azure-bot-subscribe-to-conversation-events#team-members-added) in [conversation update events](https://aka.ms/azure-bot-subscribe-to-conversation-events). | +| MembersRemoved | `onTeamsMembersRemoved` | This method calls the `OnMembersRemovedAsync` method in `ActivityHandler`. The method can be overridden to handle members leaving a team. For more information, see [team members removed](https://aka.ms/azure-bot-subscribe-to-conversation-events#team-members-removed) in [conversation update events](https://aka.ms/azure-bot-subscribe-to-conversation-events). | #### Teams invoke activities The list of Teams activity handlers called from the `onInvokeActivity` Teams act | fileConsent/invoke | `handleTeamsFileConsentAccept` | This method is invoked when a file consent card is accepted by the user. | | fileConsent/invoke | `handleTeamsFileConsent` | This method is invoked when a file consent card activity is received from the connector. | | fileConsent/invoke | `handleTeamsFileConsentDecline` | This method is invoked when a file consent card is declined by the user. |-| actionableMessage/executeAction | `handleTeamsO365ConnectorCardAction` | This method is invoked when an Office 365 connector card action activity is received from the connector. | +| actionableMessage/executeAction | `handleTeamsO365ConnectorCardAction` | This method is invoked when a connector card for Microsoft 365 Groups action activity is received from the connector. | | signin/verifyState | `handleTeamsSigninVerifyState` | This method is invoked when a signIn verify state activity is received from the connector. | | task/fetch | `handleTeamsTaskModuleFetch` | This method can be overridden in a derived class to provide logic when a task module is fetched. | | task/submit | `handleTeamsTaskModuleSubmit` | This method can be overridden in a derived class to provide logic when a task module is submitted. | The list of Teams activity handlers called from the `on_invoke_activity` Teams a | fileConsent/invoke | `on_teams_file_consent_accept` | This method is invoked when a file consent card is accepted by the user. | | fileConsent/invoke | `on_teams_file_consent` | This method is invoked when a file consent card activity is received from the connector. | | fileConsent/invoke | `on_teams_file_consent_decline` | This method is invoked when a file consent card is declined by the user. |-| actionableMessage/executeAction | `on_teams_o365_connector_card_action` | This method is invoked when an Office 365 connector card action activity is received from the connector. | +| actionableMessage/executeAction | `on_teams_o365_connector_card_action` | This method is invoked when a connector card for Microsoft 365 Groups action activity is received from the connector. | | signin/verifyState | `on_teams_signin_verify_state` | This method is invoked when a signIn verify state activity is received from the connector. | | task/fetch | `on_teams_task_module_fetch` | This method can be overridden in a derived class to provide logic when a task module is fetched. | | task/submit | `on_teams_task_module_submit` | This method can be overridden in a derived class to provide logic when a task module is submitted. | |
| platform | Bot Features | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/bots/bot-features.md | Title: Bots and SDKs -description: In this article, learn about tools and Bot Framework SDKs(C#, Python, Java, JavaScript) for Microsoft Teams bots and it's advantages and disadvantages. +description: In this article, learn about tools and Bot Framework SDKs(C#, Python, Java, JavaScript) for Microsoft Teams bots and its advantages and disadvantages. ms.localizationpriority: medium Your Teams bot consists of the following: The [Bot Framework](https://dev.botframework.com/) is a rich SDK used to create bots using C#, Java, Python, and JavaScript. If you already have a bot that is based on the Bot Framework, you can easily modify it to work in Teams. Use either C# or Node.js to take advantage of our [SDKs](/microsoftteams/platform/#pivot=sdk-tools). These packages extend the basic Bot Builder SDK classes and methods as follows: -* Use specialized card types like the Office 365 connector card. +* Use specialized card types like the connector card for Microsoft 365 Groups. * Set Teams-specific channel data on activities. * Process message extension requests. Bots in Microsoft Teams can be part of a one-to-one conversation, a group chat, ### In a channel -Channels contain threaded conversations between multiple people even up to two thousand. This potentially gives your bot massive reach, but individual interactions must be concise. Traditional multi-turn interactions don't work. Instead, you must look to use interactive cards or task modules, or move the conversation to a one-to-one conversation to collect lots of information. Your bot only has access to messages where it's `@mentioned`. You can retrieve additional messages from the conversation using Microsoft Graph and organization-level permissions. +Channels contain threaded conversations between multiple people even up to 2000. This potentially gives your bot massive reach, but individual interactions must be concise. Traditional multi-turn interactions don't work. Instead, you must look to use interactive cards or task modules, or move the conversation to a one-to-one conversation to collect lots of information. Your bot only has access to messages where it's `@mentioned`. You can retrieve additional messages from the conversation using Microsoft Graph and organization-level permissions. Bots work better in a channel in the following cases: An extensive dialog between your bot and the user is a slow and complex way to g ### Have multi-turn experiences in chat -An extensive dialog requires the developer to maintain state. To exit this state, a user must either timeout or select **Cancel**. Also, the process is tedious. For example, see the following conversation scenario: +An extensive dialog requires the developer to maintain state. To exit this state, a user must either time out or select **Cancel**. Also, the process is tedious. For example, see the following conversation scenario: USER: Schedule a meeting with Megan. -BOT: IΓÇÖve found 200 results, please include a first and last name. +BOT: IΓÇÖve found 200 results, include a first and last name. USER: Schedule a meeting with Megan Bowen. |
| platform | App Fundamentals Overview | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/concepts/app-fundamentals-overview.md | The following list helps to identify the availability of GCC, GCC-High, and DOD * For third-party apps, see [web apps](../samples/integrating-web-apps.md) and [meeting app extensibility](../apps-in-teams-meetings/teams-apps-in-meetings.md). * For bots, see [build your first conversational bot for Teams](../get-started/first-app-bot.md), [designing your Teams bot](../bots/design/bots.md), [add bots to Microsoft Teams apps](../resources/bot-v3/bots-overview.md), and [bots in Teams](../bots/what-are-bots.md). * For sideloading apps, see [enable your Teams app to be customized](../concepts/design/enable-app-customization.md), [distribute your Microsoft Teams app](../concepts/deploy-and-publish/apps-publish-overview.md), and [Upload your app in Teams](../concepts/deploy-and-publish/apps-upload.md).-* For custom connectors, see [create Office 365 connectors for Teams](../webhooks-and-connectors/how-to/connectors-creating.md). +* For custom connectors, see [create connectors for Microsoft 365 Groups for Teams](../webhooks-and-connectors/how-to/connectors-creating.md). </details> |
| platform | Deep Link Application | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/concepts/build-and-test/deep-link-application.md | ms.localizationpriority: high Application can open the profile dialog through deep links and help users to learn more about the application, permissions, and more. You can create a deep link for the app after the app is listed in the Teams store. To create a link to launch Teams, append the app ID to the URL, `https://teams.microsoft.com/l/app/<your-app-id>`. A dialog appears to install or open the app. -> [!NOTE] -> If your app is approved for mobile platform, you can deep link to an app on mobile. Apple App Store Connect Team ID is required additionally for the deep link to work on Teams-iOS. For more information, see [how to update Apple App Store Connect Team ID](../deploy-and-publish/appsource/prepare/update-apple-store-team-connect-id.md). +If your app is approved for mobile platform, you can deep link to an app on mobile. Apple App Store Connect Team ID is required additionally for the deep link to work on Teams-iOS. For more information, see [how to update Apple App Store Connect Team ID](../deploy-and-publish/appsource/prepare/update-apple-store-team-connect-id.md). ++Deep link to an app isn't supported for custom apps. [!INCLUDE [sdk-include](~/includes/sdk-include.md)] |
| platform | Deep Link Teams | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/concepts/build-and-test/deep-link-teams.md | ms.localizationpriority: high # Deep link to Teams chat -You can navigate to or create private chats between users with Teams Java Script library by specifying the set of participants. If a chat doesnΓÇÖt exist with the specified participants, the user is navigated to an empty new chat. New chats are created in draft state until the user sends the first message. Otherwise, you can specify the name of the chat if it doesnΓÇÖt already exist, along with text that should be inserted into the user's compose box. You can think of this feature as a shortcut for the user taking the manual action of navigating to or creating the chat, and then typing out the message. +You can navigate to or create private chats between users with TeamsJS library by specifying the set of participants. If a chat doesnΓÇÖt exist with the specified participants, the user is navigated to an empty new chat. New chats are created in draft state until the user sends the first message. Otherwise, you can specify the name of the chat if it doesnΓÇÖt already exist, along with text that should be inserted into the user's compose box. You can think of this feature as a shortcut for the user taking the manual action of navigating to or creating the chat, and then typing out the message. -As an use-case example , if youΓÇÖre returning an Office 365 user profile from your bot as a card, this deep link can allow the user to easily chat with that person. The following example demonstrates how to open a chat message to a group of participants with an initial message. +As a use-case example, if youΓÇÖre returning a Microsoft 365 user profile from your bot as a card, this deep link can allow the user to easily chat with that person. The following example demonstrates how to open a chat message to a group of participants with an initial message. ```javascript if(chat.isSupported()) { |
| platform | Glossary | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/get-started/glossary.md | Common terms and definitions used in Microsoft Teams developer documentation. | [OAuth card](../bots/how-to/authentication/bot-sso-code.md) | A card used by an app to represent a request to perform a sign-in via OAuth. <br> [SSO](#s); [TokenExchangeResource property](#t) | | [OAuth connection](../bots/how-to/authentication/bot-sso-register-aad.md) | It's configured as a part of bot resource configuration for SSO authentication after its registered on Azure AD. It contains details about the identity provider, client secret, and so on. <br> **See also**: [SSO](#s); [Connector name](#c); [Identity provider](#i); [Client secret](#c); [Azure Active Directory](#a) | | [Object ID](../bots/how-to/authentication/bot-sso-register-aad.md) | The unique identifier created by Azure AD portal when you register or update your app. It identifies the application object, which defines the application's identity configuration globally (across all tenants where it has access). <br> **See also**: [Application ID](#a); [Tenant ID](#t); [SSO](#s) |-| [Office 365 Connector](../webhooks-and-connectors/how-to/connectors-creating.md) | It lets you create a custom configuration page for your Incoming Webhook and package them as part of a Teams app. You can send messages primarily using Office 365 Connector cards and have the ability to add a limited set of card actions to them. | +| [Connector for Microsoft 365 Groups](../webhooks-and-connectors/how-to/connectors-creating.md) | It lets you create a custom configuration page for your Incoming Webhook and package them as part of a Teams app. You can send messages primarily using connector cards for Microsoft 365 Groups and have the ability to add a limited set of card actions to them. | | [Outgoing Webhook](../webhooks-and-connectors/how-to/add-outgoing-webhook.md) | It acts as a bot and search for messages in channels using @mention. It sends notifications to external web services and responds with rich messages, which include cards and images. <br>**See also**: [Webhook](#w); [Incoming Webhook](#i) | | [One-on-one chat](../resources/bot-v3/bot-conversations/bots-conv-personal.md) | A type of chat between a Teams personal bot app and a single user. <br>**See also**: [Group chat](#g); [Chat bot](#c) | |
| platform | Link Unfurling | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/messaging-extensions/how-to/link-unfurling.md | The following card types are supported: * [Thumbnail card](~/task-modules-and-cards/cards/cards-reference.md#thumbnail-card) * [Hero card](~/task-modules-and-cards/cards/cards-reference.md#hero-card)-* [Office 365 Connector card](~/task-modules-and-cards/cards/cards-reference.md#office-365-connector-card) +* [Connector card for Microsoft 365 Groups](../../task-modules-and-cards/cards/cards-reference.md#connector-card-for-microsoft-365-groups) * [Adaptive Card](~/task-modules-and-cards/cards/cards-reference.md#adaptive-card) For more information, see [Action type invoke](~/task-modules-and-cards/cards/cards-actions.md#action-type-invoke). Following is an example of the response: } } ```+ ## Zero install for link unfurling To get your app ready for zero install link unfurling, follow these steps: > [!NOTE] > After the link is pasted in the message compose area, Teams unfurls the link into a card and prompts the user to sign in to the app. If the user doesn't sign in to the app, the link isn't posted as a card in the chat. -1. Advantages and limitations. +1. **Advantages and limitations**: # [Advantages](#tab/advantages) To get your app ready for zero install link unfurling, follow these steps: * The bot can only send back a response as `result` or `auth` as the value for the `type` property in response to the `composeExtension/anonymousQueryLink` invoke request. The user can log an error for all other response types, such as, *silentAuth* and *config*. - * The bot can't send back an acv2 card in response to the `composeExtension/anonymousQueryLink` invoke request, either as a result or as a pre-auth card in auth. + * The bot can't send back an acv2 card in response to the `composeExtension/anonymousQueryLink` invoke request, either as a result or as a pre-auth card in auth. - * If the bot selects to send back the `"type": "auth"` with a pre-auth card, the Teams client strips away any action buttons from the card, and adds a sign in action button to get users to authenticate into your app. + * If the bot selects to send back the `"type": "auth"` with a pre-auth card, the Teams client strips away any action buttons from the card, and adds a sign in action button to get users to authenticate into your app. ## Remove link unfurling cache |
| platform | Respond To Search | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/messaging-extensions/how-to/search-commands/respond-to-search.md | The request parameters are found in the `value` object in the request, which inc | `queryOptions` | Pagination parameters: <br>`skip`: Skip count for this query <br>`count`: Number of elements to return. | # [C#/.NET](#tab/dotnet)+ * [SDK reference](/dotnet/api/microsoft.bot.builder.teams.teamsactivityhandler.onteamsmessagingextensionqueryasync?view=botbuilder-dotnet-stable#microsoft-bot-builder-teams-teamsactivityhandler-onteamsmessagingextensionqueryasync(microsoft-bot-builder-iturncontext((microsoft-bot-schema-iinvokeactivity))-microsoft-bot-schema-teams-messagingextensionquery-system-threading-cancellationtoken)&preserve-view=true) * [Sample code reference](https://github.com/OfficeDev/Microsoft-Teams-Samples/blob/main/samples/msgext-link-unfurling/csharp/Bots/LinkUnfurlingBot.cs#L32) Teams supports the following card types: * [Thumbnail card](~/task-modules-and-cards/cards/cards-reference.md#thumbnail-card) * [Hero card](~/task-modules-and-cards/cards/cards-reference.md#hero-card)-* [Office 365 Connector card](~/task-modules-and-cards/cards/cards-reference.md#office-365-connector-card) +* [Connector card for Microsoft 365 Groups](~/task-modules-and-cards/cards/cards-reference.md#connector-card-for-microsoft-365-groups) * [Adaptive Card](~/task-modules-and-cards/cards/cards-reference.md#adaptive-card) To have a better understanding and overview on cards, see [what are cards](~/task-modules-and-cards/what-are-cards.md). To learn how to use the thumbnail and hero card types, see [add cards and card actions](~/task-modules-and-cards/cards/cards-actions.md). -For additional information about the Office 365 Connector card, see [Using Office 365 Connector cards](~/task-modules-and-cards/cards/cards-reference.md#office-365-connector-card). +For additional information about the connector card for Microsoft 365 Groups, see [Using connector cards for Microsoft 365 Groups](~/task-modules-and-cards/cards/cards-reference.md#connector-card-for-microsoft-365-groups). The result list is displayed in the Microsoft Teams UI with a preview of each item. The preview is generated in one of the two ways: The result list is displayed in the Microsoft Teams UI with a preview of each it For Hero or Thumbnail card, except the invoke action other actions such as button and tap aren't supported in the preview card. -To send an Adaptive Card or Office 365 Connector card, you must include a preview. The `preview` property must be a Hero or Thumbnail card. If you don't specify the preview property in the `attachment` object, a preview isn't generated. +To send an Adaptive Card or connector card for Microsoft 365 Groups, you must include a preview. The `preview` property must be a Hero or Thumbnail card. If you don't specify the preview property in the `attachment` object, a preview isn't generated. For Hero and Thumbnail cards, you don't need to specify a preview property, a preview is generated by default. class TeamsMessagingExtensionsSearchBot extends TeamsActivityHandler { ### Enable and handle tap actions # [C#/.NET](#tab/dotnet)+ * [Sample code reference](https://github.com/OfficeDev/Microsoft-Teams-Samples/blob/main/samples/msgext-search/csharp/Bots/TeamsMessagingExtensionsSearchBot.cs#L80) ```csharp |
| platform | Bots Overview | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/resources/bot-v3/bots-overview.md | With Teams apps, you can make the bot the star of your experience, or just a hel Teams supports most of the [Microsoft Bot Framework](https://dev.botframework.com/). (If you already have a bot that's based on the Bot Framework, you can easily adapt it to work in Teams.) We recommend you use either C# or Node.js to take advantage of our [SDKs](/microsoftteams/platform/#pivot=sdk-tools). These packages extend the basic Bot Builder SDK classes and methods: -* Using specialized card types like the Office 365 Connector card. +* Using specialized card types like the connector card for Microsoft 365 Groups. * Consuming and setting Teams-specific channel data on activities. * Processing message extension requests. |
| platform | Search Extensions | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/resources/messaging-extension-v3/search-extensions.md | We support the following attachment types: * [Thumbnail card](~/task-modules-and-cards/cards/cards-reference.md#thumbnail-card) * [Hero card](~/task-modules-and-cards/cards/cards-reference.md#hero-card)-* [Office 365 Connector card](~/task-modules-and-cards/cards/cards-reference.md#office-365-connector-card) +* [Connector card for Microsoft 365 Groups](~/task-modules-and-cards/cards/cards-reference.md#connector-card-for-microsoft-365-groups) * [Adaptive card](~/task-modules-and-cards/cards/cards-reference.md#adaptive-card) For more information, see [Cards](~/task-modules-and-cards/what-are-cards.md) for an overview. To learn how to use the thumbnail and hero card types, see [Add cards and card actions](~/task-modules-and-cards/cards/cards-actions.md). -For additional documentation regarding the Office 365 Connector card, see [Using Office 365 Connector cards](~/task-modules-and-cards/cards/cards-reference.md#office-365-connector-card). +For additional documentation regarding the connector card for Microsoft 365 Groups, see [Using connector card for Microsoft 365 Groups](~/task-modules-and-cards/cards/cards-reference.md#connector-card-for-microsoft-365-groups). The result list is displayed in the Microsoft Teams UI with a preview of each item. The preview is generated in one of two ways: * Using the `preview` property within the `attachment` object. The `preview` attachment can only be a Hero or Thumbnail card. * Extracted from the basic `title`, `text`, and `image` properties of the attachment. These are used only if the `preview` property isn't set and these properties are available. -You can display a preview of an Adaptive or Office 365 Connector card in the result list simply by setting its preview property. This isn't necessary if the results are already hero or thumbnail cards. If you use the preview attachment, it must be either a Hero or Thumbnail card. If no preview property is specified, the preview of the card will fail, and nothing will be displayed. +You can display a preview of an Adaptive or connector card for Microsoft 365 Groups in the result list simply by setting its preview property. This isn't necessary if the results are already hero or thumbnail cards. If you use the preview attachment, it must be either a Hero or Thumbnail card. If no preview property is specified, the preview of the card will fail, and nothing will be displayed. #### Response example -This example shows a response with two results, mixing different card formats: Office 365 Connector and Adaptive. While you'll likely want to stick with one card format in your response, it shows how the `preview` property of each element in the `attachments` collection must explicitly define a preview in hero or thumbnail format as described above. +This example shows a response with two results, mixing different card formats: Connector for Microsoft 365 Groups and Adaptive. While you'll likely want to stick with one card format in your response, it shows how the `preview` property of each element in the `attachments` collection must explicitly define a preview in hero or thumbnail format as described above. ```json { app.run(); ## See also -[Bot Framework samples](https://github.com/OfficeDev/Microsoft-Teams-Samples/blob/main/README.md). +[Bot Framework samples](https://github.com/OfficeDev/Microsoft-Teams-Samples/blob/main/README.md). |
| platform | Manifest Schema Dev Preview | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/resources/schema/manifest-schema-dev-preview.md | An optional list of commands that your bot can recommend to users. The object is Optional: -The `connectors` block defines an Office 365 Connector for the app. +The `connectors` block defines a connector for Microsoft 365 Groups for the app. The object is an array (maximum of 1 element) with all elements of type `object`. This block is required only for solutions that provide a Connector. |
| platform | Manifest Schema | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/resources/schema/manifest-schema.md | A list of commands that your bot can recommend to users. The object is an array **Optional**ΓÇöarray -The `connectors` block defines an Office 365 Connector for the app. +The `connectors` block defines a connector card for Microsoft 365 Groups for the app. The object is an array (maximum of one element) with all elements of type `object`. This block is required only for solutions that provide a Connector. |
| platform | Integrating Web Apps | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/samples/integrating-web-apps.md | Your Teams app must include required and expected collaborative features. To wor |Share shortcuts and extensions |[Message extensions](../messaging-extensions/what-are-messaging-extensions.md) | |Action shortcuts and extensions |[Message extensions](../messaging-extensions/what-are-messaging-extensions.md) | |Chatbots |[Bots](../bots/what-are-bots.md) |-|Channel notifications |[Bots](../bots/what-are-bots.md)<br/>[Incoming Webhooks](../webhooks-and-connectors/what-are-webhooks-and-connectors.md)<br/>[Office 365 Connectors](../webhooks-and-connectors/what-are-webhooks-and-connectors.md) | +|Channel notifications |[Bots](../bots/what-are-bots.md)<br/>[Incoming Webhooks](../webhooks-and-connectors/what-are-webhooks-and-connectors.md)<br/>[connectors for Microsoft 365 Groups](../webhooks-and-connectors/what-are-webhooks-and-connectors.md) | |Message external services |[Bots](../bots/what-are-bots.md)<br/>[Outgoing Webhooks](../webhooks-and-connectors/what-are-webhooks-and-connectors.md) | |Modals |[Task modules](../task-modules-and-cards/what-are-task-modules.md) | |Content-rich cards |[Adaptive Cards](../task-modules-and-cards/what-are-cards.md) | |
| platform | Access Teams Context | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/tabs/how-to/access-teams-context.md | Use placeholders in your configuration or content URLs. Microsoft Teams replaces * [{user.userPrincipalName}](/javascript/api/@microsoft/teams-js/app.userinfo#@microsoft-teams-js-app-userinfo-userprincipalname): The User Principal Name of the current user in the current tenant. (Known as `{userPrincipalName}` prior to TeamsJS v.2.0.0). * [{user.id}](/javascript/api/@microsoft/teams-js/app.userinfo#@microsoft-teams-js-app-userinfo-id): The Azure AD object ID of the current user in the current tenant. (Known as `{userObjectId}` prior to TeamsJS v.2.0.0). * [{app.theme}](/javascript/api/@microsoft/teams-js/app.appinfo#@microsoft-teams-js-app-appinfo-theme): The current user interface (UI) theme such as `default`, `dark`, or `contrast`. (Known as `{theme}` prior to TeamsJS v.2.0.0).-* [{team.groupId}](/javascript/api/@microsoft/teams-js/app.teaminfo#@microsoft-teams-js-app-teaminfo-groupid): The ID of the Office 365 group in which the tab resides. (Known as `{groupId}` prior to TeamsJS v.2.0.0) +* [{team.groupId}](/javascript/api/@microsoft/teams-js/app.teaminfo#@microsoft-teams-js-app-teaminfo-groupid): The ID of the Microsoft 365 group in which the tab resides. (Known as `{groupId}` prior to TeamsJS v.2.0.0) * [{user.tenant.id}](/javascript/api/@microsoft/teams-js/app.tenantinfo#@microsoft-teams-js-app-tenantinfo-id): The Azure AD tenant ID of the current user. (Known as `{tid}` prior to TeamsJS v.2.0.0). * [{app.locale}](/javascript/api/@microsoft/teams-js/app.appinfo#@microsoft-teams-js-app-appinfo-locale): The current locale of the user formatted as *languageId-countryId*, for example `en-us`. (Known as `{locale}` prior to TeamsJS v.2.0.0). |
| platform | Configuration Page | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/tabs/how-to/create-tab-pages/configuration-page.md | A configuration page is a special type of [content page](content-page.md). The u * A channel or group chat tab: Collect information from the users and set the `contentUrl` of the content page to be displayed. * A [message extension](~/messaging-extensions/what-are-messaging-extensions.md).-* An [Office 365 Connector](~/webhooks-and-connectors/what-are-webhooks-and-connectors.md). +* A [connector for Microsoft 365 Groups](~/webhooks-and-connectors/what-are-webhooks-and-connectors.md). [!INCLUDE [sdk-include](~/includes/sdk-include.md)] If you choose to have your channel or group tab appear on the Teams mobile clien * [Build tabs for Teams](../../what-are-tabs.md) * [Update manifest for SSO and preview app](../authentication/tab-sso-manifest.md) * [Configure third party OAuth IdP authentication](../authentication/auth-tab-aad.md)-* [Create Office 365 Connectors](../../../webhooks-and-connectors/how-to/connectors-creating.md) +* [Create connectors for Microsoft 365 Groups](../../../webhooks-and-connectors/how-to/connectors-creating.md) * [Get context for your tab](../access-teams-context.md) * [Tabs on mobile](../../design/tabs-mobile.md) |
| platform | What Are Tabs | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/tabs/what-are-tabs.md | There are few prerequisites that you must go through before working on tabs. There are two types of tabs available in Teams, personal and channel or group. [Personal tabs](~/tabs/how-to/create-personal-tab.md), along with personal-scoped bots, are part of personal apps and are scoped to a single user. They can be pinned to the left navigation bar for easy access. [Channel or group tabs](~/tabs/how-to/create-channel-group-tab.md) deliver content to channels and group chats, and are a great way to create collaborative spaces around dedicated web-based content. -You can [create a content page](~/tabs/how-to/create-tab-pages/content-page.md) as part of a personal tab, channel or group tab, or task module. You can [create a configuration page](~/tabs/how-to/create-tab-pages/configuration-page.md) that enables users to configure Microsoft Teams app and use it to configure a channel or group chat tab, a messaging extension, or an Office 365 Connector. You can permit users to reconfigure your tab after installation and [create a tab removal page](~/tabs/how-to/create-tab-pages/removal-page.md) for your application. When you build a Teams app that includes a tab, you must test how your [tab functions on both the Android and iOS Teams clients](~/tabs/design/tabs-mobile.md). Your tab must [get context](~/tabs/how-to/access-teams-context.md) through basic information, locale and theme information, and `entityId` or `subEntityId` that identifies what is in the tab. +You can [create a content page](~/tabs/how-to/create-tab-pages/content-page.md) as part of a personal tab, channel or group tab, or task module. You can [create a configuration page](~/tabs/how-to/create-tab-pages/configuration-page.md) that enables users to configure Microsoft Teams app and use it to configure a channel or group chat tab, a messaging extension, or a connector card for Microsoft 365 Groups. You can permit users to reconfigure your tab after installation and [create a tab removal page](~/tabs/how-to/create-tab-pages/removal-page.md) for your application. When you build a Teams app that includes a tab, you must test how your [tab functions on both the Android and iOS Teams clients](~/tabs/design/tabs-mobile.md). Your tab must [get context](~/tabs/how-to/access-teams-context.md) through basic information, locale and theme information, and `entityId` or `subEntityId` that identifies what is in the tab. You can build tabs with Adaptive Cards and centralize all Teams app capabilities by eliminating the need for a different backend for your bots and tabs. [Stage View](~/tabs/tabs-link-unfurling.md) is a new UI component that allows you to render the content opened in full screen in Teams and pinned as a tab. The existing [link unfurling](~/tabs/tabs-link-unfurling.md) service is updated, so that it's used to turn URLs into a tab using an Adaptive Card and Chat Services. You can [create conversational tabs](~/tabs/how-to/conversational-tabs.md) using conversational sub-entities that allow users to have conversations about sub-entities in your tab, such as specific task, patient, and sales opportunity, instead of discussing the entire tab. You can make changes to [tab margins](~/resources/removing-tab-margins.md) to enhance the developer's experience when building apps. You can drag the tab and place it in the desired position to interchange the tab positions within your personal apps and channel or group chats. |
| platform | Cards And Task Modules | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/task-modules-and-cards/cards-and-task-modules.md | The following types of cards are supported in bots for Teams: * Adaptive Card * Hero card * List card-* Office 365 Connector card +* Connector card for Microsoft 365 Groups * Receipt card * Sign in card * Thumbnail card You can provide [dynamic search](~/task-modules-and-cards/cards/dynamic-search.m * [Cards](~/task-modules-and-cards/what-are-cards.md) * [Task modules](~/task-modules-and-cards/what-are-task-modules.md) * [Authenticate users in Microsoft Teams](../concepts/authentication/authentication.md)-* [Create Office 365 Connectors](../webhooks-and-connectors/how-to/connectors-creating.md) +* [Create connectors for Microsoft 365 Groups](../webhooks-and-connectors/how-to/connectors-creating.md) |
| platform | Cards Actions | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/task-modules-and-cards/cards/cards-actions.md | -> The `CardAction` actions differ from `potentialActions` for Office 365 Connector cards when used from connectors. +> The `CardAction` actions differ from `potentialActions` for connector cards for Microsoft 365 Groups when used from connectors. | Type | Action | | | | |
| platform | Cards Format | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/task-modules-and-cards/cards/cards-format.md | Formatting support differs between card types. Rendering of the card can differ You can include an inline image with any Teams card. Supported image formats are .png, .jpg, or .gif formats. Keep the dimensions within 1024 x 1024 pixels and file size less than 1 MB. Animated .gif images aren't supported. For more information, see [types of cards](./cards-reference.md#inline-card-images). -You can format Adaptive Cards and Office 365 Connector cards with Markdown that include certain supported styles. +You can format Adaptive Cards and connector cards for Microsoft 365 Groups with Markdown that include certain supported styles. ## Format cards with Markdown The following card types support Markdown formatting in Teams: * Adaptive Cards: Markdown is supported in Adaptive Card `Textblock` field, and `Fact.Title` and `Fact.Value`. HTML isn't supported in Adaptive Cards.-* Office 365 Connector cards: Markdown and limited HTML is supported in Office 365 Connector cards in the text fields. +* Connector cards for Microsoft 365 Groups: Markdown and limited HTML is supported in connector cards for Microsoft 365 Groups in the text fields. You can use newlines for Adaptive Cards using `\r` or `\n` escape sequences for newlines in lists. Formatting is different between the desktop and the mobile versions of Teams for Adaptive Cards. Card-based mentions are supported in web, desktop, and mobile clients. You can use the information masking property to mask specific information, such as password or sensitive information from users within the Adaptive Card `Input.Text` input element. You can expand the width of an Adaptive Card using the `width` object. You can enable typeahead support within Adaptive Cards and filter the set of input choices as the user types the input. You can use the `msteams` property to add the ability to display images in stage view selectively. In the stage view, users can zoom in and zoom out of the image. You can select t > * Zoom in and zoom out capability applies only to the image elements that is image type in an Adaptive Card. > * For Teams mobile apps, stage view functionality for images in Adaptive Cards is available by default. Users can view Adaptive Card images in stage view by simply tapping on the image, irrespective of whether the `allowExpand` attribute is present or not. -# [Markdown format for Office 365 Connector cards](#tab/connector-md) +# [Markdown format for connector cards for Microsoft 365 Groups](#tab/connector-md) Connector cards support limited Markdown and HTML formatting. When a user selects the overflow menu on mobile, the Adaptive Card displays the The following card types support HTML formatting in Teams: -* Office 365 Connector cards: Limited Markdown and HTML formatting are supported in Office 365 Connector cards. +* Connector cards for Microsoft 365 Groups: Limited Markdown and HTML formatting are supported in connector card for Microsoft 365 Groups. * Hero and thumbnail cards: HTML tags are supported for simple cards, such as the hero and thumbnail cards. -Formatting is different between the desktop and the mobile versions of Teams for Office 365 Connector cards and simple cards. In this section, you can go through the HTML format example for connector cards and simple cards. +Formatting is different between the desktop and the mobile versions of Teams for connector cards for Microsoft 365 Groups and simple cards. In this section, you can go through the HTML format example for connector cards and simple cards. -# [HTML format for Office 365 Connector cards](#tab/connector-html) +# [HTML format for connector cards for Microsoft 365 Groups](#tab/connector-html) Connector cards support limited Markdown and HTML formatting. You can test formatting in your own cards by modifying this code. * [Format your bot messages](~/bots/how-to/format-your-bot-messages.md) * [Use task modules from bots](~/task-modules-and-cards/task-modules/task-modules-bots.md) * [Schema explorer for Adaptive Cards](https://adaptivecards.io/explorer/TextBlock.html)-* [Create Office 365 Connectors](../../webhooks-and-connectors/how-to/connectors-creating.md) +* [Create connectors for Microsoft 365 Groups](../../webhooks-and-connectors/how-to/connectors-creating.md) * [Create Incoming Webhooks](../../webhooks-and-connectors/how-to/add-incoming-webhook.md) |
| platform | Cards Reference | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/task-modules-and-cards/cards/cards-reference.md | -Adaptive, hero, list, Office 365 Connector, receipt, sign in, and thumbnail cards and card collections are supported in bots for Microsoft Teams. They're based on cards defined by the Bot Framework, but Teams doesn't support all Bot Framework cards and has added some of its own. +Adaptive, hero, list, connector card for Microsoft 365 Groups, receipt, sign in, and thumbnail cards and card collections are supported in bots for Microsoft Teams. They're based on cards defined by the Bot Framework, but Teams doesn't support all Bot Framework cards and has added some of its own. Before you identify the different card types, understand how to create a hero card, thumbnail card, or Adaptive Card. You can identify and use different types of cards based on your application requ | [Adaptive Card](#adaptive-card) | This card is highly customizable and can contain any combination of text, speech, images, buttons, and input fields. | | [Hero card](#hero-card) | This card typically contains a single large image, one or more buttons, and a small amount of text. | | [List card](#list-card) | This card contains a scrolling list of items. |-| [Office 365 Connector card](#office-365-connector-card) | This card has a flexible layout with multiple sections, fields, images, and actions. | +| [Connector card for Microsoft 365 Groups](#connector-card-for-microsoft-365-groups) | This card has a flexible layout with multiple sections, fields, images, and actions. | | [Receipt card](#receipt-card) | This card provides a receipt to the user. | | [Signin card](#sign-in-card) | This card enables a bot to request that a user signs in. | | [Thumbnail card](#thumbnail-card) | This card typically contains a single thumbnail image, some short text, and one or more buttons. | You can identify and use different types of cards based on your application requ ## Features that support different card types -| Card type | Bots | Message extension previews | Message extension results | Task modules | Outgoing Webhooks | Incoming Webhooks | Office 365 Connectors | +| Card type | Bots | Message extension previews | Message extension results | Task modules | Outgoing Webhooks | Incoming Webhooks | Connectors for Microsoft 365 Groups| | | | | | | | | | | Adaptive Card | ✔️ | ❌ | ✔️ | ✔️ | ✔️ | ✔️ | ❌ |-| Office 365 Connector card | ✔️ | ❌ | ✔️ | ❌ | ✔️ | ✔️ | ✔️ | +| Connector card for Microsoft 365 Groups | ✔️ | ❌ | ✔️ | ❌ | ✔️ | ✔️ | ✔️ | | Hero card | ✔️ | ✔️ | ✔️ | ❌ | ✔️ | ✔️ | ❌ | | Thumbnail card | ✔️ | ✔️ | ✔️ | ❌ | ✔️ | ✔️ | ❌ | | List card | ✔️ | ❌ | ❌ | ❌ | ✔️ | ✔️ | ❌ | The following code shows an example of a list card: } ``` -## Office 365 connector card +## Connector card for Microsoft 365 Groups -You can work with an Office 365 Connector card that provides a flexible layout and is a great way to get useful information. The Office 365 connector card is supported in Teams, not in Bot Framework. This card provides a flexible layout with multiple sections, fields, images, and actions. This card contains a connector card so that it can be used by bots. For differences between connector cards and the Office 365 Connector card, see [Additional information on the Office 365 Connector card](#additional-information-on-the-office-365-connector-card). +You can work with an connector cards for Microsoft 365 Groups that provides a flexible layout and is a great way to get useful information. The connector card for Microsoft 365 Groups is supported in Teams, not in Bot Framework. This card provides a flexible layout with multiple sections, fields, images, and actions. This card contains a connector card so that it can be used by bots. For differences between connector cards and the connector card for Microsoft 365 Groups, see [Connector card for Microsoft 365 Groupsd](#additional-information-on-the-connector-card-for-microsoft-365-groups). -### Support for Office 365 Connector cards +### Support for connector cards for Microsoft 365 Groups -The following table provides the features that support Office 365 Connector cards: +The following table provides the features that support connector cards for Microsoft 365 Groups: | Bots in Teams | Message extensions | Connectors | Bot Framework | | | | | | | ✔️ | ✔️ | ✔️ | ❌ | -### Properties of the Office 365 Connector card +### Properties of the connector card for Microsoft 365 Groups -The following table provides the properties of the Office 365 connector card: +The following table provides the properties of the connector card for Microsoft 365 Groups: | Property | Type | Description | | | | | The following table provides the properties of the Office 365 connector card: | text | Rich text | Text appears under the subtitle. For formatting options, see [card formatting](~/task-modules-and-cards/cards/cards-format.md). | | themeColor | HEX string | Color that overrides the `accentColor` provided from the application manifest. | -For more information on the properties of the Office 365 connector card, see [card fields](/outlook/actionable-messages/message-card-reference). +For more information on the properties of the connector card for Microsoft 365 Groups, see [card fields](/outlook/actionable-messages/message-card-reference). -### Additional information on the Office 365 Connector card +### Additional information on the connector card for Microsoft 365 Groups -Office 365 Connector cards function properly in Microsoft Teams, including [`ActionCard` actions](/outlook/actionable-messages/card-reference#actioncard-action). +Connector cards for Microsoft 365 Groups function properly in Microsoft Teams, including [`ActionCard` actions](/outlook/actionable-messages/card-reference#actioncard-action). The important difference between using connector cards from a connector and using connector cards in your bot is the handling of card actions. The following table lists the difference: For all other details about connector card properties, see [actionable message c * `originator` * `correlationId` -### Example of an Office 365 Connector card +### Example of an connector card for Microsoft 365 Groups -The following code shows an example of an Office 365 Connector card: +The following code shows an example of an connector card for Microsoft 365 Groups: ```json { The following cards are implemented by the Bot Framework, but aren't supported b * [Up to date cards](~/task-modules-and-cards/cards/universal-actions-for-adaptive-cards/up-to-date-views.md) * [Work with Universal Actions for Adaptive Cards](~/task-modules-and-cards/cards/universal-actions-for-adaptive-cards/work-with-universal-actions-for-adaptive-cards.md) * [Adaptive Cards overflow menu](~/task-modules-and-cards/cards/cards-format.md#adaptive-cards-overflow-menu)-* [Create Office 365 Connectors](../../webhooks-and-connectors/how-to/connectors-creating.md) +* [Create connectors for Microsoft 365 Groups](../../webhooks-and-connectors/how-to/connectors-creating.md) * [Form completion feedback](~/bots/how-to/conversations/conversation-messages.md#form-completion-feedback) |
| platform | People Picker | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/task-modules-and-cards/cards/people-picker.md | You can implement People Picker for efficient task management in different scena * [Types of cards](cards-reference.md) * [Bots and SDKs](../../bots/bot-features.md) * [Build message extensions for Teams](../../messaging-extensions/what-are-messaging-extensions.md)-* [Create Office 365 Connectors](../../webhooks-and-connectors/how-to/connectors-creating.md) +* [Create connectors for Microsoft 365 Groups](../../webhooks-and-connectors/how-to/connectors-creating.md) |
| platform | Task Modules Bots | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/task-modules-and-cards/task-modules/task-modules-bots.md | -Task modules can be invoked from Microsoft Teams bots using buttons on Adaptive Cards and Bot Framework cards that are hero, thumbnail, and Office 365 Connector. Task modules are often a better user experience than multiple conversation steps. Keep track of bot state and allow the user to interrupt or cancel the sequence. +Task modules can be invoked from Microsoft Teams bots using buttons on Adaptive Cards and Bot Framework cards that are hero, thumbnail, and connector for Microsoft 365 Groups. Task modules are often a better user experience than multiple conversation steps. Keep track of bot state and allow the user to interrupt or cancel the sequence. There are two ways of invoking task modules: |
| platform | What Are Cards | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/task-modules-and-cards/what-are-cards.md | The bots for Teams support the following types of cards: - Adaptive Card - Hero card - List card-- Office 365 Connector card+- Connector card for Microsoft 365 Groups - Receipt card - Sign-in card - Thumbnail card Teams uses cards in three different places: ## Cards in connectors -Cards were first defined as part of Outlook and Microsoft 365 and are now used as part of Office 365 Connectors. Like many Microsoft 365 applications, Teams supports connectors. For more information, see [create Office 365 Connectors](../webhooks-and-connectors/how-to/connectors-creating.md). You can find the specification for cards in connectors in [actionable message card reference](/outlook/actionable-messages/card-reference). +Cards were first defined as part of Outlook and Microsoft 365 and are now used as part of connectors for Microsoft 365 Groups. Like many Microsoft 365 applications, Teams supports connectors. For more information, see [create connectors for Microsoft 365 Groups](../webhooks-and-connectors/how-to/connectors-creating.md). You can find the specification for cards in connectors in [actionable message card reference](/outlook/actionable-messages/card-reference). ## Cards in bots All cards used by Teams are listed in [types of cards](~/task-modules-and-cards/ ## Adaptive Cards -[Adaptive Cards](~/task-modules-and-cards/cards/cards-reference.md#adaptive-card) are a new cross product specification for cards in Microsoft products including bots, Cortana, Outlook, and Windows. They're the recommended card type for new Teams development. For general information from the Adaptive Cards team, see [Adaptive Cards overview](/adaptive-cards). You can use Adaptive Cards anywhere you use existing hero cards, Office 365 cards, and thumbnail cards. +[Adaptive Cards](~/task-modules-and-cards/cards/cards-reference.md#adaptive-card) are a new cross product specification for cards in Microsoft products including bots, Cortana, Outlook, and Windows. They're the recommended card type for new Teams development. For general information from the Adaptive Cards team, see [Adaptive Cards overview](/adaptive-cards). You can use Adaptive Cards anywhere you use existing hero cards,Microsoft 365 cards, and thumbnail cards. In addition to Adaptive Cards, Teams supports two other types of cards: -- Connector cards: Used as part of Office 365 Connectors.+- Connector cards: Used as part of connectors for Microsoft 365 Groups. - Simple cards: Used from the Bot Framework, such as the thumbnail and hero cards. ### People Picker in Adaptive Cards |
| platform | Add Incoming Webhook | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md | The following table provides the features and description of an Incoming Webhook | Features | Description | | -- | -- | |Adaptive Cards using an Incoming Webhook | Adaptive Cards can be sent through Incoming Webhooks. For more information, see [Send Adaptive Cards using Incoming Webhooks](../../webhooks-and-connectors/how-to/connectors-using.md#send-adaptive-cards-using-an-incoming-webhook).|-|Actionable messaging support|Actionable message cards are supported in all Office 365 groups including Teams. If you send messages through cards, you must use the actionable message card format. For more information, see [Legacy actionable message card reference](/outlook/actionable-messages/message-card-reference) and [message card playground](https://messagecardplayground.azurewebsites.net).| +|Actionable messaging support|Actionable message cards are supported in all Microsoft 365 groups including Teams. If you send messages through cards, you must use the actionable message card format. For more information, see [Legacy actionable message card reference](/outlook/actionable-messages/message-card-reference) and [message card playground](https://messagecardplayground.azurewebsites.net).| |Independent HTTPS messaging support|Cards provide information clearly and consistently. Any tool or framework that can send HTTPS POST requests can send messages to Teams through an Incoming Webhook.| |Markdown support|All text fields in actionable messaging cards support basic Markdown. Don't use HTML markup in your cards. HTML is ignored and treated as plain text.| |Scoped configuration|Incoming Webhook is scoped and configured at the channel level.| To add an Incoming Webhook to a Teams channel, follow these steps: The webhook is now available in the Teams channel. -You can create and send actionable messages through Incoming Webhook or Office 365 Connector. For more information, see [Create and send messages](~/webhooks-and-connectors/how-to/connectors-using.md). +You can create and send actionable messages through Incoming Webhook or connector for Microsoft 365 Groups. For more information, see [Create and send messages](~/webhooks-and-connectors/how-to/connectors-using.md). > [!NOTE] > In Teams, select **Settings** > **Member permissions** > **Allow members to create, update, and remove connectors**, so that any team member can add, modify, or delete a connector. To remove an Incoming Webhook from a Teams channel, follow these steps: * [Webhooks and connectors](../what-are-webhooks-and-connectors.md) * [Create Outgoing Webhooks](~/webhooks-and-connectors/how-to/add-outgoing-webhook.md)-* [Create Office 365 Connectors](~/webhooks-and-connectors/how-to/connectors-creating.md) +* [Create connectors for Microsoft 365 Groups](~/webhooks-and-connectors/how-to/connectors-creating.md) * [Create and send messages](~/webhooks-and-connectors/how-to/connectors-using.md) * [Build bots for Teams](../../bots/what-are-bots.md) * [Message extensions](../../messaging-extensions/what-are-messaging-extensions.md) |
| platform | Add Outgoing Webhook | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/webhooks-and-connectors/how-to/add-outgoing-webhook.md | Follow the [step-by-step guide](../../sbs-outgoing-webhooks.yml) to create Outgo * [Webhooks and connectors](../what-are-webhooks-and-connectors.md) * [Create and send messages](connectors-using.md) * [Create Incoming Webhooks](~/webhooks-and-connectors/how-to/add-incoming-webhook.md)-* [Create Office 365 Connectors](~/webhooks-and-connectors/how-to/connectors-creating.md) +* [Create connectors for Microsoft 365 Groups](~/webhooks-and-connectors/how-to/connectors-creating.md) * [Adaptive Cards](../../task-modules-and-cards/what-are-cards.md#adaptive-cards) |
| platform | Connectors Creating | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/webhooks-and-connectors/how-to/connectors-creating.md | Title: Create Office 365 Connectors + Title: Create connectors for Microsoft 365 Groups -description: Get started with Office 365 Connectors. Add connector to Teams app in Microsoft Teams. Sample(.NET, Node.js) Office 365 Connector generating notifications to Teams channel. +description: Get started with connectors for Microsoft 365 Groups. Add connector to Teams app in Microsoft Teams. Sample(.NET, Node.js) connector for Microsoft 365 Groups generating notifications to Teams channel. ms.localizationpriority: medium Last updated 06/16/2021 -# Create Office 365 Connectors +# Create connectors for Microsoft 365 Groups -With Microsoft Teams apps, you can add your existing Office 365 Connector or build a new one within Teams. For more information, see [build your own connector](/outlook/actionable-messages/connectors-dev-dashboard#build-your-own-connector). +With Microsoft Teams apps, you can add your existing connector for Microsoft 365 Groups or build a new one within Teams. For more information, see [build your own connector](/outlook/actionable-messages/connectors-dev-dashboard#build-your-own-connector). -See the following video to learn how to create an Office 365 Connectors: +See the following video to learn how to create an connectors for Microsoft 365 Groups: <br> > [!VIDEO https://www.microsoft.com/en-us/videoplayer/embed/RE4OIzv] The following table provides the parameters and the details of `getConfig` respo | `configName` | The configuration name, as set by your code when calling `setConfig()`. | | `contentUrl` | The URL of the configuration page, as set by your code when calling `setConfig()`. | | `webhookUrl` | The webhook URL created for the connector. Use the webhook URL to POST structured JSON to send cards to the channel. The `webhookUrl` is returned only when the application returns data successfully. |-| `appType` | The values returned can be `mail`, `groups`, or `teams` corresponding to the Microsoft 365 Mail, Office 365 Groups, or Teams. respectively. | +| `appType` | The values returned can be `mail`, `groups`, or `teams` corresponding to the Microsoft 365 Mail, Microsoft 365 Groups, or Teams. respectively. | | `userObjectId` | The unique ID corresponding to the Microsoft 365 user who initiated the setup of the connector. It must be secured. This value can be used to associate the user in Microsoft 365, who has setup the configuration in your service. | #### Handle edits Follow the [step-by-step guide](../../sbs-teams-connectors.yml) to create and te 1. [Create Incoming Webhooks](add-incoming-webhook.md#create-incoming-webhooks) directly for your team. -1. Add a [configuration page](~/webhooks-and-connectors/how-to/connectors-creating.md?#integrate-the-configuration-experience) and publish your Incoming Webhook in an Office 365 Connector. +1. Add a [configuration page](~/webhooks-and-connectors/how-to/connectors-creating.md?#integrate-the-configuration-experience) and publish your Incoming Webhook in a connector for Microsoft 365 Groups. 1. Package and publish your connector as part of your [AppSource](~/concepts/deploy-and-publish/office-store-guidance.md) submission. The following table provides the sample name and its description: |**Sample name** | **Description** | **.NET** | **Node.js** | |-||--|-|-| Connectors | Sample Office 365 Connector generating notifications to Teams channel.| [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/connector-todo-notification/csharp) | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/connector-github-notification/nodejs)| +| Connectors | Sample connector for Microsoft 365 Groups generating notifications to Teams channel.| [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/connector-todo-notification/csharp) | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/connector-github-notification/nodejs)| | Generic connectors sample |Sample code for a generic connector that is easy to customize for any system that supports webhooks.| | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/connector-generic/nodejs)| ## Step-by-step guide |
| platform | Connectors Using | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/webhooks-and-connectors/how-to/connectors-using.md | Title: Create and send messages -description: Create actionable messages, send message through Incoming Webhook, Office 365 Connector, cURL, or PowerShell. Send Adaptive Cards. Time based transaction. +description: Create actionable messages, send message through Incoming Webhook, connectors for Microsoft 365 Groups, cURL, or PowerShell. Send Adaptive Cards. Time based transaction. ms.localizationpriority: high # Create and send messages -You can create actionable messages and send it through Incoming Webhook or Office 365 Connector. +You can create actionable messages and send it through Incoming Webhook or connector for Microsoft 365 Groups. ## Create actionable messages For more information on connector card actions, see [Actions](/outlook/actionabl > * Specifying `compact` for the `style` property in Microsoft Teams is the same as specifying `normal` for the `style` property in Microsoft Outlook. > * For the HttpPOST action, the bearer token is included with the requests. This token includes the Microsoft Azure Active Directory (Azure AD) identity of the Microsoft 365 user who took the action. -## Send a message through Incoming Webhook or Office 365 Connector +## Send a message through Incoming Webhook or connector for Microsoft 365 Groups -To send a message through your Incoming Webhook or Office 365 Connector, post a JSON payload to the webhook URL. This payload must be in the form of an [Office 365 connector card](~/task-modules-and-cards/cards/cards-reference.md#office-365-connector-card). +To send a message through your Incoming Webhook or connector for Microsoft 365 Groups, post a JSON payload to the webhook URL. This payload must be in the form of a [connector card for Microsoft 365 Groups](~/task-modules-and-cards/cards/cards-reference.md#connector-card-for-microsoft-365-groups). You can also use this JSON to create cards containing rich inputs, such as text entry, multiselect, or selecting date and time. The code that generates the card and posts it to the webhook URL can run on any hosted service. These cards are defined as part of actionable messages and are also supported in [cards](~/task-modules-and-cards/what-are-cards.md) used in Teams bots and message extensions. |
| platform | What Are Webhooks And Connectors | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md | Title: Webhooks and connectors -description: Learn how webhooks and connectors help to connect the web services to channels and teams in Microsoft Teams. Learn Incoming, Outgoing Webhooks, and Office 365 Connectors. +description: Learn how webhooks and connectors help to connect the web services to channels and teams in Microsoft Teams. Learn Incoming, Outgoing Webhooks, and Connectors for Microsoft 365 Groups. ms.localizationpriority: high Learn more about the differences between a notification bot and Incoming Webhook | Cloud resource required | Azure Bot Framework | No resources are required. | | Tutorial | [Build notification bot with JavaScript](../sbs-gs-notificationbot.yml) | [Incoming Webhook notification sample](https://github.com/OfficeDev/TeamsFx-Samples/tree/dev/incoming-webhook-notification) | -### Office 365 Connectors +### Connectors for Microsoft 365 Groups -Office 365 Connectors allow you to create a custom configuration page for your Incoming Webhook and package them as part of a Teams app. You send messages primarily using Office 365 Connector cards and can add a limited set of card actions to them. For example, a weather connector that allows users to select a location and any time of the day, to receive updates about tomorrow's weather. They're configured at channel level but are installed at team level. +Connectors for Microsoft 365 Groups allow you to create a custom configuration page for your Incoming Webhook and package them as part of a Teams app. You send messages primarily using connector cards for Microsoft 365 Groups and can add a limited set of card actions to them. For example, a weather connector that allows users to select a location and any time of the day, to receive updates about tomorrow's weather. They're configured at channel level but are installed at team level. > [!NOTE]-> You can distribute the Office 365 Connector Teams app to our AppStore. +> You can distribute the connector for Microsoft 365 Groups Teams app to our AppStore. ## Create and send messages -Actionable messages allow users to take action without leaving their email client, increasing user engagement. With Office 365 and Incoming Webhooks, you can send messages by posting a JSON payload to the webhook URL. +Actionable messages allow users to take action without leaving their email client, increasing user engagement. With Microsoft 365 and Incoming Webhooks, you can send messages by posting a JSON payload to the webhook URL. ## Next step Actionable messages allow users to take action without leaving their email clien * [Create Incoming Webhooks](~/webhooks-and-connectors/how-to/add-incoming-webhook.md) * [App capabilities mapped to features](../concepts/design/map-use-cases.md#app-capabilities-mapped-to-features)-* [Create Office 365 Connectors](~/webhooks-and-connectors/how-to/connectors-creating.md) +* [Create connectors for Microsoft 365 Groups](~/webhooks-and-connectors/how-to/connectors-creating.md) * [Create and send messages](~/webhooks-and-connectors/how-to/connectors-using.md) |
| platform | Whats New | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/whats-new.md | Teams platform features that are available to all app developers. | 03/29/2022 |Integrate People Picker | Integrate with Teams > [Integrate People Picker](concepts/device-capabilities/people-picker-capability.md) | 03/23/2022 | Introduced step-by-step guide to unfurl links in Teams using bot | Build message extensions > Add link unfurling > [Unfurl links in Teams using bot](sbs-botbuilder-linkunfurling.yml)| | 03/22/2022 | Added information on debug process| ΓÇó Tools and SDKs> Teams Toolkit for Visual Studio Code > [Debug your Teams app locally](toolkit/debug-local.md) </br> ΓÇó Tools and SDKs> Teams Toolkit for Visual Studio Code > [Debug background process](toolkit/debug-background-process.md)|-| 03/14/2022 | Introduced step-by-step guide to build and test a connector in Microsoft Teams | Build webhooks and connectors > Create Office 365 Connectors > [Build Teams connectors](sbs-teams-connectors.yml)| +| 03/14/2022 | Introduced step-by-step guide to build and test a connector in Microsoft Teams | Build webhooks and connectors > Create connectors for Microsoft 365 Groups > [Build Teams connectors](sbs-teams-connectors.yml)| | 03/10/2022 | Added information on Moodle LMS and Microsoft 365 plugins | Integrate with Teams > Moodle LMS > [Moodle learning management system](resources/moodle-overview.md)| | 03/03/2022 | How to add authentication using external OAuth provider| Add authentication > Tabs > [Use external OAuth providers](tabs/how-to/authentication/auth-oauth-provider.md) | | 02/25/2022 | Introduced step-by-step guide to invoke task modules in Teams| Build cards and task modules > Build task modules > Use task modules from bots > [Invoke task module from Teams](sbs-botbuilder-taskmodule.yml)| |