| Service | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| platform | Glossary | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/get-started/glossary.md | Common terms and definitions used in Microsoft Teams developer documentation. | Term | Definition | | | | | [Action command](../messaging-extensions/how-to/action-commands/define-action-command.md) | A type of message extension app that uses a pop-up to collect or display information. <br>**See also**: [Message extension](#m); [Search commands](#s) |-| [Access token](../tabs/how-to/authentication/tab-sso-code.md) | An access token enables a client app to securely call protected web APIs. Access tokens are used by web APIs to perform authentication and authorization. <br> **See also**: [Identity token](#i) <br> For more information, see [Access token](/azure/active-directory/develop/access-tokens) | -| [Adaptive Cards](../task-modules-and-cards/what-are-cards.md) | An actionable content snippet added to a conversation by a bot or message extension. Use text, graphics, and buttons with these cards for rich communication. <br> **See also**: [Task module](#t) | +| [Access token](../tabs/how-to/authentication/tab-sso-code.md) | An access token enables a client app to securely call protected web APIs. Access tokens are used by web APIs to perform authentication and authorization. <br> **See also**: [Identity token](#i) <br> For more information, see [Access token](/azure/active-directory/develop/access-tokens), [Authentication](../concepts/authentication/authentication.md) | +| [Adaptive Cards](../task-modules-and-cards/what-are-cards.md) | An actionable content snippet added to a conversation by a bot or message extension. Use text, graphics, and buttons with these cards for rich communication. <br> **See also**: [Task module](#t); [Adaptive Card Schema Explorer](https://adaptivecards.io/explorer/AdaptiveCard.html) | | [Administrator consent](../tabs/how-to/authentication/tab-sso-register-aad.md) | An administrator can grant consent for the application on behalf of all users in the organization. It helps avoid the need for user consent. <br> [SSO](#s); [Consent dialog](#c); [User consent](#u) | | [Anonymous](../apps-in-teams-meetings/build-apps-for-anonymous-user.md) |Anonymous users don't have an Azure AD identity and aren't federated with a tenant. The anonymous participants are 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. <br>**See also**: [Federated or external](#f); [In-tenant](#i); [Guest](#g)| | [App Catalog](../toolkit/publish.md) | A site that stores SharePoint and Office apps for an organization's internal use. <br>**See also**: [SPFx](#s) | | [App Caching](../tabs/how-to/app-caching.md) | App caching improves subsequent launch time of the apps within Teams by allowing you to keep some resources and assets in memory that you can use when rehydrating your app.| | [App manifest](../resources/schem) | The app manifest (previously called Teams app manifest) describes how the app integrates into Microsoft Teams and also how to extend your app to run across Microsoft 365. Your manifest must conform to the [app manifest schema](https://developer.microsoft.com/json-schemas/teams/v1.11/MicrosoftTeams.schema.json). | | [App package](../concepts/build-and-test/apps-package.md) | A Teams app package is a zip file that contains the app manifest file, color icon, and outline icon. |-| [Application permission](../concepts/device-capabilities/browser-device-permissions.md#enable-apps-device-permissions) | An option in a Teams app to enable device permissions. It's available only when the manifest file of the app declares that the app needs device permissions. <br> **See also**: [Device permissions](#d) | +| [Application permission](/graph/permissions-overview?tabs=http#application-permissions) | Application permissions are used in the app-only access scenario, without a signed-in user present. The application will be able to access any data that the permission is associated with. | | [App scope](../concepts/design/understand-use-cases.md#app-scope) | An area in Teams where people can use your app. Apps can have one or many scopes, including personal, channels, chats, and meetings. A Teams app can exist across scopes. <br> **See also**: [Default install scope](#d) | | App tray | An application tray located on the bottom bar of a Teams mobile app. It collects all apps that are open but not currently used or active. <br>**See also**: [Teams Mobile](#t) | | [Application ID](../tabs/how-to/authentication/tab-sso-register-aad.md) | The application ID, or client ID, is a value the Microsoft identity platform assigns to your application when you register it in Azure AD. The application ID is a GUID value that uniquely identifies the application and its configuration within the identity platform. <br> **See also**: [GUID](#g); [Client ID](#c); [Application ID URI](#a); [Subdomain ID](#s) | | [Application ID URI](../tabs/how-to/authentication/tab-sso-register-aad.md) | The globally unique URI used to identify this web API. It's the prefix for scopes and in access tokens, it's the value of the audience claim. Also referred to as an identifier URI. <br> **See also**: [Token exchange URL](#t); [Configure your bot or message extension app in Azure AD](../bots/how-to/authentication/bot-sso-register-aad.md) |-| [Authentication](../concepts/authentication/authentication.md) | The process to validate a user's identity to access your app. <br> **See also**: [Identity providers](#i); [SSO](#s) | +|[Authentication](../concepts/authentication/authentication.md)|The process to validate a user's identity to access your app. <br> **See also**: [Identity providers](#i); [SSO](#s); [authentication](../m365-apps/teamsjs-support-m365.md#authentication)| | [Authentication flow](../concepts/authentication/authentication.md) | The way a user is authenticated to use your app. For Teams apps, we recommend using Single Sign-on (SSO) using Azure Active Directory (AD); but an alternative is to use a third-party IdP. <br> **See also**: [SSO](#s); [Identity provider](#i) | | [Authorization](../resources/schem#authorization)| An app manifest property (`authorization`) that specifies and consolidates authorization related information for the app. <br> **See also**: [Permission](#p)|-| [Azure Active Directory](../tabs/how-to/authentication/auth-tab-aad.md) | MicrosoftΓÇÖs cloud-based identity and access management service. It helps authenticated users access internal and external resources. | +| [Azure Active Directory](../tabs/how-to/authentication/auth-tab-aad.md) | MicrosoftΓÇÖs cloud-based identity and access management service. It helps authenticated users access internal and external resources. <br> **See also**: [System for Cross-Domain Identity Management (SCIM)](/azure/active-directory/architecture/sync-scim)| | [Azure resource](../toolkit/provision.md) | A service that is available through Azure that your Teams app can use for Azure deployment. It could be storage accounts, web apps, databases, and more. | ## B Common terms and definitions used in Microsoft Teams developer documentation. | Term | Definition | | | |-| [Call bot](../bots/calls-and-meetings/calls-meetings-bots-overview.md) | A bot that participates in audio or video calls and online meetings. <br> **See also**: [Chat bot](#c); [Meeting bot](#m) | +| [Call bot](../bots/calls-and-meetings/calls-meetings-bots-overview.md) | A bot that participates in audio or video calls and online meetings. <br> **See also**: [Chat bot](#c); [Meeting bot](#m); [Real-time media calls and meetings](../bots/calls-and-meetings/real-time-media-concepts.md) | | [Capabilities](../concepts/design/map-use-cases.md#app-capabilities-mapped-to-features)| Capabilities are the core functionalities that you can build in your app. They're also called entry or extension points because they enable integration and interaction. <br> **See also**: [App scope](#a)| | [Chat bot](../bots/how-to/conversations/conversation-basics.md) | A bot is also referred to as a chatbot or conversational bot. It's an app that runs simple and repetitive tasks for users such as customer service or support staff. <br> **See also**: [Conversational bot](#c) | | Channel | A single place for a team to share messages, tools, and files. You can use a channel for teamwork and communication. <br> **See also**: [Conversation](#c) | | Client ID | The client ID, or the application ID is a value the Microsoft identity platform assigns to your application when you register it in Azure AD. It's a GUID value that uniquely identifies the application and its configuration within the identity platform. <br> **See also**: [Application ID](#a); [GUID](#g); [Subdomain ID](#s) |-| [Client secret](../bots/how-to/authentication/bot-sso-register-aad.md) | A secret string that an app uses to prove its identity when requesting a token. Also, it can be referred to as application password. <br> **See also**: [Microsoft app password](#m) | +| [Client secret](../bots/how-to/authentication/bot-sso-register-aad.md) | A secret string that an app uses to prove its identity when requesting a token. Also, it can be referred to as application password. <br> **See also**: [Microsoft app password](#m) <br> For more information, see [Authentication](../concepts/authentication/authentication.md)| | [Cloud resources](../toolkit/add-resource.md) | A service that is available on cloud through internet that your Teams app can use. It could be storage accounts, web apps, databases, and more. | | [Configurable tab](../resources/schem#configurabletabs)| Configurable tabs are also known as channel or group tabs. Configurable tabs are used when your app experience has a team channel tab experience, which requires extra configuration before it's added. <br> **See also**: [App manifest](#a)| | [Configuration URL](../resources/schem#configurabletabs)| An app manifest property (`configurationUrl`) where the HTTPS URL to use when configuring the tab or connector. <br> **See also**: [App manifest](#a)| | [Collaboration app](../concepts/extensibility-points.md) | An app with capabilities for a user to work in a collaborative workspace with other users. <br> **See also**: [Standalone app](#s) | | [Collaborative Stage View](../tabs/tabs-link-unfurling.md#collaborative-stage-view) | Collaborative Stage View is an enhancement to Stage View that allows users to engage with your app content in a new Teams window. <br> **See also**: [Stage View](#s)| | [Compose Extensions](../resources/schem#composeextensions) | An app manifest property (`composeExtensions`) that refers to message extension capability. It's used when your extension needs to either authenticate or configure to continue. <br>**See also**: [App manifest](#a); [Message extension](#m) |-| [Command Box](../resources/schem) | A type of context in app manifest (`commandBox`) that you can configure to invoke a message extension from Teams command box. | +| [Command Box](../resources/schem) | A type of context in app manifest (`commandBox`) that you can configure to invoke a message extension from Teams command box. <br>**See also**: [Message extension](#m) | | [Command lists](../resources/schem#botscommandlists)| An app manifest property (`commandLists`) that consists of a list of commands that the bot supplies, including their usage, description, and the scope for which the commands are valid. For each scope, you must use a specific command list. <br> **See also**: [App manifest](#a)| | Connection Name | The name of OAuth connection that you configure for enabling SSO connection for your bot resource. <br> **See also**: [OAuth connection](#o) |-| [Connector](../webhooks-and-connectors/what-are-webhooks-and-connectors.md) | It lets users subscribe to receive notifications and messages from the web services. Connectors expose the HTTPS endpoint for the service to post messages to Teams channels, typically in the form of cards. <br> **See also**: [Webhook](#w) | +| [Connector](../webhooks-and-connectors/what-are-webhooks-and-connectors.md) | It lets users subscribe to receive notifications and messages from the web services. Connectors expose the HTTPS endpoint for the service to post messages to Teams channels, typically in the form of cards. <br> **See also**: [Webhook](#w); [Connectors Developer Dashboard](https://outlook.office.com/connectors/publish) | | [Connector ID](../resources/schem#include-the-connector-in-your-app-manifest) | | [Consent dialog](../tabs/how-to/authentication/tab-sso-code.md) | The process of a user granting authorization to an application to access protected resources on their behalf. An admin or user can be asked for consent to allow access to their organization or individual data. <br> **See also**: [SSO](#s); [Authentication flow](#a); [Administrator consent](#a); [User consent](#u) | | [Content URL](../resources/schem#statictabs)| An app manifest property (`contentUrl`) where the HTTPS URL points to the entity UI to be displayed in the Teams canvas. <br> **See also**: [App manifest](#a)| Common terms and definitions used in Microsoft Teams developer documentation. | Term | Definition | | | | |[Federated or external](../apps-in-teams-meetings/teams-apps-in-meetings.md#user-types-in-teams)|A federated or an external user is a Teams user from another organization who has been invited to join a meeting. Federated users have valid credentials with federated partners and are authorized by Teams. <br>**See also**: [Anonymous](#a); [In-tenant](#i); [Guest](#g) |-| [First-run Experience](../concepts/design/design-teams-app-ui-templates.md)|A First-run Experience (FRE) is a user's introduction to your product. The FRE helps users to get started with the functions, features, and benefits of the product and influences users to come back and continue using your product.| +| [First-run Experience](../concepts/design/design-teams-app-ui-templates.md)|A First-run Experience (FRE) is a user's introduction to your product. The FRE helps users to get started with the functions, features, and benefits of the product and influences users to come back and continue using your product such as tab or bot.| | [Fluent UI](../concepts/design/design-teams-app-basic-ui-components.md)| Design and build your Teams app from scratch with the basic Fluent UI components. These components can work across different use cases, themes, and screen sizes. <br>**See also**: [Fluent UI React Components](https://react.fluentui.dev/?path=/docs/concepts-introduction--page)| | [Fully qualified domain name (FQDN)](../tabs/how-to/authentication/tab-sso-register-aad.md) | A fully qualified domain name (FQDN) represents a domain name of a host or IP address(es). | Common terms and definitions used in Microsoft Teams developer documentation. | Term | Definition | | | |-| [Link unfurling](../messaging-extensions/how-to/link-unfurling.md) | A feature used with message extension and meeting to unfold links pasted into a compose message area. The links expand to show additional information about the link in Adaptive Cards or in the meeting Stage View. | -| [Link Share SDK](../apps-in-teams-meetings/teams-live-share-overview.md) | An SDK designed to transform Teams apps into collaborative multi-user experiences without writing any dedicated back-end code. With Live Share, your users can co-watch, co-create, and co-edit during meetings. | +| [Link unfurling](../messaging-extensions/how-to/link-unfurling.md) | A feature used with message extension and meeting to unfold links pasted into a compose message area. The links expand to show additional information about the link in Adaptive Cards or in the meeting Stage View. <br>**See also**: [Adaptive Card](../task-modules-and-cards/cards/cards-reference.md#adaptive-card); [Stage View](#s) | +| [Live Share SDK](../apps-in-teams-meetings/teams-live-share-overview.md) | An SDK designed to transform Teams apps into collaborative multi-user experiences without writing any dedicated back-end code. With Live Share, your users can co-watch, co-create, and co-edit during meetings. | | [Live Share canvas](../apps-in-teams-meetings/teams-live-share-canvas.md)| When collaborating in meetings, it's essential for users to be able to point out and emphasize content on the screen. Live Share canvas makes it easy to add inking, laser pointers, and cursors to your app for seamless collaboration. | | [Live share media](../apps-in-teams-meetings/teams-live-share-overview.md#live-share-media)| Live Share media enables media synchronization for any media player. By synchronizing media at the player state and transport controls layer, you can individually attribute views, when providing the highest possible quality available through your app.| | [Local environment](../toolkit/TeamsFx-multi-env.md#create-a-new-environment-manually-in-visual-studio-code) | A default development environment created by Teams Toolkit. <br>**See also**: [Environment](#e); [Dev environment](#d) | Common terms and definitions used in Microsoft Teams developer documentation. | [Rate-limiting](../bots/how-to/rate-limit.md) | A method to limit messages to a certain maximum frequency to ensure that number of messages are sufficient and don't appear as spam. | | [Redirect URL](../bots/how-to/authentication/bot-sso-register-aad.md) | A redirect URL is the location where the authorization server sends the user after the app has been successfully authorized and granted an authorization code or access token. It's also called or reply URL. | | [Role-based views](../task-modules-and-cards/cards/universal-actions-for-adaptive-cards/user-specific-views.md) | A feature of tabs where the tab experience may be different for users depending on their permission level. |-| [RSC permission](../graph-api/rsc/resource-specific-consent.md) | Resource-specific consent (RSC) permission feature is needed by team owners to let a bot app receive messages across channels in a team without being @mentioned. | +| [RSC permission](../graph-api/rsc/resource-specific-consent.md) | Resource-specific consent (RSC) permission feature is needed by team owners to let a bot app receive messages across channels in a team without being @mentioned. <br> For more information, see [Permissions](/graph/permissions-overview?tabs=http) | | [Real-time meeting protocol](../resources/schem#meetingextensiondefinition)| A Boolean value indicating whether this app can stream the meeting's audio and video content to a Real-time meeting protocol (RTMP) endpoint.| ## S Common terms and definitions used in Microsoft Teams developer documentation. | [SPFx](../sbs-gs-spfx.yml) | SharePoint Framework (SPFx) is a development model to build client-side solutions for Microsoft Teams and SharePoint. | | [SSO](../concepts/authentication/authentication.md) | Acronym for Single sign-on, an authentication method in which a user needs to sign in to an independent service of a software platform (such as Microsoft 365) only once. The user is then able to access all services without having to go through authentication again. <br>**See also**: [Authentication](#a); [Scope](#s) | | [Static tab](../concepts/design/personal-apps.md) | See [Personal tab](#p) |-| [Stage View](../sbs-meetings-stage-view.yml) | A user interface component that lets you render the content that is opened in full screen in Teams and pinned as a tab. It's invoked to surface web content within Teams. It *isn't* the same as meeting stage. <br>**See also**: [Meeting stage](#m); [Collaborative Stage View](#c) | +|[Stage View](../sbs-meetings-stage-view.yml)|A user interface component that lets you render the content that is opened in full screen in Teams and pinned as a tab. It's invoked to surface web content within Teams. It *isn't*the same as meeting stage. <br>**See also**: [Meeting stage](#m); [Collaborative Stage View](#c); [stageView](../m365-apps/teamsjs-support-m365.md#stageview)| | [Standalone app](../samples/integrating-web-apps.md) | A single-page or large, and complex app. The user can use some aspects of it in Teams. <br>**See also**: [Collaboration app](#c) | | Standalone bot | A type of bot app. It's a single bot app or not part of a larger application. <br> **See also**: [Chat bot](#c); [Conversational bot](#c) | | [Static search](../task-modules-and-cards/cards/dynamic-search.md) | A method of typeahead search that lets users search from pre-specified values in the Adaptive Cards payload. <br>**See also**: [Dynamic search](#d) | Common terms and definitions used in Microsoft Teams developer documentation. | [Token exchange URL](../bots/how-to/authentication/bot-sso-register-aad.md) | It's the application ID URI that is used for exchanging token. It's configured while configuring the OAuth connection for bot resource. <br> **See also**: [Application ID URI](#u); [SSO](#s) | | [TokenExchangeResource property](../bots/how-to/authentication/bot-sso-code.md) | It's a property of `OAuthCard` class that gets or sets the resource to try to perform token exchange with. Teams refreshes the token if the `TokenExchangeResource` property is populated on the card. <br> **See also**: [OAuth card](#o); [SSO](#s) <br> For more information, see [Microsoft Bot Schema 4.0](/dotnet/api/microsoft.bot.schema.oauthcard) | | [TeamsSSOTokenExchangeMiddleware](../bots/how-to/authentication/bot-sso-code.md) | This middleware exchanges the token if the activity name is `signin` or `tokenExchange`. It also ensures only one exchange request is processed. <br> **See also**: [SSO](#s) |+|[Transactable Teams SaaS offer](../resources/schem#subscriptionoffer) | Transactable Teams SaaS offer (T-SaaS) specifies the SaaS offer associated with your app. A unique identifier that includes your Publisher ID and Offer ID, which you can find in Partner Center. <br>**See also**: [SaaS](#s)| ## U |
| platform | Resource Specific Consent | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/graph-api/rsc/resource-specific-consent.md | Microsoft Graph SDK, Microsoft Bot Framework SDK, and Microsoft TeamsJS client l | RSC mode | Supported SDKs | App manifest version | Resource types | RSC-related controls for the entire tenant | Who can consent to RSC permissions? | |||||||-|Application| ΓÇó Microsoft Graph <br> ΓÇó Microsoft Bot Framework | >=v1.6 | Teams, chats, and meetings | ΓÇó Microsoft Graph-based controls for chats and meetings <br> ΓÇó Azure Active Directory (Azure AD) portal-based controls for Teams |ΓÇó Team: A team owner <br> ΓÇó Chat: A chat member <br> ΓÇó Meeting: A meeting organizer or presenter | +|Application| ΓÇó Microsoft Graph <br> ΓÇó Microsoft Bot Framework | >=v1.6 | Teams, chats, and meetings | ΓÇó Microsoft Graph-based controls for chats and meetings <br> ΓÇó Azure Active Directory (Azure AD) portal-based controls for Teams |ΓÇó Team: A team owner or member <br> ΓÇó Chat: A chat member <br> ΓÇó Meeting: A meeting organizer or presenter | | Delegated | Microsoft Teams Client | >=v1.12 | Teams, chats, meetings, and users | Always on | Any user authorized to install an app in the specific scope. | > [!NOTE] The following table provides RSC permissions for a user and their applicable dat * [App manifest schema for Teams](../../resources/schem) * [Permissions in Teams app](../App-permissions/Teams-app-permissions.md)+* [Manage custom apps in Teams admin center](/microsoftteams/teams-custom-app-policies-and-settings) +* [Allow members to upload custom apps](/microsoftteams/teams-custom-app-policies-and-settings?branch=main) |
| platform | Define Action Command | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/messaging-extensions/how-to/action-commands/define-action-command.md | To create an action command: 1. Select **Add a command** in the **Command** section to include the commands, which decides the behavior of message extension. - :::image type="content" source="../../../assets/images/tdp/add-a-command.PNG" alt-text="Screenshot shows how to add a command to define the behavior of the message extension."::: - 1. Select **Action** and then select parameter type. + :::image type="content" source="../../../assets/images/tdp/add-a-command-new.PNG" alt-text="Screenshot shows the action command and static parameters radio button selected in the Add a command page."::: + 1. Enter **Command ID**, **Command title**, and **Command description**. 1. Enter all the parameters and select the type of input from the dropdown list. |