-description: Identify the meeting apps API references with examples and Code samples, Teams apps meetings user participant role api user context notification signal query.

-|[**Get user context**](#get-user-context-api)| Get contextual information to display relevant content in a Teams tab.| [MSTC SDK](/microsoftteams/platform/tabs/how-to/access-teams-context#get-context-by-using-the-microsoft-teams-javascript-library) |

-The send real-time captions API exposes a POST endpoint for Microsoft Teams communication access real-time translation (CART) captions, human-typed closed captions. Text content sent to this endpoint appears to end users in a Microsoft Teams meeting when they have captions enabled.

-You can get the CART URL for the POST endpoint from the **Meeting options** page in a Microsoft Teams meeting. For more information, see [CART captions in a Microsoft Teams meeting](https://support.microsoft.com/office/use-cart-captions-in-a-microsoft-teams-meeting-human-generated-captions-2dd889e8-32a8-4582-98b8-6c96cf14eb47). You don't need to modify the CART URL to use CART captions.

-| Meetings extensibility | Microsoft Teams meeting extensibility sample for passing tokens. | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/meetings-token-app/csharp) | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/meetings-token-app/nodejs) |

-| Meeting content bubble bot | Microsoft Teams meeting extensibility sample for interacting with content bubble bot in a meeting. | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/meetings-content-bubble/csharp) | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/meetings-content-bubble/nodejs)|

-| Meeting meetingSidePanel | Microsoft Teams meeting extensibility sample for interacting with the side panel in-meeting. | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/meetings-sidepanel/csharp) | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/meetings-sidepanel/nodejs)|

-| Details Tab in Meeting | Microsoft Teams meeting extensibility sample for interacting with Details Tab in-meeting. | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/meetings-details-tab/csharp) | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/meetings-details-tab/nodejs)|

-keywords: UI kit template in-meeting responsive behavior shared meeting stage

-* Editing a document

-* Reviewing a dashboard

-* Watching a video

-* Playing a game

-description: Enable and configure your apps for Teams meetings and different meeting scenarios, update app manifest, configure features, such as, in-meeting dialog, shared meeting stage, meeting sidepanel, and more

-description: Learn about Teams meeting lifecycle and user's meeting experience in desktop and mobile environment, participant and user roles and types, integrate bots and message extension in meeting lifecycle.

-description: overview of apps in Teams meetings based on participant and user role

-keywords: teams apps meetings user participant role api

-$ npm install @microsoft/live-share --save

-$ yarn add @microsoft/live-share

-1. Initialize the Teams Client SDK

-2. Initialize the [TeamsFluidClient](/javascript/api/@microsoft/live-share/teamsfluidclient)

-3. Define the data structures you want to synchronize. For example, `SharedMap`

-4. Join the container

-> [!Note]

-> While you can use the `EphemeralMediaSession` object to synchronize media directly, using the `MediaPlayerSynchronizer` unless you want more fine tuned control of the synchronization logic. Depending on the player you use in your app, you might want to create a delegate shim to make your web player's interface match the HTML media interface.

-* Zero-hassle session management and security

-* Stateful and stateless distributed data structures

-* Media extensions to easily synchronize video and audio

-* Respect meeting privileges using role verification

-* Free and fully managed service with low latency

-* Intelligent audio ducking

-Not all of your apps views will need to be collaborative. The `stage` view _always_ needs collaborative features, the `content` view _may_ need collaborative features, and the `config` view should _never_ need collaborative features. For the views that do need collaborative features you'll need to join a Fluid container associated with the current meeting.

-The values returned from `diceMap` are only a snapshot in time. To keep the data up to date as it changes an event handler must be set on the `diceMap` to call `updateDice` each time that the `valueChanged` event is sent. To get a list of events fired and the values passed to those events, see [SharedMap](https://fluidframework.com/docs/data-structures/map/).

-```js

-The side panel view, loaded through the tab `contentUrl` with the `sidePanel` frame context, is displayed to the user in a side panel when they open your app within a meeting. The goal of this view is to let a user select content for the app prior to sharing the app to the meeting stage. For the Live Share SDK apps, the side panel view can also be used as a companion experience for the app. Calling [joinContainer()](/javascript/api/@microsoft/live-share/teamsfluidclient#@microsoft-live-share-teamsfluidclient-joincontainer) from the side panel view connects to the same Fluid container the stage view is connected to. This container can then be used to communicate with the stage view. Ensure that you're communicating with everyone's stage view _and_ side panel view.

-A scene only app is still an app in Microsoft Teams. The Scene studio handles the app package creation in the background. Multiple scenes in a single app package appear as a flat list to the users.

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

-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 Microsoft Teams Developer Portal. The interface and functionalities are all the same in App Studio Scene Designer.

-1. Select **Save** and select **View in Teams** to quickly test your scene in Microsoft Teams.

- * Selecting **View in Teams** automatically creates a Microsoft Teams app that can be viewed in the **Apps** page in the Teams Developer Portal.

- > On selecting **Preview** in the Scene studio, the scene is installed as an app in Microsoft Teams. This is the model for a developer to test and try out scenes from the Scene studio. After a scene is shipped as an app, users see these scenes in the scene gallery.

-description: Understand the bot activity handlers in Teams.

-keywords: activity handler framework bot card consent channel event

-To organize the conversational logic for your bot, an activity handler is used. Activities are handled in two ways using Teams activity handlers and bot logic. The Teams activity handler adds support for Microsoft Teams-specific events and interactions. The bot object contains the conversational reasoning or logic for a turn and exposes a turn handler, which is the method that can accept incoming activities from the bot adapter.

-description: Overview of the tools and SDKs for building Microsoft Teams bots.

-description: Learn about detailed technical information on handling notifications from incoming calls, redirecting and authenticating calls using code samples

-keywords: calling calls notifications callback region affinity

-description: Learn how your Microsoft Teams apps can interact with users using voice and video using Microsoft Graph APIs for calls and online meetings and learn about real-time media streams

-keywords: calling calls audio video IVR voice online meetings real-time media streams bot

-The Teams app manifest with two additional 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.

-* A user can initiate a peer-to-peer call with your bot or invite your bot into an existing multiparty call. The multiparty call isn't enabled yet in the Teams user interface.

- > User initiated calls to a bot are currently not supported on Microsoft Teams mobile platform.

-* Graph permissions aren't necessary for a user to initiate a peer-to-peer call with your bot. Additional permissions are needed for your bot to participate in a multiparty call, or for your bot to initiate a peer-to-peer call with a user.

-* A call can start as peer-to-peer and eventually become a multiparty call. Your bot can initiate multiparty calls by inviting others, provided your bot has the proper permissions. If your bot doesn't have permissions to participate in group calls and if a participant adds another participant to the call, your bot is dropped from the call.

-When a bot is participating in a call or online meeting, it must deal with audio and video streams. When users talk on a call, show themselves on a webcam, or present their screens in a meeting, to a bot it's shown as audio and video streams. If a bot wants to say something as simple as, **press 0 to reach the operator** in an interactive voice response (IVR) scenario, it requires playing a .WAV file. Collectively, this is referred to as media or real-time media.

-Real-time media refers to scenarios where media must be processed in real-time, as opposed to playback of previously recorded audio or video. Dealing with media streams, particularly real-time media streams, is complex. Microsoft has created the Real-time Media Platform to handle these scenarios and to offload as much of the traditional heavy lifting of real-time media processing as possible. When the bot answers an incoming call or joins a new or existing call, it needs to tell the Real-time Media Platform how media is handled. If you're building an IVR application, you can offload the expensive audio processing to Microsoft. Alternately, if your bot requires direct access to media streams, that scenario is also supported. There are two types of media processing:

-* **Service-hosted media**: Bots focus on managing application workflow, such as routing calls and offload audio processing to the Microsoft Real-time Media Platform. With service-hosted media, you have several options to implement and host your bot. A service-hosted media bot can be implemented as a stateless service as it doesn't process media locally. Service-hosted media bots can use the following APIs:

-description: Learn how you can also use ngrok to develop calls and online meeting bots on your local PC.

-keywords: local development ngrok tunnel

-description: Understand key concepts in building bot that can conduct real-time audio and video calls and online meetings. Learn about media sessions, frame rate, audio/video format, and reference to developer resources

-keywords: audio stream video stream audio/video calling meeting real-time media application-hosted media service-hosted media

-description: Learn how to register a new audio/video calling bot for Microsoft Teams, create a new bot or add calling capability, and add graph permissions.

-keywords: calling bot audio/video audio video media

-description: Understand important requirements and considerations, and scalability and performance considerations related to creating application-hosted media bots for Microsoft Teams using code example and samples.

-keywords: application-hosted media Windows server Azure VM

-Real-time media calls stay on the computer where they were created. A real-time media call is pinned to the virtual machine (VM) instance that accepted or started the call. Media from a Microsoft Teams call or meeting flows to that VM instance, and media the bot sends back to Microsoft Teams must also originate from that VM. If there are any real-time media calls in progress when the VM is stopped, those calls are abruptly terminated. If the bot has prior knowledge of the pending VM shutdown, it can end the calls.

-description: Learn how to design a Teams bot and get the Microsoft Teams UI Kit.

-> * By adding your chatbot to Microsoft Teams, some of the data, such as bot content and user chat content, is shared with Microsoft Teams. It means that your data flows outside of your [organizationΓÇÖs compliance and geographic or regional boundaries](/power-virtual-agents/data-location). <br/>

-description: How to add OAuth authentication to a bot in Microsoft Teams using Azure Active Directory. Learn how to create, deploy, and integrate authentication-enabled bots.

-keywords: resource group bot registration Azure emulator bot manifest deploy

-Note-there are two options for Service Providers here-Microsoft Azure Active Directory (Azure AD) V1 and Microsoft Azure Active Directory (Azure AD) V2. The differences between the two providers are summarized [here](/azure/active-directory/azuread-dev/azure-ad-endpoint-comparison), but in general, V2 provides more flexibility with respect to changing bot permissions. Graph API permissions are listed in the scopes field, and as new ones are added, bots will allow users to consent to the new permissions on the next sign in. For V1, the bot consent must be deleted by the user for new permissions to be prompted in the OAuth dialog.

- - If you selected *Accounts in any organizational directory (Any Microsoft Azure Active Directory (Azure AD) - Multi tenant and personal Microsoft accounts, for example, Skype, Xbox, Outlook)* enter the word **common** instead of a tenant ID. Otherwise, the Microsoft Azure Active Directory (Azure AD) app will verify through the tenant whose ID was selected and exclude personal Microsoft accounts.

- 1. **Service Provider**. Select **Microsoft Azure Active Directory v2**. Once you select this, the Microsoft Azure Active Directory (Azure AD)-specific fields will be displayed.

- - If you selected either *Accounts in this organizational directory only (Microsoft only - Single tenant)* or *Accounts in any organizational directory(Microsoft Azure Active directory - Multi tenant)*, enter the **tenant ID** you recorded earlier for the Microsoft Azure Active Directory (Azure AD) app. This will be the tenant associated with the users who can be authenticated.

- - If you selected *Accounts in any organizational directory (Any Microsoft Azure Active Directory (Azure AD) - Multi tenant and personal Microsoft accounts, for example, Skype, Xbox, Outlook)* enter the word **common** instead of a tenant ID. Otherwise, the Microsoft Azure Active Directory (Azure AD) app will verify through the tenant whose ID was selected and exclude personal Microsoft accounts.

- > Only one messaging endpoint is allowed for a bot

-Microsoft Teams is an entirely cloud-based product, it requires all services it accesses to be available from the cloud using HTTPS endpoints. Therefore, to enable the bot (our sample) to work in Teams, you need to either publish the code to the cloud of your choice, or make a locally running instance externally accessible via a **tunneling** tool. We recommend [ngrok](https://ngrok.com/download), which creates an externally addressable URL for a port you open locally on your machine.

-To set up ngrok in preparation for running your Microsoft Teams app locally, follow these steps:

-1. Append `/api/messages` to obtain `https://dea822bf.ngrok.io/api/messages`. This is the **messages endpoint** for the bot running locally on your machine and reachable over the web in a chat in Microsoft Teams.

-This manifest contains information needed by Microsoft Teams to connect with the bot:

-| Bot authentication | This sample shows how to get started with authentication in a bot for Microsoft Teams. | [View](https://github.com/microsoft/BotBuilder-Samples/tree/master/samples/csharp_dotnetcore/46.teams-auth) | [View](https://github.com/microsoft/BotBuilder-Samples/tree/master/samples/javascript_nodejs/46.teams-auth) | [View](https://github.com/microsoft/BotBuilder-Samples/tree/main/samples/python/46.teams-auth) |

-description: Describes how to get a user token. Currently, a bot developer can use a sign-in card or the Azure bot service with the OAuth card support.

-keywords: token, user token, SSO support for bots, permission, Microsoft Graph, Azure AD

-description: Describes Microsoft Teams authentication flow in bots with Code sample.

-keywords: teams authentication flow bots

-description: Learn how to send and receive files through the bot using Graph APIs for personal, channel and groupchat scopes. Use Teams bot APIs using code samples based on the v4 Bot Framework SDK.

-keywords: teams bots files send receive

-description: How to send, receive, and handle messages for a bot in a channel or group chat. Learn about design guidelines, creating conversation threads, using @mentions using Code samples

-description: Receive all channel messages with RSC permissions

-description: Introduction to bot conversations in a channel, personal chat, and a group chat environment.

-keyword: conversations basics messages groupchap group channel

-description: Describes ways to have a conversation with a Microsoft Teams bot. Learn about Teams channel data, notification to your message, picture messages, adaptive cards using Code samples.

-keyword: receive message send message picture message channel data adaptive cards

-| Rich text | Γ£ö | Γ£ö | Your bot can send rich text, pictures, and cards. Users can send rich text and pictures to your bot. |

-| Pictures | ✔ | ✔ | Maximum 1024×1024 MB and 1 MB in PNG, JPEG, or GIF format. Animated GIF isn't supported. |

-| Cards | Γ£û | Γ£ö | See the [Teams card reference](~/task-modules-and-cards/cards/cards-reference.md) for supported cards. |

-| Emojis | Γ£ö | Γ£ö | Teams currently supports emojis through UTF-16, such as U+1F600 for grinning face. |

-

-

-description: Describes how to send tenant ID and conversation ID to the request headers of the bot.

-description: Learn how to send proactive messages with your Microsoft Teams bot, proactively install your app using Microsoft Graph and check the code samples based on Bot Framework SDK v4.

-Keywords: send a message get user ID channel ID conversation ID

-description: Learn how to create a command menu for your Microsoft Teams bot with Code samples.

-keywords: command menu compose message conversation @mention

- > If you have been using App Studio, we recommend that you'd try the Developer Portal to configure, distribute, and manage your Teams apps. App Studio will be deprecated by June 30, 2022

-2. In **App Studio**, select the **Manifest editor** tab. If you do not have an existing app package, you can create or import an existing app. For more information, see [update C# app package in App Studio](../../get-started/deploy-csharp-app-studio.md)

-description: Learn about testing and debugging your bot locally with an IDE within Teams environment via sideloading, outside Teams using Bot emulator, and by talking directly to your bot.

-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 Microsoft Teams app capabilities like tabs or message extensions. Initiate a conversation in one of the following ways:

-* On the [Bot Dashboard](https://dev.botframework.com/bots) page for your bot, under **Channels**, select **Add to Microsoft Teams**. Microsoft Teams launches a personal chat with your bot.

-* Directly reference your bot's app ID from within Microsoft Teams:

- Alternatively, you can paste your bot's app ID in the search box in the top left in Microsoft Teams. In the search results page, go to the **People** tab to see your bot and to start chatting with it.

-> For Microsoft Teams to refer to your bot's app ID, enable [sideloading of apps](/microsoftteams/platform/concepts/build-and-test/prepare-your-o365-tenant#enable-custom-teams-apps-and-turn-on-custom-app-uploading).

-description: Add rich formatting to your bot messages, such as strikethrough, ordered and unordered list, hyperlink, image link, and more.

-After you format text content, ensure that your formatting works across all platforms supported by Microsoft Teams.

-| Bold | Γ£ö | Γ£û |

-| Italic | Γ£ö | Γ£ö |

-| Header (levels 1&ndash;3) | Γ£û | Γ£ö |

-| Strikethrough | Γ£û | Γ£ö |

-| Horizontal rule | Γ£û | Γ£û |

-| Unordered list | Γ£û | Γ£ö |

-| Ordered list | Γ£û | Γ£ö |

-| Preformatted text | Γ£ö | Γ£ö |

-| Blockquote | Γ£ö | Γ£ö |

-| Hyperlink | Γ£ö | Γ£ö |

-| Image link | Γ£ö | Γ£û |

-| Bold | Γ£ö | Γ£ö | Γ£ö |

-| Italic | Γ£ö | Γ£ö | Γ£ö |

-| Header (levels 1&ndash;3) | Γ£û | Γ£û | Γ£û |

-| Strikethrough | Γ£ö | Γ£ö | Γ£û |

-| Horizontal rule | Γ£û | Γ£û | Γ£û |

-| Unordered list | Γ£ö | Γ£û | Γ£û |

-| Ordered list | Γ£ö | Γ£û | Γ£û |

-| Preformatted text | Γ£ö | Γ£ö | Γ£ö |

-| Blockquote | Γ£ö | Γ£ö | Γ£ö |

-| Hyperlink | Γ£ö | Γ£ö | Γ£ö |

-| Image link | Γ£ö | Γ£ö | Γ£ö |

-description: How to get Microsoft Team's specific context for your bot, including the conversation roster, single member or team's details, channel list, code samples.

-keywords: bot context roster user profile channel list

-After you get details of a single member, you can get details of the team. Currently, to retrieve information for a team, use the Microsoft Teams bot APIs `TeamsInfo.GetMemberDetailsAsync` for C# or `TeamsInfo.getTeamDetails` for TypeScript.

-After you get details of the team, you can get the list of channels in a team. Currently, to retrieve information for a list of channels in a team, use the Microsoft Teams bot APIs `TeamsInfo.GetTeamChannelsAsync` for C# or `TeamsInfo.getTeamChannels` for TypeScript APIs.

-description: Learn about handling rate limit for bots with Per bot per thread limit and per limit for all bots using Code examples. Additionally, learn rate limiting best practices in Microsoft Teams.

-keywords: teams bots rate limiting

-description: An overview of bots in Microsoft Teams.

->

-Rate limiting is used to optimize bots used for your Teams application. To protect Microsoft Teams and its users, the bot APIs provide a rate limit for incoming requests. See [optimize your bot with rate limiting in Teams](~/bots/how-to/rate-limit.md).

-With Microsoft Graph APIs for calls and online meetings, Microsoft Teams apps can now interact with users using voice and video. See [calls and meetings bots](~/bots/calls-and-meetings/calls-meetings-bots-overview.md).

-keywords: entry points extensibility use cases device capability

-* Identify and map use cases to Teams features

-* Use planning checklist

-* Plan beyond app deployment

-****Compliance UI***: By enabling third-party communications, customers accept that such communication is being processed through the third party and not Microsoft. The customer is solely responsible for mitigating risks associated with connecting with third party bots in their services. Microsoft does not endorse and makes no warranties, express, or implied concerning the security of third parties the customer allows to connect with their service. Enabling bots will extend your system boundary beyond this tenant based on the bot you choose to leverage. It is your responsibility to ensure that this meets your compliance requirements including FedRAMP, DFARS, ITAR, etc. It is your responsibility to evaluate the risk and compliance of any endpoint and URL that you connect to.

-description: Describes authentication in Teams and how to use it in the apps

-keywords: teams authentication OAuth SSO Microsoft Azure Active Directory (Azure AD)

-description: Describes how to configure identity providers with a focus on Microsoft Azure Active Directory (Azure AD)

-keywords: teams authentication Azure AD oauth identity provider

-description: Get started building great apps in Microsoft Teams using App Studio

-keywords: getting started app studio teams

-App Studio is a Teams app which can be found in the Teams store. Follow this link for direct download [App Studio](https://aka.ms/InstallTeamsAppStudio). You can also find the app in the app store.

-Once you are in App Studio, click on the **Manifest editor** tab where you can either import an existing app or create a new app.

-As mentioned earlier, the most significant part of a Microsoft Teams app package is its manifest.json file. This file, which must conform to the [Teams App schema](~/resources/schem), contains metadata which allows Teams to correctly present your app to users.

-The Manifest Editor tab in App Studio simplifies creating the manifest, allowing you to describe the app, upload your icons, add app capabilities, and produce a .zip file which can easily be uploaded into Teams for testing or distributed for others to use. Note that App Studio does not produce functional code for your app, or host your app. Your app must already be hosted and running at the URL listed in the manifest for the app upload process to result in a working app.

-The details section of the Manifest Editor defines the high-level description of the app you are making. This includes things such as the appΓÇÖs name, description, and visual branding. You can automatically generate a GUID for your app and provide URLs for your privacy statement and terms of use.

-* **Team Tabs.** A team tab becomes part of a channel and provides quick access to team information and resources. For example, the Planner tab for a channel contains a single plan; the Power BI tab maps to a specific report. Users can drill down to the relevant context, but they should not be able to navigate outside the tab. The Power BI tab, for instance, doesn't enable navigation to other Power BI reports, but it does enable the *Go to website* button that launches the report in the main Power BI website.

-* **Personal Tabs.** This section lets you define a set of tabs that are presented by default in the personal app experience (experience a user has with your app outside the context of a team or channel). In this section, provide the tab name, a unique identifier, the URL that points to the UI to be displayed in Teams, and optionally, the URL to use if a user opts to view the tab in a browser. With Teams tabs, provide any additional domains from which the tab expects to load from or link to.

-This section allows you to add a [conversational bot](~/bots/what-are-bots.md) to your app. If you already have a bot registered with Bot Framework, you can add that bot by clicking *Set Up* and supplying the bot's name, Bot Framework ID, and defining the scopes in which the bot will work.

-If you have not yet registered a bot with the Bot Framework, click **Register** to create a new one. Once youΓÇÖre done registering your bot, come back to this section of the Manifest Editor to enter its name and Bot Framework ID.

-After you have supplied your bot's information, you can now optionally define a list of commands that your bot can suggest to users. Add the name of the command, a description of the command which indicates its syntax and arguments, and the scope(s) to which this command should apply.

-This section allows you to add a connector to your app. If you already have registered an Office 365 connector, choose **Set up** and enter the name and ID of the connector. If you want a new connector click **Register** to be taken to the Connector Developer Dashboard in your browser.

-[Message extensions](~/messaging-extensions/what-are-messaging-extensions.md) are a powerful way for users to engage with your app within Microsoft Teams. Users can query for information from your service and post that information in the form of cards, right into the channel or chat conversation.

-Message extensions are powered by Bot Framework bots, so they require a configured bot to operate. If you have the name and Bot Framework ID of the bot you would like to power the message extension, enter it. Otherwise, click **Register** to create one and enter the information afterward. Select whether the configuration of a message extension can be updated by the user.

-Once you have the underlying bot configured, define the commands and parameters which the message extension can accept.

-Once you have finished defining your application, the Test and Distribute section allows you export your appΓÇÖs definition as a zip file which then can be shared and uploaded into the Teams client for testing. Clicking export downloads the zip file as *appname.zip* in your default download directory.

-On your project home page, you can upload your app to a team, submit your app to your company custom app store for users in your organization, or submit your app to App Source for all Teams users. Your IT admin will review these submissions. You can return to the *Publish* page to check on your submission status and learn if your app was approved or rejected by your IT admin. This is also where you'll come to submit updates to your app or cancel any currently active submissions.

-A card is a container for short or related pieces of information. Microsoft Teams supports cards, which can have multiple properties and attachments. Cards are a key way that bots and connectors relay actionable information to users.

-Creating an app that follows the Teams best practices is a great way to give your app a look and feel that fits seamlessly with the Teams client experience. The UI controls that you use are critical to achieving that end. To make it easier to create a consistent UI, App Studio provides several categories of UI controls which follow Teams design principles.

-| App Localization | Microsoft Teams app localization using bot and tab. | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/app-localization/csharp) |[View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/app-localization/nodejs) |

-description: Describes options for testing and debugging Microsoft Teams apps in local and cloud-hosted environment.

-keywords: teams run debug apps local cloud-hosted host

-> Running the bot locally does not give you access to Teams app functionality or Teams-specific bot functions like roster calls and other channel-specific functionality. In addition, some capabilities are permitted by the Bot Framework in the Bot Emulator that might not function when running in Microsoft Teams.

-Microsoft Teams is an entirely cloud-based product, it requires all services it accesses to be available publicly using HTTPS endpoints. Therefore, to enable your app to work within Teams, you need to either publish the code to the cloud of your choice or make our local running instance externally accessible. We can do the latter with tunneling software.

-To set up ngrok in preparation to execute your Microsoft Teams app locally, follow these steps:

-> * If you have been using App Studio, we recommend that you'd try the Developer Portal to configure, distribute, and manage your Teams apps. App Studio will be deprecated by June 30, 2022

-You can use any externally addressable service to host your development and production code and their HTTPS endpoints. There's no expectation that your capabilities reside on the same service. We require all domains to be accessed from your Microsoft Teams apps listed in the [`validDomains`](~/resources/schem#validdomains) object in the `manifest.json` file.

-To load and run your experience within Microsoft Teams, you need to create a package and upload it into Teams. For more information, see:

-When navigating to a deep link, Microsoft Teams simply navigates to the tab and provides a mechanism through the Microsoft Teams JavaScript library to retrieve the sub-page ID if it exists.

-> If the bot sends a message containing a `TextBlock` with a deep link, then a new browser tab is opened when the user selects the link. This happens in Chrome and in the Microsoft Teams desktop app, both running on Linux.

-|Deep Link consuming Subentity ID |Microsoft Teams sample app for demonstrating deep link from bot chat to tab consuming Subentity ID.|[View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/tab-deeplink/csharp)|[View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/tab-deeplink/nodejs)|

-description: How to get started with Teams in Microsoft 365

-keywords: Configure Microsoft 365 tenant Teams uploading

- After completing this, the Microsoft Teams icon gets added to your website. The following image shows the Share to Teams icon:

-description: Learn how to configure, distribute, and manage your apps using the Developer Portal for Microsoft Teams.

-keywords: getting started developer portal teams

-* Register a brand new app

-* Import an existing app package

-description: Describes the process to test and debug your Teams custom app in Microsoft 365

-keywords: Configure Microsoft 365 tenant Teams uploading test app

-description: Set up your Office 365 developer program subscription for successful testing of Microsoft Teams Apps using code snippets

-keywords: testing apps developer program teams

-To distribute your Microsoft Teams app, you must have a valid app package. An app package is a zip file that contains an **app manifest** and **app icons**.

-description: Understand what you can and can't customize in Microsoft Teams when designing your app.

-keywords: wireframe channel chat meeting message extensions mobile desktop

-* Contextual actions on app content

-* Contextual filter and find

-* Navigation and breadcrumbs

-> [Get the Microsoft Teams UI Kit (Figma)](https://www.figma.com/community/file/916836509871353159)

-keywords: layout grid avatars icons segoe ui typography

-description: Learn how to design Microsoft Teams apps. Resources include the Microsoft Teams UI Kit, best practices, examples, and more.

-description: Get a general idea of how and when you might use Microsoft tools and resources to design an effective Microsoft Teams app.

-description: Design your app faster with standardized UI components, layouts, and patterns commonly seen across Microsoft Teams.

-* Project management. Assigning tasks and tracking status

-* Brainstorming. Adding ideas in different categories

-* Sorting exercises. Organizing any kind of information into buckets

-description: Understand how Teams admins can customize your app for their org.

-keywords: accent color brand hide app approval

-keywords: ui kit personal app webview navigation bot tab iframe dashboard form template

-description: Guide to plan for creating an app on Teams mobile

-* Dashboards and summaries

-* Data visuals, maps, and infographics

-* Charts, graphs, and tables

-* Search content

-* Filter data

-* Create bookmarks

-* Modify title and description

-* Insert data items to create visualizations

-* Share visualizations in a channel or group chat

-* Create tasks or items with the mandatory fields to reduce cognitive load of the users

-* Change the board type or view

-* Review tasks by expanding the view

-* Use task modules to see detailed view

-* Move the tasks into different categories

-* Share relevant tasks in chats and channels through emails and activity feed

-* Add new projects and boards

-* Add and modify different categories, such as **Proposed**, **Active**, and **Closed**

-* Configure the tasks for comments, attachments, and other complex features

-* Comments or feedback

-* Zoom in or out

-* Current stage or progress of a pending document

-* Create new board for collaboration or new documents for signing

-* Share boards internally and also with guests

-* Configure admin permissions

-* Adding text, shapes, and quick notes

-* Navigate around content

-* Add layers and filters

-* Delete, undo, and redo operations

-description: learn how plan to monetize your Microsoft Teams app.

-description: In this article learn about Microsoft Teams app capabilities, plan your Teams app, understand your app user and their needs, understand the user problems that your Teams app would solve, plan user authentication and their onboarding experience.

-> You must make users aware of where to go to enable these **App permissions** in Microsoft Teams.

-Follow the [step-by-step guide](../../sbs-tab-device-permissions.yml) to grant tab device permission in Microsoft Teams.

-Device permissions are different in the browser. Previously, browser handled how to grant access permissions and now these permissions are handled in Microsoft Teams. For more information, see [browser device permissions](browser-device-permissions.md).

-|Device permissions | Describes how to demonstrates Microsoft Teams tab sample app for device permissions. |[View](<https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/tab-device-permissions/nodejs>)|

-description: How to update your app manifest in order to request access to native features that usually require user consent, such as scan qr, barcode, image, audio, video capabilities

-> * To integrate location capabilities within your Microsoft Teams web client, desktop, and mobile, see [Integrate location capabilities](location-capability.md).

-> * Currently, Microsoft Teams support for QR barcode scanner capability is only available for mobile clients.

-* To prompt the user to access their location you must call `getCurrentPosition()`:

-* To prompt the user to access their camera on desktop or web you must call `getUserMedia()`:

-* Notifications prompts the user when you call `requestPermission()`:

- * MICROSOFT_APP_ID is ID

- * MICROSOFT_APP_PASSWORD is password

-description: With this learning path, get started for Microsoft Teams developer documentation which introduces you to common tools, fundamental concepts, and advanced features.

-description: Describes resource-specific consent in Teams and how to make advantage of it.

-keywords: teams authorization OAuth SSO Azure AD rsc Graph

-description: Learn how to test resource-specific consent for a chat in Teams using Postman with a sample JSON file.

-keywords: teams authorization OAuth SSO Azure AD rsc Postman Graph

-description: Learn How to test resource-specific consent for a team in Teams using Postman with a sample JSON file.

-keywords: teams authorization OAuth SSO Azure AD rsc Postman Graph

-> * Update your app manifest

-> * Add an Outlook channel for your bot

-> * Sideload your updated app in Teams

-* A Microsoft 365 Developer Program sandbox tenant

-* Enrollment in *Office 365 Targeted Releases* for your sandbox tenant

-* A test environment with Office apps installed from the Microsoft 365 Apps *Beta Channel*

-* (Optional) Microsoft Visual Studio Code with the Teams Toolkit extension

-> * Update your app manifest

-> * Update your TeamsJS SDK references

-> * Amend your Content Security Policy headers

-> * Update your Microsoft Azure Active Directory (Azure AD) App Registration for Single Sign On (SSO)

-> * Sideload your updated app in Teams

-description: Learn how to handle the initial invoke action and respond with a task module from an action messaging extension command using code examples and samples.

-description: An overview of messaging extension action commands with app manifest example

-description: Describes how to respond to the task module submit action from a messaging extension action command with Proactive message, another task module, Adaptive card bot, and more using Code samples.

-|Card response | Γ£ö | Γ£ö | Γ£ö |

-|Another task module | Γ£ö | Γ£ö | Γ£ö |

-|Bot with Adaptive Card | Γ£ö | x | Γ£ö |

-| No response | Γ£ö | Γ£ö | Γ£ö |

-description: Learn how to add authentication to a messaging extension using code examples and sample

-description: Learn how to enable SSO support for your messaging extensions with Code samples.

-description: Learn how to add link unfurling with messaging extension in a Microsoft Teams app with app manifest or manually using code examples and samples.

-description: Learn about message extension search commands for Microsoft Teams apps, to create a search command through app manifest and manually using code examples and sample.

-description: Learn how to respond to the search command from a message extension in a Microsoft Teams app using code examples and samples

-description: An overview of messaging extensions on the Microsoft Teams platform

-description: Describes the Azure Bot Service OAuthCard and how it is used for authentication

-Without the Azure Bot ServiceΓÇÖs OAuthCard it is complicated to implement authentication in a bot. It is 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 is 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 are 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 not use the OAuthCard, you can still refer to those topics.

-* The card will not work with [guest access](/MicrosoftTeams/guest-access)

-* It will not work with [Microsoft Teams free](https://products.office.com/microsoft-teams/free)

-* It can only be used for bot authentication

-* It only works for bots registered in the [Azure Bot Service](https://azure.microsoft.com/services/bot-service/)

-> 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 will not open the authentication window. Use the [App Studio](~/concepts/build-and-test/app-studio-overview.md) to generate your manifest.

-description: Describes the end-to-end scenario of having a conversation with a bot in a channel in Microsoft Teams

-keywords: teams scenarios channels conversation bot

-Chat in channels and group chats differ from personal chat in that the user needs to @mention the bot. If a bot is used in multiple scopes such as personal, groupchat, or channel, you need to detect what scope the bot messages came from, and process them accordingly.

-Bots added to a team become another team member and can be @mentioned as part of the conversation. In fact, bots only receive messages when they are @mentioned, so other conversations on the channel are not sent to the bot.

-Your bot, just as it is, may be entirely relevant in all scopes without requiring additional work. In Microsoft Teams there is 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/app-studio-overview.md).

-For more information on bots creating messages in channels see [Proactive messaging for bots](~/resources/bot-v3/bot-conversations/bots-conv-proactive.md), and specifically [Creating a channel conversation](~/resources/bot-v3/bot-conversations/bots-conv-proactive.md#creating-a-channel-conversation).

-When your bot is first added to the group or team, it is generally 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. See [Team member or bot addition](~/resources/bot-v3/bots-notifications.md#team-member-or-bot-addition) for more details.

-Because bots in a group or channel respond only when they are mentioned ("@*botname*") in a message, every message received by a bot in a group channel contains its own name, and you must ensure your message parsing handles that. In addition, bots can parse out other users mentioned and mention users as part of their messages.

-description: Describes the end-to-end scenario of having a one-on-one conversation with a bot in Microsoft Teams

-keywords: teams scenarios 1on1 1to1 conversation bot

-description: Learn how to use proactive messaging for bots in Microsoft Teams

-keywords: teams scenarios proactive messaging conversation bot

-* Welcome messages for personal bot conversations

-* Poll responses

-* External event notifications

-Sending a message to start a new conversation thread is different than sending a message in response to an existing conversation: when your bot starts a new conversation, there is no pre-existing conversation to post the message to. To send a proactive message, you need to:

-Sending proactive messages is an effective way to communicate with your users. However, from the user's perspective, the message appears unprompted. If there is a welcome message, it will be the first time that theyΓÇÖve interacted with your app. It's important to use this functionality and provide the complete information to the user to understand the purpose of this message.

-When using proactive messaging to send a welcome message to a user, ensure that from the user's perspective, the message appears unprompted. If there is a welcome message, it will be the first time that theyΓÇÖve interacted with your app. The best welcome messages will include:

-See [Install apps for users](/graph/api/userteamwork-post-installedapps?view=graph-rest-1.0&tabs=http&preserve-view=true) in the Graph documentation for complete details. There is also a [sample in .NET](https://github.com/microsoftgraph/contoso-airlines-teams-sample/blob/283523d45f5ce416111dfc34b8e49728b5012739/project/Models/GraphService.cs#L176).

-description: Describes how to send and receive messages with bots in Microsoft Teams

-keywords: teams bots messages

-Pictures can be at most 1024×1024 MB and 1 MB in PNG, JPEG, or GIF format; animated GIF is not supported.

-To issue a message update, simply perform a PUT request against the `/v3/conversations/<conversationId>/activities/<activityId>/` endpoint using a given activity ID. To complete this scenario, you should cache the activity ID returned by the original POST call.

-description: Describes cards and how they are used in bot messages

-keywords: bots cards messaging

-A *card* is a user-interface (UI) container for short or related pieces of information. Cards can have multiple properties and attachments. Teams support cards in bots, connectors and message extensions. See [Cards](~/task-modules-and-cards/what-are-cards.md) for an overview of what cards are and how Teams uses them.

-description: Describes how to get context for bots in Microsoft Teams

-keywords: teams bots context

-description: Describes how to create bots in Microsoft Teams

-keywords: teams bots creation

-description: Learn how to send and receive files through the bot using Graph APIs for personal, channel and groupchat scopes. Use Teams bot APIs using code samples based on the v3 Bot Framework SDK.

-keywords: teams bots files send receive

-The definition will look like this: `"supportsFiles": true`. If your bot does not enable `supportsFiles`, the following features will not work.

-4. Optionally, you can remove the original consent card if you do not want to allow the user to accept further uploads of the same file.

-After uploading a file to the user's OneDrive, whether you use the mechanism described above or OneDrive user delegated APIs, you should send a confirmation message to the user. This message should contain a `FileCard` attachment that the user can click on, either to preview it, open it in OneDrive, or download locally.

-description: Describes how to create menus for bots in Microsoft Teams

-keywords: teams bots menus creation

-description: Describes the details of formatting for bot messages

-keywords: teams scenarios channels conversation bot message

-* Text-only messages do not support table formatting.

-* Rich cards do not support Markdown or table formatting.

-To ensure that your formatting works across all platforms supported by Microsoft Teams, be aware that some styles are not currently supported across all platforms.

-| bold | Γ£ö | Γ£û |

-| italic | Γ£ö | Γ£ö |

-| header (levels 1&ndash;3) | Γ£û | Γ£ö |

-| strikethrough | Γ£û | Γ£ö |

-| horizontal rule | Γ£û | Γ£û |

-| unordered list | Γ£û | Γ£ö |

-| ordered list | Γ£û | Γ£ö |

-| preformatted text | Γ£ö | Γ£ö |

-| blockquote | Γ£ö | Γ£ö |

-| hyperlink | Γ£ö | Γ£ö |

-| image link | Γ£ö | Γ£û |

-| bold | Γ£ö | Γ£ö | Γ£ö |

-| italic | Γ£ö | Γ£ö | Γ£ö |

-| header (levels 1&ndash;3) | Γ£û | Γ£û | Γ£û |

-| strikethrough | Γ£ö | Γ£ö | Γ£û |

-| horizontal rule | Γ£û | Γ£û | Γ£û |

-| unordered list | Γ£ö | Γ£û | Γ£û |

-| ordered list | Γ£ö | Γ£û | Γ£û |

-| preformatted text | Γ£ö | Γ£ö | Γ£ö |

-| blockquote | Γ£ö | Γ£ö | Γ£ö |

-| hyperlink | Γ£ö | Γ£ö | Γ£ö |

-| image link | Γ£ö | Γ£ö | Γ£ö |

-description: Describes what notification-only bots are in Microsoft Teams

-keywords: teams bots notification

-If your bot's sole purpose is to deliver notification to users and is not conversational, you can enable the `isNotificationOnly` field in your app manifest. This produces the following changes:

-* Users cannot message your notification-only bot.

-* Users cannot @mention the bot.

-description: Describes how to handle events in bots for Microsoft Teams

-keywords: teams bots events

-Teams and group events, usually triggered off the `conversationUpdate` type, have additional Teams event information passed as part of the `channelData` object, and therefore your event handler must query the `channelData` payload for the Teams `eventType` and additional event-specific metadata.

-The [`conversationUpdate`](/azure/bot-service/dotnet/bot-builder-dotnet-activities?view=azure-bot-service-3.0#conversationupdate&preserve-view=true) event is sent to your bot when it receives information on membership updates for teams where it has been added. It also receives an update when it has been added for the first time specifically for personal conversations. Note that the user information (`Id`) is unique for your bot and can be cached for future use by your service, such as, sending a message to a specific user.

-Your bot is notified when the team it is in has been renamed. It receives a `conversationUpdate` event with `eventType.teamRenamed` in the `channelData` object. Please note that there are no notifications for team creation or deletion, because bots exist only as part of teams and have no visibility outside the scope in which they have been added.

-The `messageReaction` event is sent when a user adds or removes his or her reaction to a message which was originally sent by your bot. `replyToId` contains the ID of the specific message.

-description: Describes how to get started developing bots in Microsoft Teams

-keywords: teams bots development

-A bot behaves differently depending on what kind of conversation it is involved in. Bots in Teams support several kinds of conversations called scopes in the [app manifest](~/resources/schem).

-* `groupChat` A conversation between a bot and 2 or more users.

-The following topics will guide you through the process of creating a great bot for Teams:

-description: This article describes how to test bots in Microsoft Teams

-keywords: teams bots testing

-If you're hosting your bot locally during development you'll need to use a tunneling service like [ngrok](https://ngrok.com/) in order to test your bot. Once you've downloaded and installed ngrok, run the below command to start the tunneling service. You may need to add ngrok to your path.

-The Bot Framework Emulator is a desktop application that allows bot developers to test and debug their bots, either locally or remotely. Using the emulator, you can chat with your bot and inspect the messages that your bot sends and receives. This can be useful for verifying that your bot is available and responding, however the emulator won't allow you to test any Teams-specific functionality you've added to your bot, nor will responses from your bot be an accurate visual representation of how they are rendered in Teams. If you need to test either of those things isn't best to [upload your bot](#test-by-uploading-to-teams).

-Note that users can choose to block your bot from sending personal chat messages. They may toggle this by right-clicking your bot in the chat channel and choosing **Block bot conversation**. This means your bots will continue to send messages but the user won't receive those messages.

-Bots in personal context cannot be disabled or removed by a user, short of completely removing the bot from 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. This prevents users from discovering, adding, or interacting with your bot. Note that this does not remove the bot from other users' Teams instances, although it will cease functioning for them as well.

-description: Describes text formatting support in bot conversations

-keywords: bots conversations messaging

-* Text-only messages do not support table formatting

-To ensure that your formatting works across all platforms supported by Microsoft Teams, be aware that some styles are not currently supported across all platforms.

-description: This article describes how to use tabs and bots together.

-keywords: teams bots tabs development

-Deep links rely on an entityId, which is an opaque value that maps to a unique entity in your system. When the tab is created, you ideally store some simple state, For example, flag on your backend indicating the tab has been created in the channel. When your bot constructs a message, it can target the entityId associated with that tab.

-1. If you wish to notify an entire channel your bot can asynchronously post a message to the channel. There is no way for a bot to proactively create the tab conversation if it wasn't created with the tab.

-1. Prepare your development environment

-2. Create and deploy your web service (while developing use a tunneling service like ngrok to run it locally)

-3. Register your web service with the Bot Framework

-4. Create your app package

-5. Upload your package to Microsoft Teams

-description: In this learning article, fetch answers to some frequently asked questions while using the Moodle LMS.

-description: Bots on Microsoft Teams support only the following media formats for audio and video content.

-keywords: teams bots media formats

-description: Create Action-based message extensions to allow users to trigger external services

-keywords: teams message extensions message extensions search

-description: Describes how to get started with message extensions in Microsoft Teams

-keywords: teams messaging extensions messaging extensions

-Message extensions appear along the bottom of the compose box. A few are built in, such as Emoji, Giphy, and Sticker. Choose the **More Options** (**&#8943;**) button to see other message extensions, including those you add from the app gallery or upload yourself.

-* Work items and bugs

-* Customer support tickets

-* Usage charts and reports

-* Images and media content

-* Sales opportunities and leads

-description: Describes how to develop search based message extensions

-keywords: teams message extensions message extensions search

-* Audio or video calls

-* Chat with students

-* Courses and activity management

-* Badges and rewards

-* Analytical insights

-description: Describes how the removal of tab margins enhances app building experience.

-keywords: tab removing margins padding

-keywords: cookie attributes samesite

-keywords: teams manifest schema localization

-|`name`|32 characters|Γ£ö|The display name for the developer.|

-|`websiteUrl`|2048 characters|Γ£ö|The https:// URL to the developer's website. This link should take users to your company or product-specific landing page.|

-|`privacyUrl`|2048 characters|Γ£ö|The https:// URL to the developer's privacy policy.|

-|`termsOfUseUrl`|2048 characters|Γ£ö|The https:// URL to the developer's terms of use.|

-|`mpnId`|10 characters|Γ£ö|**Optional** The Microsoft Partner Network ID that identifies the partner organization building the app.|

-|`defaultLanguageTag`|4 characters|Γ£ö|The language tag of the strings in this top level manifest file.|

-|`languageTag`|4 characters|Γ£ö|The language tag of the strings in the provided file.|

-|`file`|4 characters|Γ£ö|A relative file path to the .json file containing the translated strings.|

-|`short`|30 characters|Γ£ö|The short display name for the app.|

-|`short`|80 characters|Γ£ö|A short description of your app experience, used when space is limited.|

-|`full`|4000 characters|Γ£ö|The full description of your app.|

-|`outline`|2048 characters|Γ£ö|A relative file path to a transparent 32x32 PNG outline icon.|

-|`color`|2048 characters|Γ£ö|A relative file path to a full color 192x192 PNG icon.|

-|`configurationUrl`|String|2048 characters|Γ£ö|The https:// URL to use when configuring the tab.|

-|`scopes`|Array of enum|1|Γ£ö|Currently, configurable tabs support only the `team` and `groupchat` scopes. |

-|`entityId`|String|64 characters|Γ£ö|A unique identifier for the entity that the tab displays.|

-|`name`|String|128 characters|Γ£ö|The display name of the tab in the channel interface.|

-|`contentUrl`|String|2048 characters|Γ£ö|The https:// URL that points to the entity UI to be displayed in the Teams canvas.|

-|`scopes`|Array of enum|1|Γ£ö|Currently, static tabs support only the `personal` scope, which means it can be provisioned only as part of the personal experience.|

-|`botId`|String|64 characters|Γ£ö|The unique Microsoft app ID for the bot as registered with the Bot Framework. This may well be the same as the overall [app ID](#id).|

-|`scopes`|Array of enum|3|Γ£ö|Specifies whether the bot offers an experience in the context of a channel in a `team`, in a group chat (`groupchat`), or an experience scoped to an individual user alone (`personal`). These options are non-exclusive.|

-|`items.scopes`|array of enum|3|Γ£ö|Specifies the scope for which the command list is valid. Options are `team`, `personal`, and `groupchat`.|

-|`items.commands`|array of objects|10|Γ£ö|An array of commands the bot supports:<br>`title`: the bot command name (string, 32).<br>`description`: a simple description or example of the command syntax and its argument (string, 128).|

-|`configurationUrl`|String|2048 characters|Γ£ö|The https:// URL to use when configuring the connector.|

-|`connectorId`|String|64 characters|Γ£ö|A unique identifier for the Connector that matches its ID in the [Connectors Developer Dashboard](https://aka.ms/connectorsdashboard).|

-|`scopes`|Array of enum|1|Γ£ö|Specifies whether the Connector offers an experience in the context of a channel in a `team`, or an experience scoped to an individual user alone (`personal`). Currently, only the `team` scope is supported.|

-|`botId`|String|64|Γ£ö|The unique Microsoft app ID for the bot that backs the message extension, as registered with the Bot Framework. This may well be the same as the overall [app ID](#id).|

-|`commands`|Array of object|10|Γ£ö|Array of commands the message extension supports|

-|`id`|String|64 characters|Γ£ö|The ID for the command.|

-|`title`|String|32 characters|Γ£ö|The user-friendly command name.|

-|`parameters`|Array of object|5|Γ£ö|The list of parameters the command takes. Minimum: 1; maximum: 5|

-|`parameter.name`|String|64 characters|Γ£ö|The name of the parameter as it appears in the client. This is included in the user request.|

-|`parameter.title`|String|32 characters|Γ£ö|User-friendly title for the parameter.|

-|`id`|String|36 characters|Γ£ö|Microsoft Azure Active Directory (Azure AD) application ID of the app. This ID must be a GUID.|

-|`resource`|String|2048 characters|Γ£ö|Resource URL of the app for acquiring auth token for SSO.|

-|`applicationPermissions`|Array|Maximum 100 items|Γ£ö|Resource permissions for application.|

-|`notificationUrl`|string|2048 characters|Γ£ö|The url where Graph-connector notifications for the application should be sent.|

-|`type`|string|32 characters|Γ£ö|The notification type. *See below*.|

-|`description`|string|128 characters|Γ£ö|A brief description of the notification. *See below*.|

-|`templateText`|string|128 characters|Γ£ö|Ex: "{actor} created task {taskId} for you"|

-|`offerId`| string | 2,048 characters | Γ£ö | A unique identifier that includes your Publisher ID and Offer ID, which you can find in [Partner Center](https://partner.microsoft.com/dashboard). You must format the string as `publisherId.offerId`.|

-|`id`|||Γ£ö| The unique identifier for the scene. This id must be a GUID. |

-|`name`| string | 128 characters |Γ£ö| The name of the scene. |

-|`file`|||Γ£ö| The relative file path to the scenes' metadata json file. |

-|`preview`|||Γ£ö| The relative file path to the scenes' PNG preview icon. |

-|`maxAudience`| integer | 50 |Γ£ö| The maximum number of audiences supported in the scene. |

-|`seatsReservedForOrganizersOrPresenters`| integer | 50 |Γ£ö| The number of seats reserved for organizers or presenters.|

-|`type`|string||Γ£ö| The type of the resource-specific permission. Options: `Application` and `Delegated`.|

-|`name`|string|128 characters|Γ£ö|The name of the resource-specific permission. For more information, see [Resource-specific application permissions](#resource-specific-application-permissions) and [Resource-specific delegated permissions](#resource-specific-delegated-permissions)|

-|`name`|32 characters|Γ£ö|The display name for the developer.|

-|`websiteUrl`|2048 characters|Γ£ö|The https:// URL to the developer's website. This link must take users to your company or product-specific landing page.|

-|`privacyUrl`|2048 characters|Γ£ö|The https:// URL to the developer's privacy policy.|

-|`termsOfUseUrl`|2048 characters|Γ£ö|The https:// URL to the developer's terms of use.|

-|`short`|30 characters|Γ£ö|The short display name for the app.|

-|`short`|80 characters|Γ£ö|A short description of your app experience, used when space is limited.|

-|`full`|4000 characters|Γ£ö|The full description of your app.|

-|`defaultLanguageTag`||Γ£ö|The language tag of the strings in this top-level manifest file.|

-|`languageTag`||Γ£ö|The language tag of the strings in the provided file.|

-|`file`||Γ£ö|A relative file path to the .json file containing the translated strings.|

-|`outline`|32 x 32 pixels|Γ£ö|A relative file path to a transparent 32x32 PNG outline icon.|

-|`color`|192 x 192 pixels|Γ£ö|A relative file path to a full color 192x192 PNG icon.|

-|`configurationUrl`|string|2048 characters|Γ£ö|The https:// URL to use when configuring the tab.|

-|`scopes`|array of enums|1|Γ£ö|Currently, configurable tabs support only the `team` and `groupchat` scopes. |

-|`entityId`|string|64 characters|Γ£ö|A unique identifier for the entity that the tab displays.|

-|`name`|string|128 characters|Γ£ö|The display name of the tab in the channel interface.|

-|`contentUrl`|string||Γ£ö|The https:// URL that points to the entity UI to be displayed in the Teams canvas.|

-|`scopes`|array of enums|1|Γ£ö|Currently, static tabs support only the `personal` scope, which means it can be provisioned only as part of the personal experience.|

-|`botId`|string|64 characters|Γ£ö|The unique Microsoft app ID for the bot as registered with the Bot Framework. The ID can be the same as the overall [app ID](#id).|

-|`scopes`|array of enums|3|Γ£ö|Specifies whether the bot offers an experience in the context of a channel in a `team`, in a group chat (`groupchat`), or an experience scoped to an individual user alone (`personal`). These options are non-exclusive.|

-|`items.scopes`|array of enums|3|Γ£ö|Specifies the scope for which the command list is valid. Options are `team`, `personal`, and `groupchat`.|

-|`items.commands`|array of objects|10|Γ£ö|An array of commands the bot supports:<br>`title`: the bot command name (string, 32)<br>`description`: a simple description or example of the command syntax and its argument (string, 128).|

-|title|string|12|Γ£ö|The bot command name.|

-|description|string|128 characters|Γ£ö|A simple text description or an example of the command syntax and its arguments.|

-|`configurationUrl`|string|2048 characters|Γ£ö|The https:// URL to use when configuring the connector.|

-|`scopes`|array of enums|1|Γ£ö|Specifies whether the Connector offers an experience in the context of a channel in a `team`, or an experience scoped to an individual user alone (`personal`). Currently, only the `team` scope is supported.|

-|`connectorId`|string|64 characters|Γ£ö|A unique identifier for the Connector that matches its ID in the [Connectors Developer Dashboard](https://aka.ms/connectorsdashboard).|

-|`botId`|string|64|Γ£ö|The unique Microsoft app ID for the bot that backs the message extension, as registered with the Bot Framework. The ID can be the same as the overall App ID.|

-|`commands`|array of objects|10|Γ£ö|Array of commands the message extension supports.|

-|`id`|string|64 characters|Γ£ö|The ID for the command.|

-|`title`|string|32 characters|Γ£ö|The user-friendly command name.|

-|`parameters`|array of object|5 items|Γ£ö|The list of parameters the command takes. Minimum: 1; maximum: 5.|

-|`parameters.name`|string|64 characters|Γ£ö|The name of the parameter as it appears in the client. The parameter name is included in the user request.|

-|`parameters.title`|string|32 characters|Γ£ö|User-friendly title for the parameter.|

-|`parameters.choices.title`|string|128 characters|Γ£ö|Title of the choice.|

-|`parameters.choices.value`|string|512 characters|Γ£ö|Value of the choice.|

-|`id`|string|36 characters|Γ£ö|Azure AD application ID of the app. This ID must be a GUID.|

-|`resource`|string|2048 characters|Γ£ö|Resource URL of app for acquiring auth token for SSO. </br> **NOTE:** If you are not using SSO, ensure that you enter a dummy string value in this field to your app manifest, for example, <https://notapplicable> to avoid an error response. |

-|`notificationUrl`|string|2048 characters|Γ£ö|The url where Graph-connector notifications for the application should be sent.|

-|`type`|string|32 characters|Γ£ö|The notification type. *See below*.|

-|`description`|string|128 characters|Γ£ö|A brief description of the notification. *See below*.|

-|`templateText`|string|128 characters|Γ£ö|Ex: "{actor} created task {taskId} for you"|

-|`offerId`| string | 2,048 characters | Γ£ö | A unique identifier that includes your Publisher ID and Offer ID, which you can find in [Partner Center](https://partner.microsoft.com/dashboard). You must format the string as `publisherId.offerId`.|

-|`id`|||Γ£ö| The unique identifier for the scene. This id must be a GUID. |

-|`name`| string | 128 characters |Γ£ö| The name of the scene. |

-|`file`|||Γ£ö| The relative file path to the scenes' metadata json file. |

-|`preview`|||Γ£ö| The relative file path to the scenes' PNG preview icon. |

-|`maxAudience`| integer | 50 |Γ£ö| The maximum number of audiences supported in the scene. |

-|`seatsReservedForOrganizersOrPresenters`| integer | 50 |Γ£ö| The number of seats reserved for organizers or presenters.|

-|`type`|string||Γ£ö| The type of the resource-specific permission. Options: `Application` and `Delegated`.|

-|`name`|string|128 characters|Γ£ö|The name of the resource-specific permission. For more information, see [Resource-specific application permissions](#resource-specific-application-permissions) and [Resource-specific delegated permissions](#resource-specific-delegated-permissions)|

-description: Describes upcoming and in-progress changes to the Bot APIs used for retrieving members of teams and chats

-keywords: bot framework apis team members roster

-description: steps for creating and publishing Teams documentation

-* Microsoft Power platform

-* Microsoft Teams app templates

-description: Learn about implementing tabs on Microsoft Teams mobile, their authentication, low bandwidth connection, testing on mobile clients, distribution, and more.

-keywords: app mobile tab channel group authentication distribution

-keywords: UI kit manage tab set-up single-sign-on sso deep linking role-based view thread discussion

-description: Describes how to get user context to your tabs

-keywords: teams tabs user context

-description: Describes authentication flow in tabs, OAuth by Azure AD, and provides code sample

-keywords: teams authentication flow tabs third party OAuth provider

-description: Describes authentication using external OAuth providers

-keywords: teams authentication using external OAuth provider

-description: Describes silent authentication, Single-sign-on, Azure AD for tabs

-keywords: teams authentication SSO silent Azure AD tab

-description: Describes authentication in Teams and how to use it in tabs

-keywords: teams authentication tabs Microsoft Azure Active Directory (Azure AD)

-description: Learn about building tabs using Adaptive Cards with Code examples, including invoking activities, understanding task module workflow, and authentication.

-keywords: adaptive card personal app authentication data flow

-description: Learn to create conversational subentity chat for your channel tabs, to manage conversations using code samples

-keywords: teams tabs channel configurable

-description: A quickstart guide to creating a channel and group tab with the Yeoman Generator for Microsoft Teams, including reviewing source code with code examples.

-description: A quickstart guide to creating a personal tab with the Yeoman Generator, ASP.NET Core, or ASP.NET Core MVC for Microsoft Teams using Node.js, and updating app manifest.

-keywords: yeoman ASP.NET MVC package appmanifest conversation domain permission store

-description: Learn how to create a configuration page to configure a channel or group chat for settings, such as, getting context data, inserting placeholders, and authentication using code examples.

-keywords: teams tabs group channel configurable

-description: how to create a content page

-keywords: teams tabs group channel configurable static

-description: How to create a tab removal page

-keywords: teams tabs group channel configurable remove delete

-description: Describes how to get to the DevTools when using the Microsoft Teams Desktop Client and debugging

-keywords: devtools debug mobile chrome desktop client developer tools tab

-description: Every tab in Microsoft Teams must adhere to these requirements.

-keywords: teams tabs group channel configurable

-description: Overview of the Microsoft Teams JavaScript client SDK, which can help you build app experiences hosted in an <iframe> in Teams, Office, and Outlook.

-keywords: teams tabs group channel configurable static SDK JavaScript personal m365

-description: An overview of custom tabs on the Teams platform

-description: Learn about types of cards supported in bots for Teams, such as, Adaptive cards, Hero card, Thumbnail card, and more. Learn about card actions and invoking task modules in channels, bots, or deep links.

-* Open a URL

-* Send messages and payload to the bot

-* Initiate OAuth flow

-description: A quick overview of Universal Actions for Adaptive Cards, such as user-specific views, sequential workflow support, and more for desktop and mobile environments

-You can get started by updating scenarios using the [quick start guide](Work-with-universal-actions-for-adaptive-cards.md) and leverage Universal Actions.

-* [Adaptive Cards @ Ignite 2020](https://techcommunity.microsoft.com/t5/video-hub/elevate-user-experiences-with-teams-and-adaptive-cards/m-p/1689460)

-description: Learn about Sequential Workflows for Adaptive cards using Universal Actions with Code samples

-description: Learn about up to date views using Universal Bot with Code samples

-keywords: approval base card reject adaptive

-description: Learn about User Specific Views using Universal Actions with Code Sample

-Earlier if Adaptive Cards were sent in a Teams conversation, all users see the exact same card content. With the introduction of the Universal Actions model and `refresh` for Adaptive Cards, bot developers can now provide User Specific Views of Adaptive Cards to users. The same Adaptive Card can now refresh to a User Specific Adaptive Card. Maximum 60 different users can see a different version of the card with additional information or actions. The Adaptive Card provides powerful scenarios like approvals, poll creator controls, ticketing, incident management, and project management cards.

-> User Specific View is supported for Adaptive Cards sent by a bot and is dependent on Universal Actions.

-Card design guidelines to keep in mind while designing User Specific Views:

-* You can create a maximum of **60 User Specific Views** for a particular card sent to a chat or channel by specifying their `userIds` in the `refresh` section.

-* **Base Card:** The base version of the card that the bot developer sends to the chat. The base version is the version of the Adaptive Card for all users who are not specified in the `userIds` section.

-* A message update can be used to update the base card and simultaneously refresh the User Specific Card. Opening the chat or channel also refreshes the card for users with refresh enabled.

-* For scenarios with larger groups where users switch to a view on action, which needs dynamic updates for responders, you can keep adding up to 60 users to the `userIds` list. You can remove the first responder from the list when the 61st user responds. For the users who get removed from the `userIds` list, you can provide a manual refresh button or use the refresh button in the message options menu to get the latest result.

-* Give a prompt to users to get a User Specific View, where they see only a particular view of the card or some actions.

-description: Learn to work with the Universal Actions for Adaptive Cards, including Schema for UniversalActions for Adaptive cards, Refresh model, and backward compatibility using Code samples.

- > Specify the `userIds` property to identify, which users get automatic updates.

-* If the `userIds` list property is specified as `userIds: []` in the refresh section of the card, the card is not automatically refreshed. Instead, a **Refresh Card** option is displayed to the user in the triple dot menu in web or desktop and in the long press context menu in mobile, that is, Android or iOS to manually refresh the card.

-| Sequential Workflows Adaptive Cards | Demonstrate how to implement Sequential Workflows, User Specific Views, and up to date Adaptive Cards in bots. | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/bot-sequential-flow-adaptive-cards/csharp) | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/bot-sequential-flow-adaptive-cards/nodejs) |

-description: Describes card actions in Microsoft Teams and how to use them in your bots

-keywords: teams bots cards actions

-description: Describes card text formatting in Microsoft Teams

-keywords: teams bots cards format

-description: Describes all the cards and card actions available to bots in Teams

-keywords: bots cards reference

-| Adaptive Card | Γ£ö | Γ£û | Γ£ö | Γ£ö | Γ£ö | Γ£ö | Γ£û |

-| Office 365 Connector card | Γ£ö | Γ£û | Γ£ö | Γ£û | Γ£ö | Γ£ö | Γ£ö |

-| Hero card | Γ£ö | Γ£ö | Γ£ö | Γ£û | Γ£ö | Γ£ö | Γ£û |

-| Thumbnail card | Γ£ö | Γ£ö | Γ£ö | Γ£û | Γ£ö | Γ£ö | Γ£û |

-| List card | Γ£ö | Γ£û | Γ£û | Γ£û | Γ£ö | Γ£ö | Γ£û |

-| Receipt card | Γ£ö | Γ£û | Γ£û | Γ£û | Γ£û | Γ£ö | Γ£û |

-| Signin card | Γ£ö | Γ£û | Γ£û | Γ£û | Γ£û | Γ£û | Γ£û |

-| Γ£ö | Γ£ö | Γ£û | Γ£ö |

-| Γ£ö | Γ£ö | Γ£û | Γ£ö |

-| Γ£ö | Γ£û | Γ£û |Γ£ö |

-| Γ£ö | Γ£ö | Γ£ö | Γ£û |

-| Γ£ö | Γ£ö | Γ£û | Γ£ö |

-| Γ£ö | Γ£û | Γ£û | Γ£ö |

-| Γ£ö | Γ£ö | Γ£û | Γ£ö |

-| Γ£ö | Γ£û | Γ£û | Γ£ö |

-| Γ£ö | Γ£ö | Γ£û | Γ£ö |

-description: Learn how to design Adaptive Cards for Teams and get the Microsoft Teams UI Kit.

-When the the size of something you're displaying doesn't need to change, set you columns to a specific pixel width. This example shows the left column sized at 50 pixels, while the descriptions next to the thumbnails stretch the length of the card

-description: Describes typeahead search with Input.ChoiceSet control in Adaptive Cards

-description: Describes how to use the People Picker control in Adaptive Cards

-keywords: Adaptive Cards People Picker

-description: Learn how to design task modules for Teams apps and get the Microsoft Teams UI Kit.

-description: How to use task modules with Microsoft Teams bots, including Bot Framework cards, Adaptive cards, and deep links.

-keywords: task modules teams bots deep links adaptive card

-description: Explains how to invoke task modules from Teams tabs and submitting its result using the Microsoft Teams client SDK. It includes code samples.

-keywords: task modules teams tabs client sdk

-description: Describes cards and how they're used in bots, connectors, and message extensions

-keywords: connectors bots cards messaging

-description: Add modal popup experiences to collect or display information to your users from your Microsoft Teams apps

-description: Describes TeamsFx Command Line Interface

-| `teamsfx account login <service>` | Log in to the selected cloud service. Service options are M365 or Azure. |

-| `teamsfx account logout <service>` | log out of selected cloud service. Service options are M365 or Azure. |

- * To login to Microsoft 365 account and Azure account:

- * Login to Microsoft 365 account. Ensure that the same Microsoft 365 account is added:

- * Login to Azure account with contributor permission for all Azure resources.

-description: About TeamsFx SDK

-description: Collaborate on TeamsFx Project using Teams Toolkit

-description: About TeamsFX multi environment

-description: Teams App Manifest

-### Preview manifest file in local environment

-### Preview manifest file in remote environment

-If the manifest file is outdated due to configuration file change or template change, select any one of the following action:

-2. You can navigate to configuration file by selecting any one of the config placeholder **Go to config file** or **View the state file** in `manifest.template.json`.

-description: Prepare accounts to build Teams apps

-3. Add environment variables to `.env.teamsfx.local`. They are the configurations for the selected authentication type. The generated code reads values from the environment variables.

-description: Describes Add Capabilities of Teams Toolkit

-description: Describes Add Resources of Teams Toolkit

-description: Describes Add single sign on of Teams Toolkit

-For applications that interact with the user in a chat, a Team, or a channel, SSO manifests as an Adaptive Card which the user can interact with to invoke the Azure AD consent flow.

-The following steps helps you to add SSO using Teams Toolkit in Visual Studio Code

-The following steps helps you to enable SSO in your application.

-The following steps helps you to add a new command, after you add SSO in your project:

-The following concepts helps you for SSO authentication:

-description: Create new Teams app using Teams Toolkit

-### Create a new Teams app

-

-

-1. If you select **Create a new Teams app**, the following image displays with templates from three categories: Scenario-based Teams app, Basic Teams app, and Extended Teams apps across Microsoft 365:

-### Create a new Teams app using view samples

-

-description: Function of Visual studio code and Teams Toolkit during local debug

- |Windows, macOs (x64), and Linux | **3.1 (recommended)**, 5.0, 6.0 |

- |macOs (arm64) |6.0 |

-description: Debug your Teams app locally in Teams Toolkit

-## Debug your Teams app locally

-description: Deploy app to the cloud, Azure, or SharePoint

-description: Provision cloud resources

-description: publish Teams apps

-description: Overview of Teams Toolkit, Installation of Teams Toolkit, and Tour of Toolkit features

-description: CI/CD templates

-description: Get started building great custom apps directly within Visual Studio with the Microsoft Teams Toolkit. Learn to configure your app in Visual Studio, validate your app, and publish it from Visual Studio and Developer Portal.

-keywords: teams visual studio toolkit

-description: Add Incoming Webhook to Teams app and post any external requests to Teams using it

-keywords: teams tabs outgoing webhook

-description: describes how to create an Outgoing Webhook

-keywords: Teams tabs outgoing webhook actionable message verify webhook

-description: Describes how to get started with Office 365 Connectors in Microsoft Teams

-keywords: teams Office365 connector

-description: Describes how to use Office 365 Connectors in Microsoft Teams

-keywords: teams Office365 connector

-description: Understand how webhooks and connectors can connect your web services to the Teams client.