| 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 | Teams activity handler is derived from Microsoft Bot Framework's activity handle When a bot for Teams receives an activity, it's routed to the activity handlers. All activities are routed through one base handler called the turn handler. The turn handler calls the required activity handler to manage any activity received. The Teams bot is derived from `TeamsActivityHandler` class, which is derived from the Bot Framework's `ActivityHandler` class. +> [!NOTE] +> If the bot activity takes more than 15 seconds to process, Teams send a retry request to bot endpoint. Hence, you'll see duplicate requests in your bot. + # [C#](#tab/csharp) Bots are created using the Bot Framework. If the bots receive a message activity, then the turn handler receives a notification of that incoming activity. The turn handler then sends the incoming activity to the `OnMessageActivityAsync` activity handler. In Teams, this functionality remains the same. If the bot receives a conversation update activity, then the turn handler receives a notification of that incoming activity and sends the incoming activity to `OnConversationUpdateActivityAsync`. The Teams activity handler first checks for any Teams specific events. If no events are found, it then passes them along to the Bot Framework's activity handler. |
| platform | Conversation Messages | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/bots/how-to/conversations/conversation-messages.md | Form completion message appears in Adaptive Cards while sending a response to th * **Success**: When a response sent to the bot is successful, **Your response was sent to the app** message appears. --You can select **Close** or switch chat to dismiss the message. --**Response on mobile**: --The error message appears at the bottom of the Adaptive Card. + :::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). |
| platform | Apps Upload | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/concepts/deploy-and-publish/apps-upload.md | You can sideload Microsoft Teams apps without having to publish to your organiza * You built an app for yourself to automate a workflow. * You built an app for a small set of users, such as, your work group. +> [!NOTE] +> Sideloading your app multiple times displays more than one instance for messaging extensions. + > [!IMPORTANT] > Currently, sideloading apps are available in Government Community Cloud (GCC), but are not available for GCC-High and Department of Defense (DOD). |
| platform | Link Unfurling | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/messaging-extensions/how-to/link-unfurling.md | To add link unfurling to your app manifest, add a new `messageHandlers` array to ### Add link unfurling manually +> [!NOTE] +> If authentication is added through Azure AD, [unfurl links in Teams using bot](/microsoftteams/platform/sbs-botbuilder-linkunfurling?tabs=vs&tutorial-step=4). + To enable your message extension to interact with links, first you must add the `messageHandlers` array to your app manifest. The following example explains how to add link unfurling manually: ```json |
| platform | Respond To Search | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/messaging-extensions/how-to/search-commands/respond-to-search.md | Your service must respond with the results matching the user query. The response |Property name|Purpose| ||| |`composeExtension`|Top-level response envelope.|-|`composeExtension.type`|Type of response. The following types are supported: <br>`result`: Displays a list of search results <br>`auth`: Asks the user to authenticate <br>`config`: Asks the user to set up the message extension <br>`message`: Displays a plain text message | +|`composeExtension.type`|Type of response. The following types are supported: <br>`result`: Displays a list of search results <br>`auth`: Prompts the user to authenticate <br>`config`: Prompts the user to set up the message extension <br>`message`: Displays a plain text message | |`composeExtension.attachmentLayout`|Specifies the layout of the attachments. Used for responses of type `result`. <br>Currently, the following types are supported: <br>`list`: A list of card objects containing thumbnail, title, and text fields <br>`grid`: A grid of thumbnail images | |`composeExtension.attachments`|Array of valid attachment objects. Used for responses of type `result`. <br>Currently, the following types are supported: <br>`application/vnd.microsoft.card.thumbnail` <br>`application/vnd.microsoft.card.hero` <br>`application/vnd.microsoft.teams.card.o365connector` <br>`application/vnd.microsoft.card.adaptive`| |`composeExtension.suggestedActions`|Suggested actions. Used for responses of type `auth` or `config`. | |
| platform | Create Messaging Extension Using Appstudio | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/resources/create-messaging-extension-using-appstudio.md | At a high level, you'll need to complete the following steps to create a messagi Creating your web service, creating your app package, and registering your web service with the Bot Framework can be done in any order. Because those three pieces are so intertwined, no matter which order you do them in you'll need return to update the others. Your registration needs the messaging endpoint from your deployed web service, and your web service needs the ID and password created from your registration. Your app manifest also needs that ID to connect Teams to your web service. -As you're building your messaging extension, you'll regularly be moving between changing your app manifest, and deploying code to your web service. When working with the app manifest, keep in mind that you can either manually manipulate the JSON file, or make changes through App Studio. Either way, you'll need to re-deploy (upload) your app in Teams when you make a change to the manifest, but there's no need to do so when you deploy changes to your web service. +As you're building your messaging extension, you'll regularly be moving between changing your app manifest, and deploying code to your web service. When working with the app manifest, ensure that you can either manually modify the JSON file, or make changes through App Studio. Either way, you'll need to re-deploy (upload) your app in Teams when you make a change to the manifest, but there's no need to do so when you deploy changes to your web service. [!include[prepare environment](~/includes/prepare-environment.md)] |
| platform | Search Extensions | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/resources/messaging-extension-v3/search-extensions.md | Your service should respond with the results matching the user query. The respon |Property name|Purpose| ||| |`composeExtension`|Top-level response envelope.|-|`composeExtension.type`|Type of response. The following types are supported: <br>`result`: displays a list of search results <br>`auth`: asks the user to authenticate <br>`config`: asks the user to set up the message extension <br>`message`: displays a plain text message | +|`composeExtension.type`|Type of response. The following types are supported: <br>`result`: displays a list of search results <br>`auth`: Prompts the user to authenticate <br>`config`: Prompts the user to set up the message extension <br>`message`: displays a plain text message | |`composeExtension.attachmentLayout`|Specifies the layout of the attachments. Used for responses of type `result`. <br>Currently the following types are supported: <br>`list`: a list of card objects containing thumbnail, title, and text fields <br>`grid`: a grid of thumbnail images | |`composeExtension.attachments`|Array of valid attachment objects. Used for responses of type `result`. <br>Currently the following types are supported: <br>`application/vnd.microsoft.card.thumbnail` <br>`application/vnd.microsoft.card.hero` <br>`application/vnd.microsoft.teams.card.o365connector` <br>`application/vnd.microsoft.card.adaptive`| |`composeExtension.suggestedActions`|Suggested actions. Used for responses of type `auth` or `config`. | |
| platform | Moodleinstructions | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/resources/moodleInstructions.md | Use the generated `AppID` and `Key` in your Microsoft 365 Moodle Plugins setup p 1. On the **Teams Settings** page, configure the required settings to enable the Teams app integration. - 1. To enable **OpenID Connect**, select the **Manage Authentication** link, and select the eye icon on the **OpenId Connect** line if it is greyed out. + 1. To enable **OpenID Connect**, select the **Manage Authentication** link, and select the eye icon on the **OpenId Connect** line if it is unavailable. 1. To enable frame embedding, select the **HTTP Security** link, and then select the checkbox next to **Allow frame embedding**. 1. To enable web services, which enables the Moodle API features, select the **Advanced Features** link, and then ensure the checkbox next to **Enable web services** is selected. 1. To enable the external services for Microsoft 365, select the **External services** link, and then: |
| platform | Manifest Schema | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/resources/schema/manifest-schema.md | An array of `string`, which specifies which permissions the app requests, which Changing these permissions during app update, causes your users to repeat the consent process after they run the updated app. For more information, see [Updating your app](~/concepts/deploy-and-publish/appsource/post-publish/overview.md). +> [!NOTE] +> Permissions are deprecated now. + ## devicePermissions **Optional**ΓÇöarray of strings |
| platform | Auth Silent Aad | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/tabs/how-to/authentication/auth-silent-aad.md | keywords: teams authentication SSO silent Azure AD tab # Silent authentication > [!IMPORTANT]-> Microsoft support and development for Active Directory Authentication Library (ADAL) including the security fixes, ends on **June 30, 2022**. Update your applications to use Microsoft Authentication Library (MSAL) to continue receiving support. See [Migrate applications to the Microsoft Authentication Library (MSAL)](/azure/active-directory/develop/msal-migration). +> Microsoft support and development for Active Directory Authentication Library (ADAL) including the security fixes, ends on **June 30, 2022**. To continue receiving support, update your applications to use Microsoft Authentication Library (MSAL).See [Migrate applications to the Microsoft Authentication Library (MSAL)](/azure/active-directory/develop/msal-migration). > [!NOTE] > For authentication to work for your tab on mobile clients, ensure that you're using Teams JavaScript SDK version 1.4.1 or later. |
| platform | Tab Sso Troubleshooting | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/tabs/how-to/authentication/tab-sso-troubleshooting.md | When Azure AD receives a request for accessing a Microsoft Graph resource, it ch Your code must tell the client (for example, in the body of a 403 Forbidden response) how to handle the error: -- If the tab app needs Microsoft Graph scopes for which only an administrator can give consent, your code should throw an error.+- If the tab app needs Microsoft Graph scopes for which only an administrator can give consent, your code should generate an error. - If the only scopes that are needed can be consented to by the user, then your code should fall back to an alternate system of user authentication. </details> |
| platform | Using Teams Client Sdk | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/tabs/how-to/using-teams-client-sdk.md | The following table lists Teams tabs and dialogs (task modules) capabilities (pu #### App permissions -App capabilities that require the user to grant [device permissions](../../concepts/device-capabilities/device-capabilities-overview.md) (such as *location*) aren't yet supported for apps running outside of Teams. There is currently no way to check app permissions in Settings or your app header when running in Outlook or Office. If a Teams app running in Office or Outlook calls a TeamsJS (or HTML5) API that triggers device permissions, that API will throw an error and fail to display a system dialog asking for user consent. +App capabilities that require the user to grant [device permissions](../../concepts/device-capabilities/device-capabilities-overview.md) (such as *location*) aren't yet supported for apps running outside of Teams. There is currently no way to check app permissions in Settings or your app header when running in Outlook or Office. If a Teams app running in Office or Outlook calls a TeamsJS (or HTML5) API that triggers device permissions, that API will generates an error and fail to display a system dialog asking for user consent. Current guidance for now is to modify your code to catch the failure: * Check [isSupported()](#differentiate-your-app-experience) on a capability before using it. `media`, `meeting`, and `files` do not yet support *isSupported* calls and do not yet work outside of Teams. * Catch and handle errors when calling TeamsJS and HTML5 APIs. -When an API is unsupported or throws an error, add logic to fail gracefully or provide a workaround. For example: +When an API is unsupported or generates an error, add logic to fail gracefully or provide a workaround. For example: * Direct the user to your app's website. * Direct the user to use the app in Teams to complete the flow. async function example() { A *capability* is a logical grouping (via namespace) of APIs that provide similar functionality. You can think of Microsoft Teams, Outlook, and Office, as hosts to your tab app. A host supports a given capability if it supports all the APIs defined within that capability. A host can't partially implement a capability. Capabilities can be feature- or content-based, such as *authentication*, or *dialog*. There are also capabilities for application types such as *pages*, and other groupings. -Starting with TeamsJS v.2.0, APIs are defined as functions in a JavaScript namespace whose name matches their required capability. For example, if an app is running in a host that supports the *dialog* capability, then the app can safely call APIs such as `dialog.open` (in addition to other dialog-related APIs defined in the namespace). If an app attempts to call an API that's not supported in that host, the API will throw an exception. To verify if the current host running your app supports a given capability, call the [isSupported()](#differentiate-your-app-experience) function of its namespace. +Starting with TeamsJS v.2.0, APIs are defined as functions in a JavaScript namespace whose name matches their required capability. For example, if an app is running in a host that supports the *dialog* capability, then the app can safely call APIs such as `dialog.open` (in addition to other dialog-related APIs defined in the namespace). If an app attempts to call an API that's not supported in that host, the API generates an exception. To verify if the current host running your app supports a given capability, call the [isSupported()](#differentiate-your-app-experience) function of its namespace. #### Differentiate your app experience |
| platform | Cards Reference | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/task-modules-and-cards/cards/cards-reference.md | Before you identify the different card types, understand how to create a hero ca To create a hero card, thumbnail card, or Adaptive Card from App Studio: -1. Go to **App Studio** from Teams. -1. Select **Card editor**. -1. Select **Create a new card**. -1. Select **Create** for one of the cards from **Hero Card**, **Thumbnail Card**, or **Adaptive Card**. The metadata details, buttons, and json, csharp, and node code examples are shown for that card. +1. Go to [Developer Portal for Teams](https://dev.teams.microsoft.com/home). +1. Select **Design and build Adaptive cards**. +1. Select **New card**. +1. Enter card name and select **Save**. +1. Select one of the cards from **Hero Card**, **Thumbnail Card**, or **Adaptive Card**. - :::image type="content" source="../../assets/images/Cards/Herocarddetails.png" alt-text="Hero card details"::: + :::image type="content" source="../../assets/images/Cards/Herocarddetailsteams.PNG" alt-text="herocard"::: +1. Select **Save**. 1. Select **Send me this card**. The card is sent to you as a chat message. ## Card examples |
| platform | Whats New | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/whats-new.md | Microsoft Teams platform features that are available to all app developers. | **Date** | **Update** | **Find here** | | -- | | -|+| 06/08/2022 | Optional card feedback for success message| Build bots > Bot conversations > [Messages in bot conversations](~/bots/how-to/conversations/conversation-messages.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) | |