| Service | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| platform | Build Apps For Teams Meeting Stage | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/apps-in-teams-meetings/build-apps-for-teams-meeting-stage.md | There are many scenarios where sharing the entire app to the meeting stage isn't To help users in such scenarios, we released APIs within the TeamsJS client library that allow you to programmatically invoke share to stage for specific parts of the app from a button in the meeting side panel. +# [Desktop](#tab/desktop) ++The following image shows the share to stage option in the Teams desktop client: ++ :::image type="content" source="../assets/images/apps-in-meetings/shared-meeting-stage-edit-review-component.png" alt-text="The screenshot shows the share to meeting stage view."::: ++# [Mobile](#tab/mobile) ++The following image shows the share to stage option in the Teams mobile client: ++ :::image type="content" source="../assets/images/meeting-stage/meeting-share-to-stage-mobile.png" alt-text="This screenshot shows meeting stage view of the app you shared to meeting in Teams mobile."::: ++ Use the following APIs to share specific part of the app: The following table provides the response codes: The `getAppContentStageSharingCapabilities` API enables you to fetch the app's capabilities for sharing the app content to meeting stage. Apps need to call the `getAppContentStageSharingCapabilities` API to either enable or disable the custom share to stage button for a meeting participant in the meeting side panel. The share to stage button must be disabled or hidden if a meeting participant doesn't have permission to share the app content to meeting stage. -The app sharing capabilities depends on the tenant user type and participant roles in a meeting. +The app sharing capabilities depend on the tenant user type and participant roles in a meeting. * **User type**: In-tenant, guest, and external user type participants can share the app to stage and also see and interact with the app being shared on stage. Anonymous user can't see, share, or interact with the app that is being shared on the stage. For more information, see [user types in a meeting.](~/apps-in-teams-meetings/teams-apps-in-meetings.md#user-types-in-teams) The following table provides the user types and lists the features that each use | User type | Scheduled meeting or Instant calendar meeting | One-on-one call | Group call | Scheduled channel meeting | | :-- | :-- | :-- | :-- | :-- |-| In-tenant user | Presenter or organizer can start, view, and interact with app on meeting stage.<br><br> Attendee can only view and interact. | Presenter or organizer can start, view, and interact with app on meeting stage. <br><br> Attendee can only view and interact. | Presenter or organizer can start, view, and interact with app on meeting stage.<br><br> Attendee can only view and interact. | Presenter or organizer can start, view, and interact with app on meeting stage.<br><br> Attendee can only view and interact. | -| Guest user | Presenter or organizer can start, view and interact with app on meeting stage.<br><br> Attendee can only view and interact. | Presenter or organizer can start, view, and interact with app on meeting stage.<br><br> Attendee can only view and interact. | Presenter or organizer can start, view, and interact with app on meeting stage.<br><br> Attendee can only view and interact. | Presenter or organizer can start, view, and interact with app on meeting stage.<br><br> Attendee can only view and interact. | -| Federated users or External user | Presenter can start, view, and interact with app on meeting stage.<br><br> Attendee can only view and interact. | Not available | Not available | Presenter can start, view, and interact with app on meeting stage.<br><br> Attendee can only view and interact. | -| Anonymous user | Not available | Not available | Not available | Not available | +| In-tenant | Presenter or organizer can start, view, and interact with app on meeting stage.<br><br> Attendee can only view and interact. | Presenter or organizer can start, view, and interact with app on meeting stage. <br><br> Attendee can only view and interact. | Presenter or organizer can start, view, and interact with app on meeting stage.<br><br> Attendee can only view and interact. | Presenter or organizer can start, view, and interact with app on meeting stage.<br><br> Attendee can only view and interact. | +| Guest | Presenter or organizer can start, view and interact with app on meeting stage.<br><br> Attendee can only view and interact. | Presenter or organizer can start, view, and interact with app on meeting stage.<br><br> Attendee can only view and interact. | Presenter or organizer can start, view, and interact with app on meeting stage.<br><br> Attendee can only view and interact. | Presenter or organizer can start, view, and interact with app on meeting stage.<br><br> Attendee can only view and interact. | +| Federated or External | Presenter can start, view, and interact with app on meeting stage.<br><br> Attendee can only view and interact. | Not available | Not available | Presenter can start, view, and interact with app on meeting stage.<br><br> Attendee can only view and interact. | +| Anonymous | Not available | Not available | Not available | Not available | ## Code sample |
| platform | Build Extensible Conversation For Meeting Chat | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/apps-in-teams-meetings/build-extensible-conversation-for-meeting-chat.md | The following table provides the user types and lists the features that each use | User type | Bots | Message extensions | Adaptive Cards | Task modules | | :-- | :-- | :-- | :-- | :-- |-| In-tenant user | Can view messages, interact with the content, and invoke the bot. | Available | Available | Available | +| In-tenant | Can view messages, interact with the content, and invoke the bot. | Available | Available | Available | | Guest, part of the tenant Azure AD | Can view messages, interact with the content, and invoke the bot. | Not available | Interactions in the meeting chat are allowed. | Interactions in the meeting chat from Adaptive Card are allowed. | | Federated users, for more information, see [non-standard users](/microsoftteams/non-standard-users). |Can view messages, interact with the content, and invoke the bot. | Not available | Interactions in the meeting chat are allowed. | Interactions in the meeting chat from Adaptive Card are allowed. |-| Anonymous user | Can view messages and interact with the bot. | Not available | Interactions in the meeting chat are allowed. | Interactions in the meeting chat from Adaptive Card are allowed. | +| Anonymous | Can view messages and interact with the bot. | Not available | Interactions in the meeting chat are allowed. | Interactions in the meeting chat from Adaptive Card are allowed. | ## See also |
| platform | Build Tabs For Meeting | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/apps-in-teams-meetings/build-tabs-for-meeting.md | The following image shows a tab added to the meeting details page in the Teams m 1. In the app gallery, select the app that you want to add and follow the steps as required. The tab is added to the meeting chat. - :::image type="content" source="../assets/images/apps-in-meetings/meeting-chat-view.png" alt-text="The screenshot shows the meeting chat view in the Teams meeting."::: +# [Meeting chat view desktop](#tab/meeting-chat-view-desktop) ++ The following image shows an app added to the meeting chat in the Teams desktop client: ++ :::image type="content" source="../assets/images/apps-in-meetings/meeting-chat-view.png" alt-text="The screenshot shows the meeting chat view in a meeting chat in Teams desktop."::: ++# [Meeting chat view mobile](#tab/meeting-chat-view-mobile) ++ The following image shows an app added to the meeting chat in the Teams mobile client: ++ :::image type="content" source="../assets/images/apps-in-meetings/meeting-chat-view-mobile.png" alt-text="The screenshot shows the meeting chat view in a meeting chat in Teams mobile."::: ++ ### Meeting side panel view The following image shows a tab added to the meeting details page in the Teams m 1. This results in rendering tab on the stage for every participant in the meeting. - :::image type="content" source="../assets/images/meeting-stage-view.png" alt-text="This screenshot shows meeting stage view of the app you shared to meeting."::: +# [Meeting stage view desktop](#tab/meeting-stage-view-desktop) ++ The following image shows a tab added to the meeting stage in the Teams desktop client: ++ :::image type="content" source="../assets/images/meeting-stage-view.png" alt-text="This screenshot shows meeting stage view of the app you shared to meeting in Teams desktop."::: ++# [Meeting stage view mobile](#tab/meeting-stage-view-mobile) ++ The following image shows a tab added to the meeting stage in the Teams mobile client: ++ :::image type="content" source="../assets/images/meeting-stage/meeting-stage-view-mobile.png" alt-text="This screenshot shows meeting stage view of the app you shared to meeting in Teams mobile."::: ++ ### Apps in channel meeting A public scheduled channel meeting has the same list of apps as its parent team. However, the tab instances in a channel meeting are separate from the tabs in the channel itself. For example, suppose a *Development* channel has a *Polly* tab. If you create a *Standup* meeting in that channel, that meeting would not have a *Polly* tab, until you explicitly [add the tab to the meeting](#meeting-details-view). +# [Channel meeting desktop](#tab/channel-meeting-desktop) ++ The following image shows apps in a channel in the Teams desktop client: ++ :::image type="content" source="../assets/images/apps-in-meetings/apps-in-channel-meeting-desktop.png" alt-text="This screenshot shows a tab added to a channel meeting in Teams desktop."::: ++# [Channel meeting mobile](#tab/channel-meeting-mobile) ++ The following image shows apps in a channel in the Teams mobile client: ++ :::image type="content" source="../assets/images/apps-in-meetings/apps-in-channel-meeting-mobile.png" alt-text="This screenshot shows a tab added to a channel meeting in Teams mobile."::: +++ In public scheduled channel meetings, after a meeting tab is added, you can select the meeting object in the meeting details page to access the tab. :::image type="content" source="~/assets/images/apps-in-meetings/after-a-meeting1.png" alt-text="After a meeting"::: The `context` property determines if the app is available in specific view after | **meetingChatTab** | A tab in the header of a group chat between a set of users for a scheduled meeting. You can specify either **meetingChatTab** or **meetingDetailsTab** to ensure the apps work in mobile. | | **meetingDetailsTab** | A tab in the header of the meeting details view of the calendar. You can specify either **meetingChatTab** or **meetingDetailsTab** to ensure the apps work in mobile. | | **meetingSidePanel** | An in-meeting panel opened through the unified bar (U-bar). |-| **meetingStage** | An app from the `meetingSidePanel` can be shared to the meeting stage. You can't use this app either on mobile or Teams room clients. | +| **meetingStage** | An app from the `meetingSidePanel` can be shared to the meeting stage. You can't use this app in Teams room clients. | #### Configure tab app for a meeting The following table provides the user types and lists the features that each use | User type | Scheduled meeting or Instant calendar meeting | One-on-one call | Group call | Scheduled channel meeting | | :-- | :-- | :-- | :-- | :-- |-| In-tenant user | Interaction allowed for all roles.<br><br> Create, update, or delete is allowed for all except the Attendees. | Interaction and create, update, or delete allowed. <br><br> In-tenant users in call with federated users can't interact and create, update, or delete. | Interaction and create, update, or delete allowed.<br><br> In-tenant users in call with federated users can't interact and create, update, or delete. | Interaction and create, update, or delete allowed for all roles except for attendees. | -| Guest user | Can interact only | Can interact only | Can interact only | Can interact only. | -| Federated user or External user | Can interact only | Not available | Not available | Can interact only | -| Anonymous user | Not available | Not available | Not available | Not available | +| In-tenant | Interaction allowed for all roles.<br><br> Create, update, or delete is allowed for all except the Attendees. | Interaction and create, update, or delete allowed. <br><br> In-tenant users in call with federated users can't interact and create, update, or delete. | Interaction and create, update, or delete allowed.<br><br> In-tenant users in call with federated users can't interact and create, update, or delete. | Interaction and create, update, or delete allowed for all roles except for attendees. | +| Guest | Can interact only | Can interact only | Can interact only | Can interact only. | +| Federated or External | Can interact only | Not available | Not available | Can interact only | +| Anonymous | Not available | Not available | Not available | Not available | ## Code sample The following table provides the user types and lists the features that each use > [!NOTE] >-> * Meeting apps (side panel and meeting stage) are supported in Teams desktop client. +> * Meeting apps (side panel and meeting stage) are supported in Teams desktop and mobile clients. > * Meeting apps (side panel and meeting stage) in Teams web client is supported only when the [developer preview is enabled](/microsoftteams/platform/resources/dev-preview/developer-preview-intro#enable-developer-preview). ## Step-by-step guides |
| platform | In Meeting Notification For Meeting | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/apps-in-teams-meetings/in-meeting-notification-for-meeting.md | The in-meeting notification is used to engage participants and collect informati An external resource URL is used to display in-meeting notification. You can use the `submitTask` method to submit data in a meeting chat. +# [Desktop](#tab/desktop) ++ The following image shows an in-meeting notification in the Teams desktop client: ++ :::image type="content" source="../assets/images/apps-in-meetings/in-meeting-dialogbox.png" alt-text="Screenshot shows an in-meeting notification on Teams desktop."::: ++# [Mobile](#tab/mobile) ++ The following image shows an in-meeting notification in the Teams mobile client: ++ :::image type="content" source="../assets/images/apps-in-meetings/in-meeting-notification-mobile.png" alt-text="Screenshot shows an in-meeting notification in on Teams mobile."::: ++ You can also add the Teams display picture and people card of the user to in-meeting notification based on `onBehalfOf` token with user MRI and display name passed in payload. Following is an example payload: The following table provides the user types and lists the features that each use | User type | Scheduled meeting or Instant calendar meeting | One-on-one call | Group call | Scheduled channel meeting | | :-- | :-- | :-- | :-- | :-- |-| In-tenant user | Available | Available | Available | Available | +| In-tenant | Available | Available | Available | Available | | Guest | Available | Available | Available | Available | | Federated or External | Available | Not available | Not available | Available | | Anonymous | Not available | Not available | Not available | Not available | |
| platform | Teams Apps In Meetings | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/apps-in-teams-meetings/teams-apps-in-meetings.md | Last updated 04/07/2022 Meetings enable collaboration, partnership, informed communication, and shared feedback. The meeting space can deliver a user experience for each stage of the meeting lifecycle. The following illustration gives you an idea of the meeting app extensibility features: - :::image type="content" source="../assets/images/apps-in-meetings/meetingappextensibility.png" alt-text="The screenshot shows you how meeting app extensibility works."::: <!-- Meetings enable collaboration, partnership, informed communication, and shared f :::row-end::: --> - You must be familiar with the following product concepts to create custom meeting experiences with apps in Microsoft Teams. ## Supported meeting types in Teams For more information, see [roles in a Teams meeting](https://support.microsoft.c * [Custom Together Mode scenes](~/apps-in-teams-meetings/teams-together-mode.md) * [Get meeting transcripts using Graph APIs](../graph-api/meeting-transcripts/overview-transcripts.md) * [Instrumenting for Teams app specific analytics](../concepts/design/overview-analytics.md#instrumenting-for-teams-app-specific-analytics)- |
| platform | Teams Live Share Tutorial | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/apps-in-teams-meetings/teams-live-share-tutorial.md | Users invited to the meeting can see your app on stage when they join the meetin ## Deployment -After you're ready to deploy your code, you can use [Teams Toolkit(../toolkit/provision.md#provision-using-teams-toolkit-in-visual-studio) or the [Teams Developer Portal](https://dev.teams.microsoft.com/apps) to provision and upload your app's zip file. +After you're ready to deploy your code, you can use [Teams Toolkit](../toolkit/provision.md#provision-using-teams-toolkit-in-visual-studio) or the [Teams Developer Portal](https://dev.teams.microsoft.com/apps) to provision and upload your app's zip file. > [!NOTE] > You need to add your provisioned appId to the `manifest.json` before uploading or distributing the app. |
| platform | Share In Meeting | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/concepts/build-and-test/share-in-meeting.md | keywords: Share in Meeting Share in meeting allows users to share documents or third-party web apps to the meeting stage. The meeting participants can collaborate and interact with the third-party web apps or edit the documents together. -> [!NOTE] -> Share in meeting is available only in [public developer preview](~/resources/dev-preview/developer-preview-intro.md). - The following image shows the **Share in meeting** button on the web app: :::image type="content" source="../../assets/images/share-in-teams-meeting/web-app.png" alt-text="Screenshot shows share in meeting button on the web app."::: A deep link can be launched either from the Teams web or from the Teams desktop |Deep link|Format|Example| ||||- |To share the app and open Teams calendar, when `UseMeeetNow` is **false**, default.|`https://teams.microsoft.com/l/meeting-share?deeplinkId={deeplinkid}&fqdn={fqdn}}&lm=deeplink%22&appContext={encoded app context}`|`https://teams.microsoft.com/l/meeting-share?deeplinkId={sampleid}&fqdn=teams.microsoft.com&lm=deeplink%22&appContext=%257B%2522appSharingUrl%2522%253A%2522https%253A%252F%252Fteams.microsoft.com%252Fextensibility-apps%252Fmeetingapis%252Fview%2522%252C%2522appId%2522%253A%25229cc80a93-1d41-4bcb-8170-4b9ec9e29fbb%2522%252C%2522useMeetNow%2522%253Afalse%257D`| - |To share the app and initiate instant meeting, when `UseMeeetNow` is **true**.|`https://teams.microsoft.com/l/meeting-share?deeplinkId={deeplinkid}&fqdn={fqdn}}&lm=deeplink%22&appContext={encoded app context}`|`https://teams.microsoft.com/l/meeting-share?deeplinkId={sampleid}&fqdn=teams.microsoft.com&lm=deeplink%22&appContext=%257B%2522appSharingUrl%2522%253A%2522https%253A%252F%252Fteams.microsoft.com%252Fextensibility-apps%252Fmeetingapis%252Fview%2522%252C%2522appId%2522%253A%25229cc80a93-1d41-4bcb-8170-4b9ec9e29fbb%2522%252C%2522useMeetNow%2522%253Atrue%257D`| + |To share the app and open Teams calendar, when `UseMeetNow` is **false**, default.|`https://teams.microsoft.com/l/meeting-share?deeplinkId={deeplinkid}&fqdn={fqdn}}&lm=deeplink%22&appContext={encoded app context}`|`https://teams.microsoft.com/l/meeting-share?deeplinkId={sampleid}&fqdn=teams.microsoft.com&lm=deeplink%22&appContext=%257B%2522appSharingUrl%2522%253A%2522https%253A%252F%252Fteams.microsoft.com%252Fextensibility-apps%252Fmeetingapis%252Fview%2522%252C%2522appId%2522%253A%25229cc80a93-1d41-4bcb-8170-4b9ec9e29fbb%2522%252C%2522useMeetNow%2522%253Afalse%257D`| + |To share the app and initiate instant meeting, when `UseMeetNow` is **true**.|`https://teams.microsoft.com/l/meeting-share?deeplinkId={deeplinkid}&fqdn={fqdn}}&lm=deeplink%22&appContext={encoded app context}`|`https://teams.microsoft.com/l/meeting-share?deeplinkId={sampleid}&fqdn=teams.microsoft.com&lm=deeplink%22&appContext=%257B%2522appSharingUrl%2522%253A%2522https%253A%252F%252Fteams.microsoft.com%252Fextensibility-apps%252Fmeetingapis%252Fview%2522%252C%2522appId%2522%253A%25229cc80a93-1d41-4bcb-8170-4b9ec9e29fbb%2522%252C%2522useMeetNow%2522%253Atrue%257D`| * **Team desktop client**: Use the following format to launch a deep link from the Teams desktop client to share content on stage: |
| platform | In App Purchase Flow | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/concepts/deploy-and-publish/appsource/prepare/in-app-purchase-flow.md | To enable in-app purchase experience, update your Teams app `manifest.json` file To trigger in-app purchase for the app, invoke the `openPurchaseExperience` API from your web app. -Following code snippet is an example of calling the API from the Teams app built using Teams JavaScript client library: --# [TeamsJS v1](#tab/jsonV11) +Following code snippet is an example of calling the API from the Teams app built using Microsoft Teams JavaScript client library: ```json <div> Following code snippet is an example of calling the API from the Teams app built </script> ``` -# [TeamsJS V2](#tab/jsonV2) --```json -<div> -<div class="sectionTitle">openPurchaseExperience</div> -<button onclick="openPurchaseExperience()">openPurchaseExperience</button> -</div> -</body> -<script> - function openPurchaseExperience() { - micorosftTeams.app.initialize(); - var planInfo = { - planId: "<Plan id>", // Plan Id of the published SAAS Offer - term: "<Plan Term>" // Term of the plan. - } - monetization.openPurchaseExperience(planInfo); - } -</script> -``` --- ## End-user in-app purchasing experience The following example shows the users to purchase subscription plans for a fictional Teams app called *Contoso Tasks for Teams*: |
| platform | Tabs Link Unfurling | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/tabs/tabs-link-unfurling.md | When the user enters a URL on the Teams desktop client, the bot is invoked and r The following images display a stage opened from an Adaptive Card: :::image type="content" source="../assets/images/tab-images/open-stage-from-adaptive-card2.png" alt-text="Screenshot shows the open stage from card."lightbox="~/assets/images/tab-images/open-stage-from-adaptive-card2.png"::: Following is the deep link syntax: ### Examples -When a user enters a URL, it's unfurled into an Adaptive card. +When a user enters a URL, it's unfurled into an Adaptive Card. Following are the deep link examples to invoke Stage View: |
| platform | Add Incoming Webhook | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md | You can create and send actionable messages through Incoming Webhook or connecto > [!NOTE] > In Teams, select **Settings** > **Member permissions** > **Allow members to create, update, and remove connectors**, so that any team member can add, modify, or delete a connector. +**Example** ++# [C#](#tab/dotnet) ++[Sample code reference](https://github.com/OfficeDev/Microsoft-Teams-Samples/blob/main/samples/incoming-webhook/csharp/IncomingWebhook/Controllers/CardController.cs#L28) ++```csharp +url = {{Webhook_URL}}; +HttpClient client = new HttpClient(); +client.DefaultRequestHeaders.Accept.Add(new MediaTypeWithQualityHeaderValue("application/json")); +var content = new StringContent({{formatted_Card_Payload}}(Adaptive_Card_Json), System.Text.Encoding.UTF8, "application/json"); +var response = await client.PostAsync({{WebhookUrl}}, content); +``` ++# [JavaScript](#tab/javascript) ++[Sample code reference](https://github.com/OfficeDev/Microsoft-Teams-Samples/blob/main/samples/incoming-webhook/nodejs/api/server/index.js#L16) ++```javascript + axios.post({{WebhookUrl}}, {{formatted_Card_Payload}}) + .then(res => { + console.log(`statusCode: ${res.status}`) + console.log(res) + }) + .catch(error => { + console.error(error) + }) +``` + ## Remove Incoming Webhooks To remove an Incoming Webhook from a Teams channel, follow these steps: |
| platform | Add Outgoing Webhook | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/webhooks-and-connectors/how-to/add-outgoing-webhook.md | The following codes are examples of an Adaptive Card response: # [C#/.NET](#tab/dotnet) +[Sample code reference](https://github.com/OfficeDev/Microsoft-Teams-Samples/blob/main/samples/outgoing-webhook/csharp/Controllers/SampleController.cs#L20) + ```csharp-string content = await this.Request.Content.ReadAsStringAsync(); -Activity incomingActivity = JsonConvert.DeserializeObject<Activity>(content); ++// This method is to read the request body content +string content; +using (var reader = new StreamReader(Request.Body)) + { + content = await reader.ReadToEndAsync(); + } var Card = new AdaptiveCard(new AdaptiveSchemaVersion("1.4")) { return sampleResponseActivity; # [JavaScript/Node.js](#tab/javascript) +[Sample code reference](https://github.com/OfficeDev/Microsoft-Teams-Samples/blob/main/samples/outgoing-webhook/nodejs/app.js#L30) + ```javascript var receivedMsg = JSON.parse(payload); var responseMsg = JSON.stringify({ |
| platform | Whats New | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/whats-new.md | Title: What is new and updated for developers in Teams -description: Learn about new Microsoft Teams developer features and updates to existing features, deprecation notes, and changes. Subscribe to the RSS feed for latest updates. +description: Learn about new Microsoft Teams developer features and updates to existing features, deprecation notes, and changes. Subscribe to the RSS feed for latest updates ms.localizationpriority: high zone_pivot_groups: What-new-features Teams platform features that are available to all app developers. **2022 December** -* ***December 8, 2022***: [Teams developer documentation FAQs](teams-faq.md) --* ***December 07, 2022***: [Notification bot in Teams](bots/how-to/conversations/notification-bot-in-teams.md) --* ***December 07, 2022***: [Command bot in Teams](bots/how-to/conversations/command-bot-in-teams.md) +* ***December 8, 2022***: [Introducing Teams developer documentation FAQs](teams-faq.md) +* ***December 7, 2022***: [Introducing notification bot in Teams](bots/how-to/conversations/notification-bot-in-teams.md) +* ***December 7, 2022***: [Introducing command bot in Teams](bots/how-to/conversations/command-bot-in-teams.md) :::column-end::: :::row-end::: Discover Microsoft Teams platform features that are in developer preview. You ca Developer preview is a public program that provides early access to unreleased Teams platform features. -**2022 December** +**2022 November** ++ ***November 10, 2022***: [Enable bots to receive all chat messages without being @mentioned.](bots/how-to/conversations/channel-messages-with-rsc.md) -***December 05, 2022***: [Introduced share in meeting to share any document or third-party app to the meeting stage](concepts/build-and-test/share-in-meeting.md). + ***November 10, 2022***: [Generate a deep link to share content to stage in meetings.](concepts/build-and-test/share-in-meeting.md) :::column-end::: :::row-end::: |