| Service | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| platform | Designing Apps In Meetings | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/apps-in-teams-meetings/design/designing-apps-in-meetings.md | You can allow users to share and interact with some or all of your app content o Apps shared to the meeting stage occupy the same space as a shared screen. The stage reorients for all meeting participants the same way, too. -> [!NOTE] -> Currently, mobile users can't share app content to the meeting stage. They can see content shared from desktop, though. - ### Use cases The shared meeting stage is all about collaboration and participation. Here are some example scenarios to help you get started. |
| platform | Enable And Configure Your App For Teams Meetings | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/apps-in-teams-meetings/enable-and-configure-your-app-for-teams-meetings.md | To share specific parts of the app to stage, you must invoke the related APIs in > [!NOTE] > > * To share specific parts of the app to stage, use Teams manifest version 1.12 or later.-> * Currently, you can share specific parts of the app to meeting stage only on Teams desktop clients. +> * You can share specific parts of the app to meeting stage only on Teams desktop clients. Mobile users can share specific parts of the app to stage using the [share to stage API](API-references.md#share-app-content-to-stage-api). ### After a meeting |
| platform | Meeting App Extensibility | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/apps-in-teams-meetings/meeting-app-extensibility.md | The following table provides the user types and lists the features that each use | User type | Tabs | Bots | Message extensions | Adaptive Cards | Task modules | In-meeting dialog | Meeting stage | | :-- | :-- | :-- | :-- | :-- | :-- | :-- | :-- | | Anonymous user | Not available | Not available | Not available | Interactions in the meeting chat are allowed. | Not available | Not available | Not available |-| Guest, part of the tenant Azure AD | Interaction is allowed. Create, update, and delete aren't allowed. | Not available | Not available | Interactions in the meeting chat are allowed. | Interactions in the meeting chat from Adaptive Card are allowed. | Available | Can start, view, and interact with app on the meeting stage only on Teams desktop client | -| Federated users, for more information, see [non-standard users](/microsoftteams/non-standard-users). | Interaction is allowed in scheduled meetings. Create, update, and delete aren't allowed. | Interaction is allowed. Acquire, update, and delete aren't allowed. | Not available | Interactions in the meeting chat are allowed. | Interactions in the meeting chat from Adaptive Card are allowed. | Not available | Can start, view, and interact with app on the meeting stage only on Teams desktop client. | +| Guest, part of the tenant Azure AD | Interaction is allowed. Create, update, and delete aren't allowed. | Not available | Not available | Interactions in the meeting chat are allowed. | Interactions in the meeting chat from Adaptive Card are allowed. | Available | Can start, view, and interact with app on the meeting stage only on Teams desktop client and Teams mobile. | +| Federated users, for more information, see [non-standard users](/microsoftteams/non-standard-users). | Interaction is allowed in scheduled meetings. Create, update, and delete aren't allowed. | Interaction is allowed. Acquire, update, and delete aren't allowed. | Not available | Interactions in the meeting chat are allowed. | Interactions in the meeting chat from Adaptive Card are allowed. | Not available | Can start, view, and interact with app on the meeting stage only on Teams desktop client and Teams mobile. | > [!NOTE] > |
| platform | Channel And Group Conversations | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/bots/how-to/conversations/channel-and-group-conversations.md | Bots in a group or channel only receive messages when they're mentioned @botname > [!NOTE] > This feature is currently available in [public developer preview](../../../resources/dev-preview/developer-preview-intro.md) only. >-> Using resource-specific consent (RSC), bots can receive all channel messages in teams that it is installed in without being @mentioned. For more information, see [receive all channel messages with RSC](channel-messages-with-rsc.md). +> Using resource-specific consent (RSC), bots can receive all channel messages in teams that it's installed in without being @mentioned. For more information, see [receive all channel messages with RSC](channel-messages-with-rsc.md). > > Posting a message or Adaptive Card to a private channel is currently not supported. See the following video to learn about channel and group chat conversations with a bot: <br> -> [!VIDEO https://www.microsoft.com/en-us/videoplayer/embed/RE4NzEs] +> [!VIDEO <https://www.microsoft.com/en-us/videoplayer/embed/RE4NzEs>] <br> ## Design guidelines Now, you can create new conversation threads and easily manage different convers ## Create new conversation threads -When your bot is installed in a team, you must create a new conversation thread rather than reply to an existing one. At times it's difficult to differentiate between two conversations. If the conversation is threaded, it is easier to organize and manage different conversations in channels. This is a form of [proactive messaging](~/bots/how-to/conversations/send-proactive-messages.md). +When your bot is installed in a team, you must create a new conversation thread rather than reply to an existing one. At times, it's difficult to differentiate between two conversations. If the conversation is threaded, it's easier to organize and manage different conversations in channels. This is a form of [proactive messaging](~/bots/how-to/conversations/send-proactive-messages.md). Next, you can retrieve mentions using the `entities` object and add mentions to your messages using the `Mention` object. Now you can send an introduction message when your bot is first installed or add When your bot is first added to the group or team, an introduction message must be sent. The message must provide a brief description of the bot's features and how to use them. You must subscribe to the `conversationUpdate` event with the `teamMemberAdded` eventType. The event is sent when any new team member is added. Check if the new member added is the bot. For more information, see [sending a welcome message to a new team member](~/bots/how-to/conversations/send-proactive-messages.md). -Send a personal message to each team member when the bot is added. To do this, get the team roster and send each user a direct message. +You can send a personal message to each member of the team when the bot is added. To do this, [fetch the team roster](../../../resources/bot-v3/bots-context.md#fetch-the-team-roster) and send each user a [direct message](../../../resources/bot-v3/bot-conversations/bots-conv-proactive.md). ++>[!NOTE] +> Ensure that the message sent by the bot is relevant and adds value to the initial message and doesn't spam the users. Don't send a message in the following cases: -* The team is large, for example, larger than 100 members. Your bot can be seen as spam and the person who added it can get complaints. You must clearly communicate your bot's value proposition to everyone who sees the welcome message. +* When the team is large, for example, larger than 100 members. Your bot can be seen as spam and the person who added it can get complaints. You must clearly communicate your bot's value proposition to everyone who sees the welcome message. * Your bot is first mentioned in a group or channel instead of being first added to a team. * A group or channel is renamed. * A team member is added to a group or channel. Follow the [step-by-step guide](../../../sbs-teams-conversation-bot.yml), to cre * [Get Teams context](~/bots/how-to/get-teams-context.md) * [Create private channel on behalf of user](/graph/api/channel-post#example-2-create-private-channel-on-behalf-of-user) * [Connect a bot to Web Chat channel](/azure/bot-service/bot-service-channel-connect-webchat)- |
| platform | Feedback | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/feedback.md | Suggest a feature or vote up existing feature requests. |:-|:| | **Features suggestions** | Post feature suggestions on :::image type="icon" source="assets/icons/Teams-icon.png"::: [Microsoft Teams feedback portal](https://feedbackportal.microsoft.com/feedback/forum/ad198462-1c1c-ec11-b6e7-0022481f8472). | | **General questions** | Send general questions about the Microsoft Teams developer platform to [Microsoft Teams Community Help](mailto:microsoftteamsdev@microsoft.com). We encourage posting questions on the channels mentioned here and using email only if no other mode of communication is applicable. |+| **Feedback interview** | Your feedback is important to us. If you're interested in talking to us about your experience of leveraging our platform documentation, community forum responses, and Teams store publishing process, please feel free to [book a slot](https://aka.ms/bookdevfeedback).| ## See also |