+* Have a Microsoft Developer account and be familiar with the Teams [Developer Portal](../concepts/build-and-test/teams-developer-portal.md).

+Microsoft has a Scene studio that allows you to build scenes. It's available on [Scenes Editor - Teams Developer Portal](https://dev.teams.microsoft.com/scenes). This document refers to Scene studio in the Teams Developer Portal.

+This document guides you on how to make your chatbot available in Teams through the Power Virtual Agents portal, and add your bot to Teams using Developer Portal.

+## Add your bot to Teams using Developer Portal

+If [uploading custom apps is enabled](/microsoftteams/admin-settings) in your Teams instance, you can use Teams Developer Portal to directly upload your chatbot and start using it immediately. To share your chatbot, you can request your admin to make your bot available in the tenant app catalog or you can send your app package to others and ask them to upload it independently.

+1. **Install Developer Portal in Teams**

+ Install Developer Portal from the Teams store that simplifies the process of bot creation and registration in Teams:

+ 1. Select the app store icon from Teams instance, and search for **Developer Portal**.

+ :::image type="content" source="../../assets/images/tdp/dev-portal-app.png" alt-text="Screenshot shows how to add Developer Portal apps in Teams client." lightbox="../../assets/images/tdp/add-dev-portal.png":::

+ 1. Select the **Developer Portal** and select **Add** in the pop-up dialog box.

+ :::image type="content" source="../../assets/images/tdp/home-page-dev-portal.png" alt-text="Screenshot shows home page of the Developer Portal apps in Teams client.":::

+1. **Create the Teams app manifest in Developer Portal**

+ 1. Bots in Teams are defined by an app manifest JSON file that provides the basic information about your bot and its capabilities. In **Developer Portal**, select **Apps**, and select **New app**.

+ :::image type="content" source="../../assets/images/tdp/create-new-app.png" alt-text="Screenshot shows how to create Teams app manifest in Developer Portal.":::

+ 1. Enter your app name and select **Save**.

+1. **Set up your bot**

+ To set up your bot, perform the following steps:

+ 1. Go to **App features** > **Bots**.

+ 1. Select **Enter a bot ID** and then enter your bot ID.

+ 1. Select required scopes and then select **Save**.

+ This step is only applicable, if you want your user to sign in to the bot:

+ 1. Go to **Domains** under **Configure** section.

+ 1. Select **Create your first domain** and enter a valid domain.

+ 1. Select **Add**.

+ Select **Preview in Teams** to add your bot directly to your Teams instance. Alternately, you can download the completed app package to share with Teams users or provide it to your admin to make your bot available in the tenant app catalog.

+ The set up process for adding your Power Virtual Agents chat bot to Teams is complete. You can now start a conversation with your bot in a personal chat.

+1. Select the three dots (●●●) in the left panel. Then select the **Developer Portal** icon.

+Command menus are defined in your app manifest. You can either use **Developer Portal** to create them or add them manually in the app manifest.

+### Create a command menu for your bot using Developer Portal

+To create a command menu for your bot using Developer Portal:

+1. Open Teams and select **Apps** from the left pane. In the **Apps** page, search for **Developer Portal**, and then select **Open**.

+ :::image type="content" source="../../assets/images/tdp/add-dev-portal.png" alt-text="Screenshot shows how to add Developer Portal in Teams client.":::

+

+1. In **Developer Portal**, select the **Apps** tab. If you don't have an existing app package, you can create or import an existing app. For more information, see [Developer Portal for Teams](../../concepts/build-and-test/teams-developer-portal.md).

+1. Select **Apps** tab, select **App features** from the left pane, and then select **Bots**.

+1. Select **Add a command** under **Commands** section.

+ :::image type="content" source="../../assets/images/tdp/add-a-bot-command.png" alt-text="Screenshot shows how to add a command for your bot in Developer Portal.":::

+1. Enter the **Command** that appears as the command menu for your bot.

+1. Enter the **Description** that appears under the command text in the menu. **Description** must be a brief explanation of the purpose of the command.

+1. Select the **Scope** check box and then select **Add**.

+ This defines where the command menu must appear.

+ :::image type="content" source="../../assets/images/tdp/bot-command.png" alt-text="Screenshot shows how to add a command, description and scopes for your bot.":::

+description: Learn about testing and debugging your bot locally with an IDE within Teams environment via sideloading and more.

+The most comprehensive way to test your bot is by creating an app package and uploading it to Teams. Uploading the app package to Teams is the only method to test the full functionality available to your bot, across all scopes.

+* Use [Developer Portal for Teams](~/concepts/build-and-test/teams-developer-portal.md).

+Initiate a conversation with your bot by using its ID. When a bot is added through one of these methods, it isn't addressable in channel conversations, and you can't take advantage of other Teams app capabilities like tabs or message extensions. Initiate a conversation in one of the following ways:

+ 2. Open Microsoft Teams, on the Chat pane, selects the **Add chat** icon. In **To:**, paste your bot's Microsoft App ID.

+To remove your bot completely from Teams, go to your **Bot Dashboard** and edit the Teams channel. Choose the **Delete** button at the bottom. Deleting a bot from Teams prevents users from discovering, adding, and interacting with your bot. Deleting a bot from Teams doesn't remove the bot from other user's Teams instances, however, it stops functioning for them as well.

+> To update the messaging endpoint for a bot, you must use the Bot Framework. Select your bot in [your list of bots in Bot Framework](https://dev.botframework.com/bots). You do not need to migrate your bot to Microsoft Azure. You can also update your messaging endpoint through [Developer Portal for Teams](~/concepts/build-and-test/teams-developer-portal.md).

+ Title: Teams Connect shared channels

+description: Learn about Teams Connect shared channels to securely collaborate with internal and external users in a shared space without switching tenants.

+localization_priority: Normal

+# Microsoft Teams Connect shared channels

+Microsoft Teams Connect shared channels allow members of a channel to collaborate with users across other teams and organizations. You can create and share a shared channel with:

+* Members of another team within the same organization.

+* Individuals within the same organization.

+* Individuals and other teams of other organizations.

+Teams Connect shared channels facilitate secure collaboration seamlessly. Allow external users outside of your organization to collaborate with internal users in Teams without changing their user context. Enhance user experience unlike using guest accounts, for example, the members must sign out of Teams and sign in again using a guest account. Teams applications extend the powerful collaboration space.

+## Enable your app for shared channels

+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"

+ ]

+ }

+ }

+```

+> [!NOTE]

+>

+> * If your app supports the team scope, it functions in standard channels, regardless of what values are defined in this property.

+> * Your app may need to account for the unique properties of each of these channel types in order to function properly.

+## Get context for shared channels

+When the content UX is loaded in a shared channel, use the data received from `getContext` call for shared channel changes. `getContext` call publishes two new properties, `hostTeamGroupID` and `hostTenantID`, which are used to retrieve channel membership using Microsoft Graph APIs. `hostTeam` is the team that creates the shared channel.

+For more information to enable your tab, see:

+* [Get context for your tab for private channels](../../tabs/how-to/access-teams-context.md#retrieve-context-in-private-channels)

+* [Get context for your tab for shared channels](../../tabs/how-to/access-teams-context.md#retrieve-context-in-microsoft-teams-connect-shared-channels)

+## Apps and permissions in shared channels

+You can collaborate with external members outside of your organization using shared channels. App permissions in shared channels follow the host team's app roster and host tenant's app policy.

+> [!NOTE]

+> The [activity feed notification API](/graph/teams-send-activityfeednotifications) doesn't support cross-tenant notifications for apps in a shared channel.

+## Get shared channel membership

+You can get direct shared channel membership by using the `hostTeamGroupID` from `getContext` and following these steps:

+1. Get direct members with [GET channel members API](/graph/api/channel-list-members?view=graph-rest-beta&tabs=http&preserve-view=true) API.

+ ```http

+ GET /teams/{host-team-group-id}/channels/{channel-id}/members

+ ```

+2. Get each shared team with GET `sharedWithTeams` API.

+ ```http

+ GET /teams/{host-team-group-id}/channels/{channel-id}/sharedWithTeams

+ ```

+3. Use GET members of each shared team (Team X) with GET `sharedWithTeams` API.

+ ```http

+ GET /teams/{host-team-group-id}/channels/{channel-id}/sharedWithTeams/{teamX}/members

+ ```

+## Classify members in the shared channel as in-tenant or out-tenant

+You can classify members as in-tenant or out-tenant by comparing `tenantID` of the member or team with `hostTeamTenantID` as follows:

+1. Get the member you wish to compare.

+ ```http

+ GET /teams/{host-team-group-id}/channels/{channel-id}/members

+ ```

+2. Use `getContext`, compare the `tenantID` of the member to the `hostTenantID` property.

+## Azure AD native identity

+Apps must function cross-tenants in installation and usage. The following table lists the channel types and their corresponding group IDs:

+|Channel type| groupId | hostTeamGroupId |

+|-||--|

+|Regular | Team Azure AD group ID | Team Azure AD group ID |

+|Shared | Empty | Host Team Azure AD group ID |

+## See also

+* [Build tabs for Teams](../../tabs/what-are-tabs.md)

+* [App manifest schema for Teams](../../resources/schem)

+> [!VIDEO <https://www.microsoft.com/videoplayer/embed/RE4WG3l>]

+1. Go to the [Microsoft Teams app validation tool](https://dev.teams.microsoft.com/appvalidation.html). (Note: The tool is also available in [Developer Portal for Teams](~/concepts/build-and-test/teams-developer-portal.md)

+- [Microsoft Teams samples](https://github.com/OfficeDev/Microsoft-Teams-Samples#microsoft-teams-samples)

+- [Git and GitHub resources](/contribute/additional-resources)

+> [!VIDEO <https://www.microsoft.com/en-us/videoplayer/embed/RE4OANG>]

+* [Create an action command using Developer Portal](#create-an-action-command-using-developer-portal)

+### Create an action command using Developer Portal

+You can create an action command using **Developer Portal**.

+To create an action command:

+1. Open **Developer Portal** from the Microsoft Teams client and select the **Apps** tab.

+ If you already created your app package in **Developer Portal**, select from the list. If you haven't created an app package, import an existing one.

+1. After importing an app package, select **Message extensions** under **App features**.

+1. To create a message extension, you need a Microsoft registered bot. You can either use an existing bot or create a new bot. Select **Create new bot** option, give a name to the new bot, and then select **Create**.

+ :::image type="content" source="../../../assets/images/tdp/bot-page.png" alt-text="The screenshot show you how to create a bot in Developer Portal.":::

+1. To use an existing bot, select **Select an existing bot** and choose the existing bots from the dropdown list or select **Enter a bot ID** if you have a bot id created already.

+1. Select the scope of the messaging extension and select **Save**.

+1. Select **Add a command** in the **Command** section to include the commands, which decides the behavior of message extension.

+ :::image type="content" source="../../../assets/images/tdp/add-a-command.PNG" alt-text="Screenshot shows how to add a command to define the behavior of the message extension.":::

+1. Select **Action** and then select parameter type.

+1. Enter **Command ID**, **Command title**, and **Command description**.

+1. Enter all the parameters and select the type of input from the dropdown list.

+ :::image type="content" source="../../../assets/images/tdp/add-a-command-parameter.PNG" alt-text="Screenshot shows how to add a parameters to define your command for message extension.":::

+1. Select **Add a domain** under **Preview links**.

+1. Enter valid domain and then select **Add**.

+ :::image type="content" source="../../../assets/images/tdp/add-domain.PNG" alt-text="Screenshot shows how to add a valid domain to your messaging extension for link unfurlings.":::

+1. Select **Save**.

+ :::image type="content" source="../../../assets/images/tdp/add-a-command-save.PNG" alt-text="Screenshot shows how to save all your setting and parameters for your message extension.":::

+**To add additional parameters**

+1. Select ellipse under command section and then select **Edit parameter**.

+ :::image type="content" source="../../../assets/images/tdp/edit-parameters.PNG" alt-text="Screenshots shows how to add additional parameters for your message extension.":::

+1. Select **Add a Parameters** and enter all the parameters.

+ :::image type="content" source="../../../assets/images/tdp/add-parameter.PNG" alt-text="Screenshot shows how to add additional parameters for your message extension."lightbox="../../../assets/images/tdp/add-a-parameters.PNG":::

+ "botId": "c8fa3cf6-b1f0-4ba8-a5bf-a241bc29adf3",

+ "scopes": [

+ "personal",

+ "groupchat"

+ ],

+ "id": "To do",

+ "title": "Create To do",

+ "description": "Create a To do",

+ "initialRun": true,

+ "context": [

+ "commandBox",

+ "compose"

+ ],

+ "description": "To do Title",

+ "description": "Description of the task",

+ "description": "Due date for the task",

+ }

+ ],

+ "canUpdateConfiguration": true,

+ "messageHandlers": [

+ "type": "link",

+ "value": {

+ "domains": [

+ "yourapp.onmicrosoft.com"

+ ]

+ }

+This document guides you on how to add link unfurling to your app manifest using Developer Portal or manually. With link unfurling, your app can register to receive an `invoke` activity when URLs with a particular domain are pasted into the compose message area. The `invoke` contains the full URL that was pasted into the compose message area. You can respond with a card that the user can unfurl for additional information or actions. This works as a search command with the URL as the search term.

+To add link unfurling to your app manifest, add a new `messageHandlers` array to the `composeExtensions` section of your app manifest JSON. You can add the array with the help of Developer Portal or manually. Domain listings can include wildcards, for example `*.example.com`. This matches exactly one segment of the domain; if you need to match `a.b.example.com` then use `*.*.example.com`.

+### Add link unfurling using Developer Portal

+1. Open **Developer Portal** from the Microsoft Teams client and then select the **Apps** tab.

+1. On the **Messaging Extension** page under **App features**, select existing bot or create a new bot.

+1. Select **Save**.

+1. Select **Add a domain** under **Preview links** section and then enter valid domain.

+1. Select **Add**. The following image explains the process:

+ :::image type="content" source="../../assets/images/tdp/add-domain-button.PNG" alt-text="Screenshot of the message handlers section in Developer Portal." lightbox="../../assets/images/tdp/add-domain.PNG":::

+> [!VIDEO <https://www.microsoft.com/en-us/videoplayer/embed/RE4OIvK>]

+To add the search command to your app manifest, you must add a new `composeExtension` object to the top level of your app manifest JSON. You can add the search command either with the help of Developer Portal, or manually.

+### Create a search command using Developer Portal

+**To create an action command**

+1. Open **Developer Portal** from the Microsoft Teams client and select the **Apps** tab.

+ If you already created your app package in **Developer Portal**, select from the list. If you haven't created an app package, import an existing one.

+1. After importing an app package, select **Message extensions** under **App features**.

+1. To create a message extension, you need a Microsoft registered bot. You can either use an existing bot or create a new bot. Select **Create new bot** option, give a name to the new bot, and then select **Create**.

+ :::image type="content" source="../../../assets/images/tdp/bot-page.png" alt-text="The screenshot show you how to create a bot in Developer Portal.":::

+1. To use an existing bot, select **Select an existing bot** and choose the existing bots from the dropdown list, or select **Enter a bot ID** if you have a bot ID created already.

+1. Select the scope of the messaging extension and select **Save**.

+1. Select **Add a command** in the **Command** section to include the commands, which decides the behavior of message extension.

+The following image displays command addition for message extension:

+ :::image type="content" source="../../../assets/images/tdp/add-a-command.PNG" alt-text="The screenshot shows how to add a command to define the behavior of the message extension.":::

+1. Select **Search** and enter **Command ID**, **Command title**, and **Command description**.

+1. Enter all the parameters and select the type of input from the dropdown list.

+ :::image type="content" source="../../../assets/images/tdp/add-a-command-parameter.PNG" alt-text="The screenshot shows how to add a parameter to define your command for message extension.":::

+1. Select **Add a domain** under **Preview links**.

+1. Enter valid domain and then select **Add**.

+ :::image type="content" source="../../../assets/images/tdp/add-domain.PNG" alt-text="Screenshot shows how to add a valid domain to your messaging extension for link unfurlings.":::

+1. Select **Save**.

+ :::image type="content" source="../../../assets/images/tdp/add-a-command-save.PNG" alt-text="Screenshot shows how to save all your setting and parameters for your message extension.":::

+**To add additional parameters**

+1. Select ellipse under command section and then select **Edit parameter**.

+ :::image type="content" source="../../../assets/images/tdp/edit-parameters.PNG" alt-text="Screenshots shows how to add additional parameters for your message extension.":::

+1. Select **Add a Parameters** and enter all the parameters.

+ :::image type="content" source="../../../assets/images/tdp/add-parameter.PNG" alt-text="Screenshot shows how to add additional parameters for your message extension."lightbox="../../../assets/images/tdp/add-a-parameters.PNG":::

+| `id` | This property is a unique ID that you assign to search command. The user request includes this ID. | Yes | 1.0 |

+You must add the details of the search parameter that defines the text visible to your user in the Teams client.

+Without the Azure Bot ServiceΓÇÖs OAuthCard, it's complicated to implement authentication in a bot. It's a full-stack challenge that involving building a web experience, integrating with external OAuth providers, token management, and handling the right server-to-server API calls to complete authentication flow securely. This can result in clunky experiences requiring the entry of ΓÇ£magic numbersΓÇ¥.

+With Azure Bot ServiceΓÇÖs OAuthCard, it's easier for your Teams bot to sign in your users and access external data providers. Whether youΓÇÖve already implemented auth and you want to switch over to something simpler, or if you're looking to add authentication to your bot service for the first time, the OAuthCard can make it easier.

+Other topics in [Authentication](~/resources/bot-v3/bot-authentication/auth-flow-bot.md) describe authentication without using the OAuthCard, so if you want to understand authentication in Teams more deeply, or have a situation where you can't use the OAuthCard, you can still refer to those topics.

+Full documentation using the OAuthCard is available in the topic: [Add authentication to your bot via Azure Bot Service](/azure/bot-service/bot-builder-tutorial-authentication?view=azure-bot-service-3.0&preserve-view=true). Note that this topic is in the Azure Bot Framework documentation set, and isn't specific to Teams.

+* Is seamless for end users: complete the full sign-in experience right within Teams.

+> This guide is using the Bot Framework v3 SDK. You can find the v4 implementation [here](/azure/bot-service/bot-builder-authentication?view=azure-bot-service-4.0&tabs=csharp&preserve-view=true). You will still need to create a manifest and include token.botframework.com in the `validDomains` section, because otherwise the Sign in button won't open the authentication window. Use the [Developer Portal](~/concepts/build-and-test/teams-developer-portal.md) to generate your manifest.

+Your bot, just as it is, may be entirely relevant in all scopes without requiring more work. In Teams, there's no expectation that your bot function in all scopes, but you should ensure that your bot provides user value in whichever scope(s) you choose to support. For more information on scopes, see [Apps in Microsoft Teams](~/concepts/build-and-test/teams-developer-portal.md).

+When your bot is first added to the group or team, it's useful to send a welcome message introducing the bot to all users. The welcome message should provide a description of the botΓÇÖs functionality and user benefits. Ideally the message should also include commands for the user to interact with the app. To do this, ensure that your bot responds to the `conversationUpdate` message, with the `teamsAddMembers` eventType in the `channelData` object. Be sure that the `memberAdded` ID is the bot's App ID itself, because the same event is sent when a user is added to a team. For more information, see [Team member or bot addition](~/resources/bot-v3/bots-notifications.md#team-member-or-bot-addition).

+* The team is large (obviously subjective, for example, more than 100 members). Your bot may be seen as 'spammy' and the person who added it may get complaints unless you clearly communicate your bot's value proposition to everyone who sees the welcome message.

+Your bot can do more than send and receive messages in groups and teams. For instance, it can also fetch the list of members, including their profile information, and the list of channels. For more information, see [Get context for your Microsoft Teams bot](~/resources/bot-v3/bots-context.md).

+**Teams Developer Portal for Teams** is a tool that can help create your bot, and an app package that references your bot. It also contains a React control library and configurable samples for cards. For more information, see [Getting started with Teams Developer Portal for Teams](~/concepts/build-and-test/teams-developer-portal.md). The steps that follow assume that you are hand configuring your bot and not using **Teams Developer Portal for Teams**:

+> * You can now use Developer Portal for Teams to register/update app and bot information directly within Teams. You'll only have to use the Azure portal for adding or configuring other Bot Framework channels such as Direct Line, Web Chat, Skype, and Facebook Messenger.

+*Developer Portal for Teams* helps you create and configure your app manifest, and can create your Bot Framework bot for you. It also contains a React control library and an interactive card builder.

+When testing your bot you have to take into consideration both the context(s) you want your bot to run in, and any functionality you may have added to your bot that requires data specific to Microsoft Teams. Ensure that the method you chose to test your bot aligns with its functionality.

+The most comprehensive way to test your bot is by creating an app package and uploading it to Teams. Uploading the app to Teams is the only method to test the full functionality available to your bot, across all scopes.

+There are two methods for uploading your app. You can either use [Developer Portal for Teams](~/concepts/build-and-test/teams-developer-portal.md) or you can manually [create an app package](~/concepts/build-and-test/apps-package.md) and [upload your app](~/concepts/deploy-and-publish/apps-upload.md). If you need to alter your manifest, and reupload your app, you should [delete your bot](#deleting-a-bot-from-teams) before uploading your altered app package.

+To stop your bot receiving messages, go to your Bot Dashboard and edit the Microsoft Teams channel. Clear the **Enable on Microsoft Teams** option. Disabling a bot in Teams prevents users from interacting with the bot, but it will still be discoverable and users can add it to teams.

+To remove your bot completely from Teams, go to your Bot Dashboard and edit the Microsoft Teams channel. Choose the **Delete** button at the bottom. Deleting a bot from Teams prevents users from discovering, adding, or interacting with your bot. Deleting a bot from Teams doesn't remove the bot from other users' Teams instances, although it will cease functioning for them as well.

+Many features enabled in developer preview will require alterations to your app manifest JSON file. To do so, you'll need to use the [developer preview manifest schema](~/resources/schem) to make these changes, nor will you be able to use it to upload your app for testing. To upload your app you'll need to select the `More apps` icon on the app bar, then select the `Upload a custom app link`. Using this method you can only upload a zipped version of your app package.

+You may find it useful to use Developer Portal for Teams to create the non-developer preview portions of your app package, then export that package and manually edit the `manifest.json` file to add the developer preview features you wish to use. Once you've added developer preview features to the `manifest.json` file, you won't be able to re-import the package into Developer Portal for Teams.

+ "$schema": "https://developer.microsoft.com/en-us/json-schemas/teams/v1.9/MicrosoftTeams.Localization.schema.json",

+ "name.short": "Portail de Développement",

+ "name.full": "Portail des développeurs",

+ "description.short": "Configurer, distribuer et gérer vos applications Microsoft Teams",

+ "description.full": "Anciennement App Studio, le portail des développeurs peut vous aider où que vous soyez dans votre parcours de développement d’applications Microsoft Teams.1. Configurez une nouvelle application ou importez une application existante.2. Configurez les fonctionnalités de votre application et d’autres métadonnées importantes.3. Obtenez des ressources pour vous aider à créer une application de haute qualité.3. Testez votre application directement dans Teams.4. Distribuez votre application dans votre organisation ou dans le Store Teams.5. Analysez l’utilisation, l’engagement et d’autres informations sur votre application. Le portail inclut également des outils pour concevoir des scènes virtuelles personnalisées, des cartes adaptatives et l’intégration à la Plateforme d’identités Microsoft.",

+ "staticTabs[0].name": "Accueil",

+ "staticTabs[1].name": "Applications",

+ "staticTabs[2].name": "Outils",

+ "staticTabs[3].name": "Developer Portal",

+ "bots[0].commandLists[0].commands[0].title": "Rechercher",

+ "bots[0].commandLists[0].commands[0].description": "Rechercher la documentation Teams appropriée"

+Teams Shifts Workforce management (WFM) connectors are production-ready and community-driven integrations, useful for Firstline Workers. They offer a seamless experience and quick process for the digital transformation of Firstline Workers with Teams Shifts.

+Each connector provides detailed guidance for deployment and integration to your organization. You can explore in detail and customize to meet your specific needs.

+This document gives an overview of key benefits of Teams Shifts WFM connectors.

+* **Detailed documentation & support:** All Shifts WFM connectors are accompanied by end-to-end documentation for solution architecture, deployment, and configuration steps. The connector repositories are monitored, so that you can report any issues, challenges or difficulties you encounter.

+For more information on Teams Shifts Workforce management (WFM) connectors, see [Shifts connectors](/microsoft-365/frontline/shifts-connectors).

+The following sequence diagram explains the interaction between the client, which could be the Tasks collaboration control, the [Collaboration API](/rest/api/industry/collaboration-controls/) and the Planner Plan and Task virtual tables.

+To resolve this issue, you must check the error message in the response and if it's set to the message shown above this means the virtual record isn't associated. To create an association for this record, you must call [Associate Collaboration Map - REST API](/rest/api/industry/collaboration-controls/collaboration-custom-ap-is/associate-collaboration-map).

+To create a hero card, thumbnail card, or Adaptive Card from Developer Portal for Teams:

+Use in scenarios where you want the user to pick an item from a list, but the items donΓÇÖt need a lot of explanations.

+Adaptive Cards have a lot of flexibilities. But at minimum, we strongly suggest including the following components in every card.

+Use [`ColumnSet`](https://adaptivecards.io/explorer/ColumnSet.html) to format your card content into a table or grid. There are several options for formatting column width. These guidelines help you understand when to use each one.

+ * **Do**: Use with one column if all your other columns have a static width. For example, you have thumbnail images in one column that are all 50 pixels wide.

+#### Example: Making sure text don't truncate