| Service | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| platform | Build Apps For Anonymous User | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/apps-in-teams-meetings/build-apps-for-anonymous-user.md | Last updated 02/07/2023 Anonymous users don't have an Azure Active Directory (Azure AD) identity and aren't federated with a tenant. The anonymous participants are like external users but their identity isn't shown in the meeting. An anonymous user can be a presenter or an attendee but can't be an organizer. You can build bots, messaging extensions, and cards and task modules in your app to engage with anonymous meeting participants. > [!NOTE]-> Apps for anonymous users are supported in Teams desktop and Teams mobile iOS client only. +> Apps for anonymous users are supported in Teams desktop and Teams mobile iOS client only and isn't supported in channel meetings. For anonymous users to interact with the apps in Teams meetings, ensure to: |
| platform | Calls Meetings Bots Overview | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/bots/calls-and-meetings/calls-meetings-bots-overview.md | To use these Graph APIs in a Teams app, you create a bot and specify some additi In addition, the Real-time Media Platform enables bots to interact with Teams calls and meetings using real-time voice, video, and screen sharing. A bot that participates in audio or video calls and online meetings is a regular Microsoft Teams bot with few extra features used to register the bot. -The Teams app manifest with two more settings `supportsCalling` and `supportsVideo`, Graph permissions for your bot's Microsoft App ID, and tenant admin consent enable you to register the bot. In registering a calls and meetings bot for Teams, the Webhook URL is mentioned, which is the webhook endpoint for all incoming calls to your bot. An application-hosted media bot requires the Microsoft.Graph.Communications.Calls.Media .NET library to access the audio and video media streams, and the bot must be deployed on a Windows Server machine or Windows Server guest Operating System (OS) in Azure. Bots on Teams support only a specific set of media formats for audio and video content. +The Teams [app manifest](../../resources/schem#bots) with two more settings `supportsCalling` and `supportsVideo`, Graph permissions for your bot's Microsoft App ID, and tenant admin consent enable you to register the bot. In registering a calls and meetings bot for Teams, the Webhook URL is mentioned, which is the webhook endpoint for all incoming calls to your bot. An application-hosted media bot requires the Microsoft.Graph.Communications.Calls.Media .NET library to access the audio and video media streams, and the bot must be deployed on a Windows Server machine or Windows Server guest Operating System (OS) in Azure. Bots on Teams support only a specific set of media formats for audio and video content. Now, you must understand some core concepts, terminology, and conventions. Real-time media refers to scenarios where media must be processed in real-time, * [Develop calling and online meeting bots on your local PC](debugging-local-testing-calling-meeting-bots.md) * [Enable an event as online meeting in Outlook calendar](/graph/outlook-calendar-online-meetings?tabs=http) * [Requirements and considerations for application-hosted media bots](./requirements-considerations-application-hosted-media-bots.md)-* [App manifest schema for Teams](../../resources/schem) * [Teams recording policy](/microsoftteams/teams-recording-policy) * [Set up an auto attendant](/microsoftteams/create-a-phone-system-auto-attendant)-* [Set up auto answer for Microsoft Teams Rooms on Android and Teams video phone devices](/microsoftteams/set-up-auto-answer-on-teams-android) +* [Set up auto answer for Microsoft Teams Rooms on Android and Teams video phone devices](/microsoftteams/set-up-auto-answer-on-teams-android) |
| platform | Registering Calling Bot | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/bots/calls-and-meetings/registering-calling-bot.md | Last updated 11/23/2022 A bot that participates in audio or video calls and online meetings is a regular Microsoft Teams bot with the following extra features used to register the bot: -* There's a new version of the Teams app manifest with two additional settings, `supportsCalling` and `supportsVideo`. These settings are included in the [Manifest schema for Microsoft Teams](../../resources/schem). +* There's a new version of the Teams app manifest with two additional settings, `supportsCalling` and `supportsVideo`. These settings are included in the [app manifest](../../resources/schem#bots). * [Microsoft Graph permissions](./registering-calling-bot.md#add-graph-permissions) must be configured for your bot's Microsoft App ID. * The Graph calls and online meetings APIs permissions require tenant admin consent. |
| platform | Add Authentication | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/bots/how-to/authentication/add-authentication.md | With the preliminary settings done, let's focus on the creation of the bot to us [!code-json[appsettings](~/../Microsoft-Teams-Samples/samples/bot-teams-authentication/csharp/appsettings.json?range=1-5)] -1. In the Solution Explorer, go to the `TeamsAppManifest` folder, open `manifest.json` and set `id` and `botId` to the **bot App ID** you saved at the time of the bot registration. +1. In the Solution Explorer, go to the `TeamsAppManifest` folder, open `manifest.json` and set `id` and `botId` to the **bot App ID** you saved at the time of the bot registration. For more information, see [app manifest](../../../resources/schem#bots). # [JavaScript](#tab/node-js) |
| platform | Bots Filesv4 | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/bots/how-to/bots-filesv4.md | +> > * This article is based on the v4 Bot Framework SDK. > * Bots don't support sending and receiving files in Governmernt Community Cloud High (GCC-High) and Department of Defense (DOD) environments. The next sections describe how to send file content as direct user interaction, ### Configure the bot to support files -To send and receive files in the bot, set the `supportsFiles` property in the manifest to `true`. This property is described in the [bots](~/resources/schem#bots) section of the Manifest reference. +To send and receive files in the bot, set the `supportsFiles` property in the manifest to `true`. This property is described in the [bots](~/resources/schem#bots) section of the manifest reference. The definition looks like this, `"supportsFiles": true`. If the bot does not enable `supportsFiles`, the features listed in this section do not work. Follow the [step-by-step guide](../../sbs-file-handling-in-bot.yml) to upload fi * [Authentication flow for bots in Microsoft Teams](authentication/auth-flow-bot.md) * [Have a personal (one-on-one) conversation with a Microsoft Teams bot](../../resources/bot-v3/bot-conversations/bots-conv-personal.md) * [Get Teams specific context for your bot](get-teams-context.md)-* [App manifest schema for Teams](../../resources/schem) -* [Protected APIs in Microsoft Teams](/graph/teams-protected-apis) |
| platform | Command Bot In Teams | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/bots/how-to/conversations/command-bot-in-teams.md | You can edit the manifest template file `appPackage\manifest.json` to update the ] ``` +For more information, see [app manifest](../../../resources/schem#botscommandlistscommands). + <br> </details> |
| platform | Bots Notification Only | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/resources/bot-v3/bots-notification-only.md | Last updated 04/02/2023 [!include[v3-to-v4-SDK-pointer](~/includes/v3-to-v4-pointer-bots.md)] -If your bot's sole purpose is to deliver notification to users and isn't conversational, you can enable the `isNotificationOnly` field in your app manifest. This produces the following changes: +If your bot's sole purpose is to deliver notification to users and isn't conversational, you can enable the `isNotificationOnly` field in your [app manifest](../schem#bots). This produces the following changes: * Users can't message your notification-only bot. * Users can't @mention the bot. |
| platform | Tabs Mobile | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/tabs/design/tabs-mobile.md | If you are sideloading your app or publishing to an organization's app catalog, * [Test your app](../../concepts/build-and-test/test-app-overview.md) * [Distribute your Microsoft Teams app](../../concepts/deploy-and-publish/apps-publish-overview.md) * [Create Teams app package](../../concepts/build-and-test/apps-package.md)+* [App manifest schema for Teams](../../resources/schem#statictabs) |
| platform | Build A Dashboard Tab App | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/tabs/how-to/Build-a-dashboard-tab-app.md | export default function App() { ### Modify manifest to add a new dashboard tab app -Open the `appPackage/manifest.json` file and add a new dashboard tab under `staticTabs`. Here's an example: +Open the `appPackage/manifest.json` file and add a new dashboard tab under `staticTabs`. For more information, see [app manifest](../../resources/schem#statictabs). Here's an example: ```json { |
| platform | Create Channel Group Tab | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/tabs/how-to/create-channel-group-tab.md | You've completed the tutorial to build a tab app with Blazor. * [Developer Portal for Teams](../../concepts/build-and-test/teams-developer-portal.md) * [Build tabs with Adaptive Cards](build-adaptive-card-tabs.md) * [Add a SharePoint page as a tab in Teams](https://support.microsoft.com/en-us/office/add-a-sharepoint-page-list-or-document-library-as-a-tab-in-teams-131edef1-455f-4c67-a8ce-efa2ebf25f0b)+* [App manifest schema for Teams](../../resources/schem) |
| platform | Tabs Link Unfurling | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/tabs/tabs-link-unfurling.md | Following is the process to invoke Collaborative Stage View: * [Build tabs for Teams](what-are-tabs.md) * [Add link unfurling](../messaging-extensions/how-to/link-unfurling.md)-* [composeExtensions](../resources/schem#composeextensions) * [Build tabs with Adaptive Cards](how-to/build-adaptive-card-tabs.md) * [Create deep links](../concepts/build-and-test/deep-links.md) * [Cards](../task-modules-and-cards/what-are-cards.md)+* [App manifest schema for Teams](../resources/schem) |
| platform | What Are Tabs | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/tabs/what-are-tabs.md | You can use one of the following methods to create tabs: A custom tab is declared in the app manifest of your app package. For each webpage you want included as a tab in your app, you define a URL and a scope. Additionally, you can add the [Teams JavaScript client library](/javascript/api/overview/msteams-client) to your page, and call `microsoftTeams.initialize()` after your page loads. Teams displays your page and provides access to Teams-specific information, for example, the Teams client is running the dark theme. -Whether you choose to expose your tab within the channel or group, or personal scope, you must present an <iframe\> HTML [content page](~/tabs/how-to/create-tab-pages/content-page.md) in your tab. For personal tabs, the content URL is set directly in your Teams app manifest by the `contentUrl` property in the `staticTabs` array. Your tab's content is the same for all users. +Whether you choose to expose your tab within the channel or group, or personal scope, you must present an <iframe\> HTML [content page](~/tabs/how-to/create-tab-pages/content-page.md) in your tab. For personal tabs, the content URL is set directly in your Teams [app manifest](../resources/schem#statictabs) by the `contentUrl` property in the `staticTabs` array. Your tab's content is the same for all users. > [!Note] > Teams app doesn't recognize sub iframes. Therefore, it'll not load if there is an iframe within the tab app. |
| platform | Add Single Sign On V4 | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/toolkit/toolkit-v4/add-single-sign-on-v4.md | SSO command handler `ProfileSsoCommandHandler` uses an Azure AD token to call Mi }); ``` -1. Register your command in the Teams app manifest. Open `templates\appPackage\manifest.template.json`, and add the following lines under `commands` in `commandLists` of your bot: +1. Register your command in the Teams [app manifest](../../resources/schem#botscommandlists). Open `templates\appPackage\manifest.template.json`, and add the following lines under `commands` in `commandLists` of your bot: ```json { |