| Service | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| platform | Channel Messages With Rsc | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/bots/how-to/conversations/channel-messages-with-rsc.md | ms.localizationpriority: medium The resource-specific consent (RSC) permissions model, originally developed for Microsoft Teams Graph APIs, is being extended to bot scenarios. With RSC, conversation owners can consent for a bot to receive all user messages in standard channels and chats without being @mentioned. This can be enabled by specifying the `ChannelMessage.Read.Group` or `ChatMessage.Read.Chat` permission strings in your Teams app manifest. Conversation owners can grant consent during the app installation or upgrade process after the app updates are published. For more information about enabling RSC for your app and inside of a tenant, see [resource-specific consent](../../../graph-api/rsc/resource-specific-consent.md). +> [!NOTE] +> Bots that receive all conversation messages with RSC aren't supported in Government Community Cloud (GCC), GCC-High, and Department of Defense (DOD) environments. + ## Enable bots to receive all channel or chat messages The `ChannelMessage.Read.Group` and `ChatMessage.Read.Chat` RSC permissions are being extended to bots. With user consent and app installation, these permissions: |
| platform | Shared Channels | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/concepts/build-and-test/shared-channels.md | Teams Connect shared channels facilitate secure collaboration seamlessly. Allow SupportedChannelTypes is an optional property that enables your app in non-standard channels. If your app supports the team scope and the property is defined, Teams enables your app in each channel type accordingly. Private and shared channels are currently supported. For more information, see [supportedChannelTypes](../../resources/schem#supportedchanneltypes). ```JSON-"supportedChannelTypes": { - "type": "array", - "description": "List of ΓÇÿnon-standardΓÇÖ channel types that the app supports. Note: Channels of standard type are supported by default if the app supports team scope. ", - "maxItems": 2, - "items": { - "enum": [ - "sharedChannels", - "privateChannels" - ] - } - } + "supportedChannelTypes": [ + "sharedChannels", + "privateChannels" + ] ``` > [!NOTE] |
| platform | Manifest Schema | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/resources/schema/manifest-schema.md | The following is the sample manifest schema: "searchUrl": "https://contoso.com/content (displayed in web browser)" } ],+ "supportedChannelTypes": [ + "sharedChannels", + "privateChannels" + ], "bots": [ { "botId": "%MICROSOFT-APP-ID-REGISTERED-WITH-BOT-FRAMEWORK%", You can define any of the following properties: **Optional**ΓÇöarray -Enables your app in non-standard channels. If your app supports a team scope and this property is defined, Teams enables your app in each channel type accordingly. Currently, the private and shared channel types are supported. +Enables your app in non-standard channels. If your app supports a team scope and this property is defined, Teams enables your app in each channel type accordingly. The supportedChannelTypes property only supports `sharedChannels` and `privateChannels`. > [!NOTE] > |
| platform | Build Adaptive Card Tabs | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/tabs/how-to/build-adaptive-card-tabs.md | Follow the [step-by-step](../../sbs-tab-with-adaptive-cards.yml) guide to build * [Tabs on mobile](../design/tabs-mobile.md) * [Cards](../../task-modules-and-cards/what-are-cards.md) * [Use task modules in tabs](../../task-modules-and-cards/task-modules/task-modules-tabs.md)-* [Form completion feedback](../../task-modules-and-cards/cards/cards-format.md#form-completion-feedback) +* [Form completion feedback](../../task-modules-and-cards/cards/cards-actions.md#form-completion-feedback) |
| platform | Tabs Link Unfurling | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/tabs/tabs-link-unfurling.md | Encoded URL: ## Collaborative Stage View > [!NOTE]-> -> * Collaborative Stage View is available only in [public developer preview](/microsoftteams/platform/resources/dev-preview/developer-preview-intro). -> * Collaborative Stage View isn't supported in Teams web and mobile clients. +> Collaborative Stage View isn't supported in Teams web and mobile clients. Collaborative Stage View is an enhancement to Stage View that allows users to engage with your app content in a new Teams window. When a user opens Collaborative Stage View from an Adaptive Card, the app content pops-out in a new Teams window instead of the default Stage View modal. |
| platform | Sequential Workflows | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/task-modules-and-cards/cards/Universal-actions-for-adaptive-cards/Sequential-Workflows.md | var adaptiveCardResponse = JObject.FromObject(new * [Adaptive Card actions in Teams](~/task-modules-and-cards/cards/cards-actions.md#adaptive-cards-actions) * [How bots work](/azure/bot-service/bot-builder-basics?view=azure-bot-service-4.0&preserve-view=true) * [Work with Universal Actions for Adaptive Cards](Work-with-universal-actions-for-adaptive-cards.md)-* [Form completion feedback](../cards-format.md#form-completion-feedback) +* [Form completion feedback](../cards-actions.md#form-completion-feedback) |
| platform | Up To Date Views | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/task-modules-and-cards/cards/Universal-actions-for-adaptive-cards/Up-To-Date-Views.md | The following code provides an example of Adaptive Cards sent as response of `ad * [Cards and task modules](../../cards-and-task-modules.md) * [Work with Universal Actions for Adaptive Cards](Work-with-universal-actions-for-adaptive-cards.md) * [User Specific Views](User-Specific-Views.md)-* [Form completion feedback](../cards-format.md#form-completion-feedback) +* [Form completion feedback](../cards-actions.md#form-completion-feedback) |
| platform | User Specific Views | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/task-modules-and-cards/cards/Universal-actions-for-adaptive-cards/User-Specific-Views.md | The following list provides card design guidelines for User Specific Views: * [Work with Universal Actions for Adaptive Cards](Work-with-Universal-Actions-for-Adaptive-Cards.md) * [Up to date cards](Up-To-Date-Views.md) * [Cards](../../what-are-cards.md)-* [Form completion feedback](../cards-format.md#form-completion-feedback) +* [Form completion feedback](../cards-actions.md#form-completion-feedback) |
| platform | Work With Universal Actions For Adaptive Cards | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/task-modules-and-cards/cards/Universal-actions-for-adaptive-cards/Work-with-Universal-Actions-for-Adaptive-Cards.md | For more information, see [backward compatibility on Teams](/adaptive-cards/auth * [Basics of the Microsoft Bot Framework](/azure/bot-service/bot-builder-basics?view=azure-bot-service-4.0&preserve-view=true) * [Sequential Workflows](~/task-modules-and-cards/cards/universal-actions-for-adaptive-cards/sequential-workflows.md) * [Up to date cards](~/task-modules-and-cards/cards/universal-actions-for-adaptive-cards/up-to-date-views.md)-* [Form completion feedback](../cards-format.md#form-completion-feedback) +* [Form completion feedback](../cards-actions.md#form-completion-feedback) |
| platform | Cards Actions | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/task-modules-and-cards/cards/cards-actions.md | The following is an example of the incoming activity to a bot when user types so The next section provides details on how to use existing Bot Framework actions with Adaptive Cards. +#### Form completion feedback ++You can build form completion feedback using an Adaptive Card. Form completion message appears in Adaptive Cards while sending a response to the bot. The message can be of two types, error or success: ++* **Error**: When a response sent to the bot is unsuccessful, **Something went wrong, Try again** message appears. The error occurs due to various reasons, such as: + * Too many requests + * Multiple concurrent operations on the same conversation + * Service dependency issue + * Gateway Timeout ++ :::image type="content" source="../../assets/images/Cards/error-message.png" alt-text="Screenshot shows an Error message in an Adaptive Card." ::: ++* **Success**: When a response sent to the bot is successful, **Your response was sent to the app** message appears. ++ :::image type="content" source="../../assets/images/Cards/success.PNG" alt-text="Screenshot shows a success message in an Adaptive Card."::: ++ You can select **Close** or switch chat to dismiss the message. ++ If you don't want to display the success message, set the attribute `hide` to `true` in the `msTeams` `feedback` property. Following is an example: ++ ```json + "content": { + "type": "AdaptiveCard", + "title": "Card with hidden footer messages", + "version": "1.0", + "actions": [ + { + "type": "Action.Submit", + "title": "Submit", + "msTeams": { + "feedback": { + "hide": true + } + } + } + ] + } + ``` ++For more information on cards and cards in bots, see [cards documentation](~/task-modules-and-cards/what-are-cards.md). + ### Adaptive Cards with messageBack action To include a `messageBack` action with an Adaptive Card include the following details in the `msteams` object: The following code shows an example of Adaptive Cards with `invoke` action with * [Types of cards](cards-reference.md) * [Use task modules from bots](~/task-modules-and-cards/task-modules/task-modules-bots.md) * [Adaptive Cards in bots](../../bots/how-to/conversations/conversation-messages.md#adaptive-cards)-* [Form completion feedback](cards-format.md#form-completion-feedback) |
| platform | Cards Format | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/task-modules-and-cards/cards/cards-format.md | The following code shows an example of formatting for Markdown connector cards: -### Form completion feedback --You can build form completion feedback using an Adaptive Card. Form completion message appears in Adaptive Cards while sending a response to the bot. The message can be of two types, error or success: --* **Error**: When a response sent to the bot is unsuccessful, **Something went wrong, Try again** message appears. -- :::image type="content" source="../../assets/images/Cards/error-message.png" alt-text="Error message" border="false"::: --* **Success**: When a response sent to the bot is successful, **Your response was sent to the app** message appears. -- :::image type="content" source="../../assets/images/Cards/success.PNG" alt-text="Success message"border="true"::: -- You can select **Close** or switch chat to dismiss the message. -- If you don't want to display the success message, set the attribute `hide` to `true` in the `msTeams` `feedback` property. Following is an example: -- ```json - "content": { - "type": "AdaptiveCard", - "title": "Card with hidden footer messages", - "version": "1.0", - "actions": [ - { - "type": "Action.Submit", - "title": "Submit", - "msTeams": { - "feedback": { - "hide": true - } - } - } - ] - } - ``` --For more information on cards and cards in bots, see [cards documentation](~/task-modules-and-cards/what-are-cards.md). - ## Adaptive Cards overflow menu Adaptive Card in Teams supports overflow menu. You can populate an overflow menu for all the secondary actions in an Adaptive Card. An overflow menu in an Adaptive Card can be added to the following: |
| platform | Cards Reference | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/task-modules-and-cards/cards/cards-reference.md | The following cards are implemented by the Bot Framework, but aren't supported b * [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 connectors for Microsoft 365 Groups](../../webhooks-and-connectors/how-to/connectors-creating.md)-* [Form completion feedback](cards-format.md#form-completion-feedback) +* [Form completion feedback](cards-actions.md#form-completion-feedback) * [App manifest schema for Teams](../../resources/schem) |
| platform | Add Incoming Webhook | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md | Last updated 01/25/2023 # Create Incoming Webhooks -An Incoming Webhook lets external applications to share content in Microsoft Teams channels. The webhooks are used as tools to track and notify. The webhooks provide a unique URL, to send a JSON payload with a message in card format. Cards are user interface containers that include content and actions related to a single article. You can use cards in the following capabilities: +An Incoming Webhook lets external applications share content in Microsoft Teams channels. The webhooks are used as tools to track and notify. The webhooks provide a unique URL, to send a JSON payload with a message in card format. Cards are user interface containers that include content and actions related to a single article. You can use cards in the following capabilities: * Bots * Message extensions |
| 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. **2023 July** +* ***July 28, 2023***: [Use Collaborative Stage View to engage with your app content in a new Teams window](tabs/tabs-link-unfurling.md#collaborative-stage-view). + * ***July 25, 2023***: [Use people icon in an Adaptive Card to view the images of users](task-modules-and-cards/cards/cards-format.md#people-icon-in-an-adaptive-card). * ***July 20, 2023***: [App caching for iOS personal tray](tabs/how-to/app-caching.md). Teams platform features that are available to all app developers. | 07/21/2022 | Introduced step by step guide to send activity feed notifications | Design your app > UI components> Activity feed notifications > [Send activity feed notification](sbs-graphactivity-feedbroadcast.yml) | | 07/08/2022| Updates to send channel ID selected by user during app installation to bots via conversation and installation update events | Build bots > Bot conversations > Conversation events in your Teams bot > [Conversation events in your Teams bot](bots/how-to/conversations/subscribe-to-conversation-events.md) | | 06/16/2022 | Updated media capabilities to support desktop and mobile| Integrate device capabilities > [Integrate media capabilities](concepts/device-capabilities/media-capabilities.md)|-| 06/08/2022 | Optional card feedback for success message| Build cards and task modules > Build cards > [Format cards in Microsoft Teams](task-modules-and-cards/cards/cards-format.md#form-completion-feedback)| +| 06/08/2022 | Optional card feedback for success message| Build cards and task modules > Build cards > [Form completion feedback](task-modules-and-cards/cards/cards-actions.md#form-completion-feedback)| | 06/03/2022 | Updated Add authentication module for enabling SSO for tab app with new structure and procedures | Add authentication > Tabs > [Enable single sign-on in a tab app](tabs/how-to/authentication/tab-sso-overview.md) | | 05/24/2022 | Additional tips for rapid approval to publish your app linked to a SaaS offer | Publish to the Teams store > Overview > [Additional tips for rapid approval to publish your app linked to a SaaS offer](~/concepts/deploy-and-publish/appsource/publish.md#additional-tips-for-rapid-approval-to-publish-your-app-linked-to-a-saas-offer) | | 05/24/2022 | Submit your Outlook- and Office-enabled apps to the Teams store | Extend your app across Microsoft 365 > [Overview](m365-apps/overview.md) | Teams platform features that are available to all app developers. | 02/08/2022 | Introduced step-by-step guide to create Calling and Meeting bot| Build bots > Calls and meetings bots > Register calls and meetings bot > [Step-by-step guide to create Calling and Meeting bot](sbs-calling-and-meeting.yml) | | 02/02/2022 | Introduced app manifest version 1.12 | App manifest > [App manifest schema](resources/schem) | | 01/25/2022 | Send real-time captions API | Build apps for Teams meetings > Meeting apps API references> [Advanced meeting APIs](apps-in-teams-meetings/meeting-apps-apis.md)|-| 01/19/2022 | Adaptive Cards form completion feedback | Build cards and task modules > Build cards > [Format cards in Microsoft Teams](task-modules-and-cards/cards/cards-format.md#form-completion-feedback)| +| 01/19/2022 | Adaptive Cards form completion feedback | Build cards and task modules > Build cards > [Form completion feedback](task-modules-and-cards/cards/cards-actions.md#form-completion-feedback)| | 01/17/2022 | People Picker in Adaptive cards for desktop | Build cards and task modules > Build cards > [People Picker in Adaptive Cards](task-modules-and-cards/cards/people-picker.md)| </details> Developer preview is a public program that provides early access to unreleased T | **Date** | **Update** | **Find here** | | -- | | -|-|19/07/2023| Use Collaborative Stage View to engage with your app content in a new Teams window | Build tabs > [Tabs link unfurling and Stage View](tabs/tabs-link-unfurling.md#collaborative-stage-view) | |31/01/2023| Send notifications to specific participants on a meeting stage with targeted in-meeting notification. |Build apps for Teams meetings and calls > Enable and configure apps for meetings > Build in-meeting notification for Teams meeting > Build tabs for meeting > [Targeted in-meeting notification](apps-in-teams-meetings/in-meeting-notification-for-meeting.md#targeted-in-meeting-notification)| |30/01/2023| Enable app caching to improve subsequent launch time of the apps to the meeting side panel.|Build tabs > [App caching for your tab app](tabs/how-to/app-caching.md) | |