Updates from: 03/17/2021 04:11:05
Service Microsoft Docs article Related commit history on GitHub Change details
platform Designing Apps In Meetings https://github.com/MicrosoftDocs/msteams-docs/commits/master/msteams-platform/apps-in-teams-meetings/design/designing-apps-in-meetings.md
There are two header variants. When possible, use the variant with the avatar to
In-meeting dialogs can vary in size to account for different scenarios. Make sure to maintain padding and component sizes.
-* **Width**: The iframe width is an absolute value within the range you specify.
-* **Height**: The height of the dialog is determined by the content in the iframe. Vertical scroll takes over for content that exceeds the maximum height.
+* **Width**: The iframe width of the dialog is an absolute value within the range you specify.
+* **Height**: The iframe height of the dialog is an absolute value within the range you specify.
+
+> [!NOTE]
+> The values that you define for the width and height are used in `externalResourceURL` of in-meeting dialog.
:::image type="content" source="../../assets/images/apps-in-meetings/in-meeting-dialog-responsive.png" alt-text="Example shows the in-meeting dialog. Width: Min--280 pixels (248 pixels iframe). Max--460 pixels (428 pixels iframe). Height: 300 pixels (iframe)." border="false":::
platform Respond To Task Module Submit https://github.com/MicrosoftDocs/msteams-docs/commits/master/msteams-platform/messaging-extensions/how-to/action-commands/respond-to-task-module-submit.md
description: Describes how to respond to the task module submit action from a me
+ # Respond to the task module submit action [!include[v4-to-v3-SDK-pointer](~/includes/v4-to-v3-pointer-me.md)]
-After a user submits the task module, your web service receives a `composeExtension/submitAction` invoke message with the command ID and parameter values. Your app has five seconds to respond to the invoke, otherwise the user receives an error message *Unable to reach the app*, and any reply to the invoke is ignored by the Teams client.
+After a user submits the task module, your web service receives a `composeExtension/submitAction` invoke message with the command ID and parameter values. Your app has five seconds to respond to the invoke, otherwise the user receives an error message **Unable to reach the app** and any reply to the invoke is ignored by the Teams client.
You have the following options for responding:
For authentication or configuration, after the user completes the flow the origi
|Bot with Adaptive Card | x | | x | | No response | x | x | x |
+> [!NOTE]
+> * When you select **Action.Submit** through ME cards, it sends invoke activity with the name **composeExtension**, where the value is equal to the usual payload.
+> * When you select **Action.Submit** through conversation, you receive message activity with the name **onCardButtonClicked**, where the value is equal to the usual payload.
+ ## The submitAction invoke event Examples of receiving the invoke message are as follows:
platform Removing Tab Margins https://github.com/MicrosoftDocs/msteams-docs/commits/master/msteams-platform/resources/removing-tab-margins.md
Removing the margins around all tabs will allow developers to build apps that lo
## Timelines * March 5, 2021 - Margins removed in [Public Developer Preview](~/resources/dev-preview/developer-preview-intro.md).
-* May 1, 2021 - Margins will be removed in production.
+* June 15, 2021 - Margins will be removed in production.
## Guidelines
platform Cards Reference https://github.com/MicrosoftDocs/msteams-docs/commits/master/msteams-platform/task-modules-and-cards/cards/cards-reference.md
The cards listed in this section are supported in bots for Microsoft Teams. They
You can find additional information on how to use cards in the documentation for the Bot Builder SDK (v3). Code samples are also available in the Microsoft/BotBuilder-Samples repository on GitHub. * .NET
- * [Add cards as attachments to messages](/bot-framework/dotnet/bot-builder-dotnet-add-rich-card-attachments)
- * [Cards sample code (Bot Builder v3)](https://github.com/Microsoft/BotBuilder-Samples/tree/v3-sdk-samples/CSharp/cards-RichCards)
+ * [Add cards as attachments to messages](/azure/bot-service/bot-builder-howto-add-media-attachments?view=azure-bot-service-4.0&tabs=csharp#send-an-adaptive-card&preserve-view=true)
+ * [Cards sample code (Bot Builder v4)](https://github.com/microsoft/BotBuilder-Samples/tree/main/samples/csharp_dotnetcore/06.using-cards)
+ * Node.js
- * [Add cards as attachments to messages](/bot-framework/nodejs/bot-builder-nodejs-send-rich-cards)
- * [Cards sample code (Bot Builder v3)](https://github.com/Microsoft/BotBuilder-Samples/tree/v3-sdk-samples/Node/cards-RichCards)
+ * [Add cards as attachments to messages](/azure/bot-service/bot-builder-howto-add-media-attachments?view=azure-bot-service-4.0&tabs=javascript#send-an-adaptive-card&preserve-view=true)
+ * [Cards sample code (Bot Builder v4)](https://github.com/microsoft/BotBuilder-Samples/tree/main/samples/javascript_nodejs/06.using-cards)
## Types of cards
An adaptive card is a customizable card that can contain any combination of text
#### Additional information on adaptive cards
-* [Adaptive cards overview](/adaptive-cards/)
-* [Adaptive card actions in Teams](~/task-modules-and-cards/cards/cards-actions.md#adaptive-cards-actions)
+Bot Framework reference:
+
+* [Adaptive cards Node](/azure/bot-service/bot-builder-howto-add-media-attachments?view=azure-bot-service-4.0&tabs=javascript#send-an-adaptive-card&preserve-view=true)
+* [Adaptive card C#](/azure/bot-service/bot-builder-howto-add-media-attachments?view=azure-bot-service-4.0&tabs=csharp#send-an-adaptive-card&preserve-view=true)
## Hero card
A card that typically contains a single large image, one or more buttons and tex
| | | | | title | Rich text | Title of the card. Maximum 2 lines. | | subtitle | Rich text | Subtitle of the card. Maximum 2 lines.|
-| text | Rich text | Text appears just below the subtitle; see [Card formatting](~/task-modules-and-cards/cards/cards-format.md) for formatting options. |
+| text | Rich text | Text appears under the subtitle; see [Card formatting](~/task-modules-and-cards/cards/cards-format.md) for formatting options. |
| images | Array of images | Image displayed at top of card. Aspect ratio 16:9. | | buttons | Array of action objects | Set of actions applicable to the current card. Maximum 6. | | tap | Action object | This action will be activated when the user taps on the card itself. |
A card that typically contains a single large image, one or more buttons and tex
Bot Framework reference:
-* [Hero card Node](https://docs.microsoft.com/javascript/api/botframework-schema/herocard)
-* [Hero card C#](https://docs.microsoft.com/dotnet/api/microsoft.bot.connector.herocard?view=botbuilder-dotnet-3.0&preserve-view=true)
+* [Hero card Node](/azure/bot-service/bot-builder-howto-add-media-attachments?view=azure-bot-service-4.0&tabs=javascript#send-a-hero-card&preserve-view=true)
+* [Hero card C#](/azure/bot-service/bot-builder-howto-add-media-attachments?view=azure-bot-service-4.0&tabs=csharp#send-a-hero-card&preserve-view=true)
## List card
The Office 365 Connector card is supported in Teams, not in Bot Framework. This
| | | | | title | Rich text | Title of the card. Maximum 2 lines. | | summary | Rich text | Summary of the card. Maximum 2 lines. |
-| text | Rich text | Text appears just below the subtitle; see [Card formatting](~/task-modules-and-cards/cards/cards-format.md) for formatting options. |
+| text | Rich text | Text appears under the subtitle; see [Card formatting](~/task-modules-and-cards/cards/cards-format.md) for formatting options. |
| themeColor | HEX string | Color that overrides the accentColor provided from the application manifest. | ### Notes on the Office 365 connector card
Office 365 connector cards function properly in Microsoft Teams, including [Acti
One important difference between using connector cards from a connector and using connector cards in your bot is the handling of card actions.
-* For a connector, the endpoint receives the card payload via HTTP POST.
+* For a connector, the endpoint receives the card payload through HTTP POST.
* For a bot, the `HttpPOST` action triggers an `invoke` activity that sends only the action ID and body to the bot. Each connector card can display a maximum of 10 sections, and each section can contain a maximum of 5 images and 5 actions.
Teams supports receipt card. It is a card that enables a bot to provide a receip
Bot Framework reference:
-* [Receipt card Node](https://docs.microsoft.com/javascript/api/botframework-schema/receiptcard?view=botbuilder-ts-latest&preserve-view=true)
-* [Receipt card C#](https://docs.microsoft.com/dotnet/api/microsoft.bot.connector.receiptcard?view=botbuilder-dotnet-3.0&preserve-view=true)
+* [Receipt card Node](/javascript/api/botframework-schema/receiptcard?view=botbuilder-ts-latest&preserve-view=true)
+* [Receipt card C#](/dotnet/api/microsoft.bot.schema.receiptcard?view=botbuilder-dotnet-stable&preserve-view=true)
## Signin card Signin card enables a bot to request a user to sign in. Supported in Teams in a slightly different form than is found in the Bot Framework. The signin card in Teams is similar to the signin card in the Bot Framework except that the signin card in Teams only supports two actions: `signin` and `openUrl`.
-The *signin action* can be used from any card in Teams, not just the signin card. For more details on authentication, see [Microsoft Teams authentication flow for bots](~/bots/how-to/authentication/auth-flow-bot.md).
+The **signin action** can be used from any card in Teams, not just the signin card. For more details on authentication, see [Microsoft Teams authentication flow for bots](~/bots/how-to/authentication/auth-flow-bot.md).
### Support for Signin cards
The *signin action* can be used from any card in Teams, not just the signin card
Bot Framework reference: * [Signin card Node](/javascript/api/botframework-schema/signincard?view=botbuilder-ts-latest&preserve-view=true)
-* [Signin card C#](/dotnet/api/microsoft.bot.connector.signincard?view=botbuilder-dotnet-3.0&preserve-view=true)
+* [Signin card C#](/dotnet/api/microsoft.bot.schema.signincard?view=botbuilder-dotnet-stable&preserve-view=true)
## Thumbnail card
A card that typically contains a single thumbnail image, one or more buttons, an
| | | | | title | Rich text | Title of the card. Maximum 2 lines.| | subtitle | Rich text | Subtitle of the card. Maximum 2 lines.|
-| text | Rich text | Text appears just below the subtitle; see [Card formatting](~/task-modules-and-cards/cards/cards-format.md) for formatting options. |
+| text | Rich text | Text appears under the subtitle; see [Card formatting](~/task-modules-and-cards/cards/cards-format.md) for formatting options. |
| images | Array of images | Image displayed at top of card. Aspect ratio 1:1 (square). | | buttons | Array of action objects | Set of actions applicable to the current card. Maximum 6. | | tap | Action object | This action will be activated when the user taps on the card itself. |
A card that typically contains a single thumbnail image, one or more buttons, an
Bot Framework reference:
-* [Thumbnail card Node](https://docs.microsoft.com/javascript/api/botframework-schema/thumbnailcard?view=botbuilder-ts-latest&preserve-view=true)
-* [Thumbnail card C#](https://docs.microsoft.com/dotnet/api/microsoft.bot.connector.thumbnailcard?view=botbuilder-dotnet-3.0&preserve-view=true)
+* [Thumbnail card Node](/javascript/api/botframework-schema/thumbnailcard?view=botbuilder-ts-latest&preserve-view=true)
+* [Thumbnail card C#](/dotnet/api/microsoft.bot.schema.thumbnailcard?view=botbuilder-dotnet-stable&preserve-view=true)
## Card collections
Card collections: `builder.AttachmentLayout.carousel` and `builder.AttachmentLay
## Carousel collection
-The [carousel layout](/azure/bot-service/dotnet/bot-builder-dotnet-add-rich-card-attachments?view=azure-bot-service-3.0&preserve-view=true) shows a carousel of cards, optionally with associated action buttons.
+The [carousel layout](/azure/bot-service/bot-builder-howto-add-media-attachments?view=azure-bot-service-4.0&tabs=csharp#send-a-carousel-of-cards&preserve-view=true) shows a carousel of cards, optionally with associated action buttons.
### Support for carousel collections
platform Connectors Creating https://github.com/MicrosoftDocs/msteams-docs/commits/master/msteams-platform/webhooks-and-connectors/how-to/connectors-creating.md
Here's a sample HTML to create a Connector configuration page without the CSS:
}); microsoftTeams.settings.registerOnRemoveHandler(function (removeEvent) {
- var removeCalled = true;
alert("Removed" + JSON.stringify(removeEvent)); });