Glossary
Common terms and definitions used in Microsoft Teams developer documentation.
A
| Term | Definition |
|---|---|
| Action command | A type of message extension app that uses a pop-up to collect or display information. See also: Message extension; Search commands |
| Access token | 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. See also: Identity token For more information, see Access token, Authentication |
| Adaptive Cards | 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. See also: Dialog; Adaptive Card Schema Explorer |
| Administrator consent | An administrator can grant consent for the application on behalf of all users in the organization. It helps avoid the need for user consent. SSO; Consent dialog; User consent |
| AI label | An AI label in an AI bot message indicates that the content was generated using AI and reminds the user that the content they are interacting with was not created by a human, but by an AI system. See also: Citation; Sensitivity label |
| Anonymous | Anonymous users don't have a Microsoft Entra 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. See also: Federated or external; In-tenant; Guest |
| App Catalog | A site that stores SharePoint and Office apps for an organization's internal use. See also: SPFx |
| App Caching | 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 | 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. |
| App package | An app package is a zip file that contains the app manifest file, color icon, and outline icon. |
| Application permission | 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 | 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. See also: Default install scope |
| App tray | An application tray located on the bottom bar of a Teams mobile app. It collects all apps that are open but not in use or active. See also: Teams Mobile |
| Application ID | The application ID, or client ID, is a value the Microsoft identity platform assigns to your application when you register it in Microsoft Entra ID. The application ID is a GUID value that uniquely identifies the application and its configuration within the identity platform. See also: GUID; Client ID; Application ID URI; Subdomain ID |
| Application ID URI | 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. See also: Token exchange URL; Configure your bot or message extension app in Microsoft Entra ID |
| Authentication | The process to validate a user's identity to access your app. See also: Identity providers; SSO; authentication |
| Authentication flow | The way a user is authenticated to use your app. For Teams apps, we recommend using Single Sign-on (SSO) using Microsoft Entra ID; but an alternative is to use a third-party IdP. See also: SSO; Identity provider |
| Authorization | An app manifest property (authorization) that specifies and consolidates authorization related information for the app. See also: Permission |
| Azure resource | 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
| Term | Definition |
|---|---|
| Blazor | A free and open-source web framework that enables developers to create web apps using C# and HTML. It's being developed by Microsoft. |
| Bicep | A declarative language, which means the elements can appear in any order. Unlike imperative languages, the order of elements doesn't affect how deployment is processed. |
| Bot | A bot is an app or service that executes programmed repetitive tasks. See also: Conversational bot; Chat bot |
| Bot Builder SDK | It's an open-source SDK hosted on GitHub to help build dialogs within your Node.js- or C#-based bot. |
| Bot Emulator | A desktop application that lets you test and debug bots, either locally or remotely. |
| Bot Framework | A rich SDK used to create bots using C#, Java, Python, and JavaScript. If you have a bot that is based on the Bot Framework, you can modify it to work in Teams. Bot Framework Token Service; Bot Framework Schema |
| Bot handle | A bot handle is a unique identifier for your bot. A bot handle represents a bot's registration with the online Azure Bot Service. This registration is associated with an HTTP webhook endpoint and registration with channels. See also: SSO; Bot resource; Microsoft Entra ID |
| Bot Framework Schemas | Bot Framework Schemas are specifications for JSON data. They define the shape of the data and can be used to validate JSON. See also: Bot Framework |
| Bot Framework Token Service | It's a feature of Bot Framework that facilitates a bot app to use the OAuth protocol for acquiring and storing access token. See also: Bot Framework; SSO; Access token; Identity token For more information, see Bot Framework Token Service |
| Bot ID | A unique identifier of your bot app that is generated at the time you register your app in Microsoft Entra ID. See also: Bot handle |
| Bot resource | The Azure Bot resource (bot resource) allows you to register your bot with Azure Bot Services and to connect your bot to channels. See also: SSO; Microsoft Entra ID |
C
| Term | Definition |
|---|---|
| Call bot | A bot that participates in audio or video calls and online meetings. See also: Chat bot; Meeting bot; Real-time media calls and meetings |
| Capabilities | 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. See also: App scope |
| Chat bot | 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. See also: Conversational bot |
| Channel | A single place for a team to share messages, tools, and files. You can use a channel for teamwork and communication. See also: Conversation |
| Citation | A citation in a bot message is a reference to the source of information used in the message, such as web results. The citation typically includes the title of the source, the URL, and sometimes a brief snippet of the information from the source. See also: Sensitivity label; AI label |
| Contoso | Contoso Ltd. (also known as Contoso and Contoso University) is a fictional company used by Microsoft as an example company and domain. |
| 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 Microsoft Entra ID. It's a GUID value that uniquely identifies the application and its configuration within the identity platform. See also: Application ID; GUID; Subdomain ID |
| Client secret | A secret string that an app uses to prove its identity when requesting a token. Also, it can be referred to as application password. See also: Microsoft app password For more information, see Authentication |
| Cloud resources | 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 | 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. See also: App manifest |
| Configuration URL | An app manifest property (configurationUrl) where the HTTPS URL to use when configuring the tab or connector. See also: App manifest |
| Collaboration app | An app with capabilities for a user to work in a collaborative workspace with other users. See also: Standalone app |
| Collaborative Stageview | Collaborative Stageview is an enhancement to Stageview that allows users to engage with your app content in a new Teams window accompanied by a side panel conversation. See also: Stageview |
| Compose Extensions | 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. See also: App manifest; Message extension |
| Command Box | A type of context in app manifest (commandBox) that you can configure to invoke a message extension from Teams command box. See also: Message extension |
| Command lists | 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. See also: App manifest |
| Connection name | The name of OAuth connection that you configure for enabling SSO connection for your bot resource. See also: OAuth connection |
| Connector | 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. See also: Webhook; Connectors Developer Dashboard |
| Connector for Microsoft 365 Groups | It lets you create a custom configuration page for your Incoming Webhook and package them as part of a Teams app. You can send messages primarily using connector cards for Microsoft 365 Groups and can add a limited set of card actions to them. See also: Graph connector |
| Connector ID | A unique identifier for the Connector that matches its ID in the Connectors Developer Dashboard. For more information, see Include the connector in your manifest |
| Consent dialog | 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. See also: SSO; Authentication flow; Administrator consent; User consent |
| Content URL | An app manifest property (contentUrl) where the HTTPS URL points to the entity UI to be displayed in the Teams canvas. See also: App manifest |
| Conversation | A series of messages sent between your Microsoft Teams app (tab or bot) and one or more users. A conversation can have three scopes: channel, personal, and group chat. See also: One-on-one chat; Group chat; Channel |
| Conversational bot | It lets a user interact with your web service using text, interactive cards, and dialogs. See also Chat bot; Standalone app |
| Copilot | Microsoft 365 Copilot is powered by an advanced processing and orchestration engine that seamlessly integrates Microsoft 365 apps, Microsoft Graph, and Large Language Models (LLMs) to turn your words into the most powerful productivity tool. |
| Copilot handoff | Copilot handoffs are plugin-provided deep links that carry over chat context, enabling users to seamlessly transition their chat with Microsoft 365 Copilot to your bot service. |
| Custom engine agent | Custom engine agents are conversational Teams bots designed to harness the powerful capabilities of Large Language Models (LLMs) for seamless user interaction. These advanced bots mark a significant departure from traditional bots, offering an extensive range of features that elevate the overall user experience. |
| Customer-owned apps | An app created by you or your organization that is meant for use by other Teams app users outside the organization. It can be made available on Microsoft Teams Store. See also: Teams Store validation guidelines; Microsoft Store; LOB apps; Personal tab; Shared apps |
| Custom app built for your org (LOB app) | An app created only for Teams by you or your organization. |
| Custom app upload | A process where a Teams app is loaded to the Teams client to test it in the Teams environment before distributing it. |
| Custom Together Mode | Custom Together Mode scenes in Teams provide an immersive and engaging meeting environment. See also: Developer Portal for Teams |
D
| Term | Definition |
|---|---|
| Deep linking | In a Teams app, you can create deep links to information and features within Teams or to help the user navigate to content in your app. |
| Default install scope | An app manifest property (defaultInstallScope) that specifies the install scope defined for the app by default. See also: App manifest; App scope |
| Delegated permission | They're used by apps that have a signed-in user present. For these apps, either the user or an administrator consents to the permissions that the app requests and the app can act as the signed-in user when making calls to Microsoft Graph. See also: SSO; Permission; Scope |
| Department of Defense (DoD) | DoD environments deliver compliance with Department of Defense Security Requirements Guidelines, Defense Federal Acquisition Regulations Supplement (DFARS), and International Traffic in Arms Regulations (ITAR). |
| Developer Portal for Teams | The primary tool for configuring, distributing, and managing your Microsoft Teams apps. With Developer Portal, you can collaborate with colleagues on your app, set up runtime environments, and much more. |
| Developer Preview | A public program for developers that provides early access to unreleased features in Microsoft Teams. It lets you explore and test upcoming features for potential inclusion in your Microsoft Teams app. |
| Deploy | A process to upload the backend and frontend code for the application. At Deployment, the code for your app is copied to the resources you created during provisioning. See also: Provision |
| Device capabilities | Built-in devices, such as camera, microphone, barcode scanner, photo gallery, in a mobile or desktop. You can access the following device capabilities on mobile or desktop through dedicated APIs available in the Microsoft Teams JavaScript client library (TeamsJS). See also: Capability; Media capability; Location capability |
| Device permission | A Teams app setting that you can configure in your app. You use it to request permission for your app to access and utilize a native device capability. You can manage device permissions in Teams settings. See also: App permissions |
| Dev environment | A type of development environment that Teams Toolkit creates by default. It represents remote or cloud environment configurations. A project can have multiple remote environments. You can add more dev environments to your project using Teams Toolkit. See also Environment; Local environment |
| Dev Tools | Browser's Dev Tools are used to view console logs, view or modify runtime network requests, add breakpoints to code (JavaScript) and perform interactive debugging for a Teams app. |
| Dialogs (referred as task modules in TeamsJS v1.x) | A feature of Teams app to create modal pop-up for completing tasks, displaying videos, or dashboard. See also: Adaptive Card, Task modules |
| Dynamic search | A search feature for Adaptive Cards that is useful to search and select data from large data sets. It helps to filter out the choices as the user enters the search string. See also: Static search |
E
| Term | Definition |
|---|---|
| E5 developer account | E5 developer subscription for building apps to extend Microsoft 365. It includes 25 user licenses, including the administrator, for development purposes only. See also: Microsoft 365 account |
| Endpoint address | It's used in Developer Portal to configure SSO for a bot app. It's the endpoint where messages are sent to your bot. See also: Bot handle; Messaging endpoint; OAuth connection; SSO |
| Entry point | An access point, such as team, channel, and chat, for a Teams app where users can use your app. |
| Environment | A feature in Teams Toolkit that lets you create and use multiple development environments for your app project. There are two dev environments that Teams Toolkit creates by default, local environment and dev environment. See also: Local environment; Dev environment |
F
| Term | Definition |
|---|---|
| Federated or external | 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. See also: Anonymous; In-tenant; Guest |
| First-run Experience | 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 | 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. See also: Fluent UI React Components |
| Fully qualified domain name (FQDN) | A fully qualified domain name (FQDN) represents a domain name of a host or IP address(es). |
G
| Term | Definition |
|---|---|
| Geo-filtering | A Teams feature where you can cater your app to a specific audience from the available list of countries or regions and communicate what’s great about your app in ways that are relevant to users. |
| Government community cloud (GCC) | GCC environment provides compliance with federal requirements for cloud services. It includes FedRAMP High, Defense Federal Acquisition Regulations Supplement (DFARS), and requirements for criminal justice and federal tax information systems (CJI and FTI data types). |
| Government community cloud (GCC) High | GCC high environments deliver compliance with Department of Defense (DoD) Security Requirements Guidelines, Defense Federal Acquisition Regulations Supplement (DFARS), and International Traffic in Arms Regulations (ITAR). See also: Department of Defense (DoD) |
| Graph API | A RESTful web API for Microsoft Graph that enables you to access Microsoft Cloud service resources. See also: Microsoft Graph Explorer |
| Group chat | A chat feature where a user is able to chat with a bot in a group setting by using @mention to invoke the bot. See also: One-on-one chat; Chat bot |
| GUID | GUID is a specific-format identifier such as application ID or client ID. Microsoft identity platform assigns GUID to your app when you register in Microsoft Entra ID and helps to uniquely identify your app and the configuration within the identity platform. See also: Application ID |
| Guest | A guest is a participant from another organization invited to access Teams or other resources in the organization's tenant. Guests are added to the organization’s Microsoft Entra ID and have same Teams capabilities as a native team member. They have access to team chats, meetings, and files. A guest can be an organizer, presenter, or attendee. See also: Anonymous; In-tenant; Federated or external |
I
| Term | Definition |
|---|---|
| Identity provider | Identity provide (IDP) is an entity that stores and provides credentials to the user. It also allows users to register themselves. See also: Authentication |
| Identity token | An identity token is used for authenticating app users. It's used by an application to verify if the app user is as per the declared identity. See also: Access token For more information, see ID tokens. |
| Incoming Webhook | It lets an external app share content in Teams channels. These webhooks are used as tracking and notifying tools. See also: Webhook; Outgoing Webhook |
| In-meeting app experience | A stage of Teams meeting lifecycle. With the in-meeting app experience, you can engage participants during the meeting by using apps and the in-meeting dialog box. See also: Meeting lifecycle |
| In-tenant | In-tenant users belong to the organization and have credentials in Microsoft Entra ID for the tenant. They're full-time, onsite, or remote employees and can be an organizer, presenter, or attendee. See also: Anonymous; Federated or external; Guest |
L
| Term | Definition |
|---|---|
| Link unfurling | 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 Stageview. See also: Adaptive Card; Stageview |
| Live Share SDK | 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 | 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 | 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 | A default development environment created by Teams Toolkit. See also: Environment; Dev environment |
| Local workbench | The default option to run and debug a Teams app in Visual Studio Code (VS Code) that is created using SPFx. See also: Workbench; Teams workbench |
| Location capability | A device capability that you can integrate with your app to know the geographical location of the app user for an enhanced collaborative experience. This feature is available only for Teams mobile clients only. See also: Capability; Media capability; Device Capability; Teams Mobile |
| Long description | The long description can provide a narrative that highlights your apps main features, the problems it solves, and target audience. See also: Short description |
| Low code apps | A custom Teams app built from scratch using Microsoft Power Platform that requires little or no coding and can be developed and deployed quickly. |
M
| Term | Definition |
|---|---|
| Media capability | Native device capabilities, such as, camera and microphone, that you can integrate with your Teams app. See also: Capability; Device capability |
| Meeting bot | Bots that interact with Teams calls and meetings using real-time voice, video, and screen sharing. See also: Call bot; Chat bot |
| Meeting lifecycle | It spans from pre-meeting, in-meeting, and post-meeting app experience. You can integrate tabs, bots, and message extensions in each stage of the meeting lifecycle. See also: In-meeting experience |
| Meeting stage | A feature of meeting extension app. It's a shared space accessible to all participants during the meeting. It helps participants interact and collaborate with app content in real time. See also: Stageview |
| Messaging endpoint | It's the endpoint where messages are sent to your bot. See also: Endpoint address; Bot handle; OAuth connection; SSO |
| Message extension | Message extensions (previously called composeExtensions) are shortcuts for inserting app content or acting on a message. You can use a message extension without navigating away from the conversation. See also: Search commands; Action commands |
| Meeting extension | An app designed to be used during the meeting lifecycle to make it more productive, such as whiteboard, dashboard, and more. |
| Meeting surfaces | The set of meetingSurfaceItem scopes where a tab is supported. See also: Configurable tab |
| Microsoft 365 account | Microsoft 365 account includes 25 user licenses, including the administrator, for development purposes only. |
| Microsoft 365 client ID | See Client ID |
| Add Microsoft 365 channel for your bot | A feature of Teams message extension app that lets the users interact with it from Microsoft 365. |
| Microsoft 365 developer program | The Microsoft 365 Developer Program helps you build apps that extend Microsoft 365. |
| Microsoft App Password | A secret string that the application uses to prove its identity when requesting a token. Also, it can be referred to as application password. See also: Client secret |
| Microsoft Graph Explorer | The gateway to data and intelligence in Microsoft 365. It provides a unified programmability model that you can use to access data in Microsoft 365, Windows 10, and Enterprise Mobility + Security. |
| Microsoft Partner Center | Microsoft Partner Center streamlines several business processes to make it easier for Microsoft partners to manage their relationship with Microsoft and their customers. Partner Center gives you access to the tools you need to get work done. |
| Microsoft Cloud Partner Program ID | The Microsoft Cloud Partner Program ID (CCP ID) that identifies the partner organization building the app. You can find your CCP ID by fetching the Partner Center ID. |
| Microsoft Teams | Microsoft Teams is a group collaboration software that can be used to help teams work together remotely. |
| Microsoft Teams Platform | The Microsoft Teams developer platform makes it easy for developers to integrate their own apps and services with Teams. |
| Microsoft Store | It's a digital distribution platform operated by Microsoft. it's also known as Windows Store. See also: Teams Store |
| Monetization | Teams Store provides features that enable you to monetize your apps and gain customers by engaging with your users. See also: SaaS |
| Multitenant app | A class of applications that enables sign-in and consent by users provisioned in any Microsoft Entra tenant, including tenants other than the one where the client app is registered. See also: Single-tenant apps |
N
| Term | Definition |
|---|---|
| Notification only Bot | Microsoft Teams Toolkit enables you to build applications that capture events and send them as notifications to a personal, group chat, or a channel in Teams. By design, if your bot doesn't respond or support any user command and is a one way bot only intended to notify users. You must set isNotificationOnly to true in the app manifest. See also: Teams Toolkit |
O
| Term | Definition |
|---|---|
| OAuth card | A card used by an app to represent a request to perform a sign-in via OAuth. See also: SSO; TokenExchangeResource property |
| OAuth connection | It's configured as a part of bot resource configuration for SSO authentication after its registered on Microsoft Entra ID. It contains details about the identity provider, client secret, and so on. See also: SSO; Connection name; Identity provider; Client secret; Microsoft Entra ID |
| Object ID | The unique identifier created by Microsoft Entra admin center when you register or update your app. It identifies the application object, which defines the application's identity configuration globally (across all tenants where it has access). See also: Application ID; Tenant ID; SSO |
| Outgoing Webhook | It acts as a bot and search for messages in channels using @mention. It sends notifications to external web services and responds with rich messages, which include cards and images. See also: Webhook; Incoming Webhook |
| One-on-one chat | A type of chat between a Teams personal bot app and a single user. See also: Group chat; Chat bot |
P
| Term | Definition |
|---|---|
| People picker | A native control in Teams platform to search and select people, which can be integrated in web apps, Adaptive Cards, and more. |
| People icon | People icon helps users to view the images of users in an Adaptive Card. |
| Permission | While authentication and providing access token for app user, a client application gains access to a resource server by declaring permission requests. Two types are available, Delegated permissions and Application permissions. See also: Scope; SSO; Authentication flow; Authorization |
| Personal tab | A personal tab is also known as static tab. A personal (static) tab is a Teams application with a personal scope. It focuses on interactions with a single user. It can be a conversational bot to engage in one-to-one conversations with a user or a personal tab providing an embedded web experience, or both. See also: Shared app; Static tab |
| Policy | The privacy policy can be specific to your Teams app or an overall policy for all your services. |
| Power Virtual Agents | A no-code, guided graphical interface solution that empowers every member of your team to create rich, conversational chat bots that easily integrate with the Teams platform. |
| Privacy URL | A property in the app manifest file (privacyUrl). The HTTPS URL to the page that provides privacy information for the app. |
| Proactive messages | A message sent by a bot that isn't in response to a request from a user, such as welcome messages, notifications, scheduled messages. |
| Provision | A process that creates resources in Azure and Microsoft 365 for your app, but no code (HTML, CSS, JavaScript, etc.) is copied to the resources. It's a prerequisite to deployment. See also: Deploy |
| Publisher docs URL | The value of the publisherDocsUrl parameter is a secure HTTPS URL to the app documentation and information page that app developers choose to provide. Tenant admins get documentation about the app at this URL. Teams admin center displays the URL in the app details page. |
R
| Term | Definition |
|---|---|
| Rate-limiting | 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 | 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 | A feature of tabs where the tab experience may be different for users depending on their permission level. |
| RSC permission | 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. For more information, see Permissions |
| Real-time meeting protocol | 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
| Term | Definition |
|---|---|
| SaaS | You can monetize your Teams app by selling subscription plans directly from your Teams Store listing with a transactable Software-as-a-Service (SaaS) offer. See also: Monetization |
| Scene | You can build a scene using the scene studio. |
| Scope | Scopes are used to implement scope-based access control, for a client application that has been given delegated access to the resource by its owner. They're resource-defined strings. For example, Mail.Read, Directory.ReadWrite.All; managed in the Azure portal. See also: SSO; Authentication flow; Delegated permission; Permission |
| Search commands | A type of message extension app that lets users search external systems and include the search result into a message using a card. See also: Message extensions; Action commands |
| Sequential workflow | A workflow that lets a bot carry out a conversation with a user based on the user response. |
| Shared app | An app that exists in a team, channel, or chat where users can collaborate and interact. See also: Personal tab |
| SharePoint site collection | A collection site for SharePoint apps. You need to have an administrator account for this site before you can deploy your SPFx-based app on the SharePoint site. See also: SPFx |
| Short description | A concise summary of your app that must be original, engaging, and directed at your target audience. See also: Long description |
| SidePanel | A feature of Teams meeting app that enables you to customize experiences in a meeting that allow organizers and presenters to have different set of views and actions. |
| Single-tenant app | Single-tenant apps are only available in the tenant they were registered in, also known as their home tenant. See also: Multitenant apps |
| SPFx | SharePoint Framework (SPFx) is a development model to build client-side solutions for Microsoft Teams, Office Add-ins, and SharePoint. |
| SSO | 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. See also: Authentication; Scope |
| Static tab | See Personal tab |
| Stageview | 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. See also: Meeting stage; Collaborative Stageview; stageView |
| Standalone app | An app that can be added to Teams to customize chats and channels by adding bots, tabs, message extensions, or connectors. Anyone can install standalone apps for personal use, and based on permissions, admins and members can install them in channels for collaboration. Standalone apps can be extended to Outlook and Microsoft 365, and built by you through integrated development environments (IDEs) like Visual Studio or Visual Studio Code. Microsoft also provides standalone apps such as Planner, Word, or Outlook. See also: Collaboration app |
| Static search | A method of typeahead search that lets users search from pre-specified values in the Adaptive Cards payload. See also: Dynamic search |
| Teams Store validation guidelines | A set of standards and principles for validating an app before submitting the app to Teams store. The guidelines are applicable for apps that work across Teams, Outlook, and Microsoft 365. See also: Teams store |
| Subdomain ID | It's the application ID URI that you register when configuring scope for your app in Microsoft Entra ID. See also: SSO; Application ID URI; Application ID |
| Subscription offer | This 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. See also: SaaS |
| Sensitivity label | A sensitivity label in a bot message enables the user to understand the confidentiality of the bot's message. For an AI bot, this label is essential for maintaining transparency and accountability in AI usage. See also: AI label; Citation |
T
| Term | Definition |
|---|---|
| Tab | Tabs are client-aware webpages embedded in Microsoft Teams, Outlook, and Microsoft 365 that point to domains declared in app manifest. You can add it as part of a channel inside a team, group chat, or personal app for an individual user. |
| Tab chat | A type of tab that lets a user have a focused conversation experience in dynamic tabs. |
| Task modules (referred as dialogs in TeamsJS v2.x) | A feature of Teams app to create modal pop-up for completing tasks, displaying videos, or dashboard. See also: Adaptive Card, Dialogs |
| Task info | The TaskInfo object contains the metadata for a dialogs (referred as task modules in TeamsJS v.1.0). |
| Thread discussion | A conversation posted on a channel or chat between users. See also Conversation; Channel |
| Teams | Microsoft Teams is the ultimate message app for your organization. It's a workspace for real-time collaboration and communication, meetings, file and app sharing. |
| Teams AI library | A Teams-centric interface to GPT-based common language models and user intent engines. You can take on complex and expensive tasks of writing and maintaining conversational bot logic to integrate with Large Language Models (LLMs). |
| Teams identity | The Microsoft account or Microsoft 365 account of an app user that is used to log in to Teams client, web, or mobile app. |
| Teams identity | The Microsoft account or Microsoft 365 account of an app user that is used to sign in to Teams client, web, or mobile app. |
| Teams Toolkit | The Microsoft Teams Toolkit enables you to create custom Teams apps directly within the VS Code environment. |
| Teams Toolkit CLI | Teams Toolkit CLI is a text-based command line interface that accelerates Teams application development. It's also called Teamsapp CLI. |
| TeamsFx SDK | TeamsFx SDK is pre-configured in a scaffolded project using TeamsFx toolkit or CLI. |
| TeamsJS library | The TeamsJS library enables you to create hosted experiences in supported clients including Teams, Outlook, and Microsoft 365. (Note: When using TeamsJS v.1.x, hosted experiences are for Teams client only.) |
| Teams Mobile | Microsoft Teams available as a mobile app. |
| Microsoft Teams Store | A Teams Store landing page that brings apps to users in a single place. The apps are categorized by usage, industry, and more. An app must follow Teams Store validation guidelines and obtain an approval before it's available to users via the Teams Store. See also: Teams Store validation guidelines; Microsoft Store |
| Teams workbench | A workbench in VS Code used at build for Teams apps created using SPFx and Teams Toolkit. See also: Workbench; Local workbench |
| Tenant ID | The unique identifier of the tenant where your app is registered in Microsoft Entra admin center. Your app may be classified as a single-tenant or a multitenant app. See also: Single-tenant app; Multitenant apps |
| Terms of use | These terms of use govern your access to and use of Azure Marketplace, AppSource, and any Microsoft owned or operated online storefronts that point to offers cataloged by Azure Marketplace or AppSource. Your offer listing must include a valid Terms of use link. Offers with invalid, unsecured, and broken Terms of use links fail app review. |
| Token exchange URL | It's the application ID URI that is used for exchanging token. It's configured while configuring the OAuth connection for bot resource. See also: Application ID URI; SSO |
| TokenExchangeResource property | 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. See also: OAuth card; SSO For more information, see Microsoft Bot Schema 4.0 |
| TeamsSSOTokenExchangeMiddleware | This middleware exchanges the token if the activity name is signin or tokenExchange. It also ensures only one exchange request is processed. See also: SSO |
| Transactable Teams SaaS offer | 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. See also: SaaS |
U
| Term | Definition |
|---|---|
| UI components | For Teams app development, you can use Fluent UI components to build your app from scratch. |
| UI templates | For Teams app development, you can use Teams UI templates to design your apps quickly. |
| Universal Actions for Adaptive Cards | A way to implement Adaptive Cards across platforms and applications. It uses a bot as a common backend for handling actions. |
| User consent | A user can authorize an app to access some data at the protected resource, while acting as that user. See also: Consent dialog; Administrator consent; User consent; Delegated permission; Configure your app in Microsoft Entra ID. |
V
| Term | Definition |
|---|---|
| Valid domains | A property in the app manifest file (validDomains). A list of valid domains for websites the app expects to load within the supported clients. |
| Virtual assistant | A Microsoft open-source template that enables you to create a robust conversational solution. |
W
| Term | Definition |
|---|---|
| Website URL | A property in the app manifest file (websiteUrl) that links the app to the website of the organization or landing page of the relevant product. See also: App manifest; Teams Mobile |
| Web app | An app that runs on a web server that can be integrated with Microsoft 365 applications such as Microsoft Teams, Office, and SharePoint. |
| Webhook | It's a feature of a Teams app used to integrate it with external apps. See also: Incoming Webhook ; Outgoing Webhook; Connector |
| Web application info | Provide your Microsoft Entra App ID and Microsoft Graph information to help users seamlessly sign into your app. If your app is registered in Microsoft Entra ID, you must provide the App ID. If your app requires admins to review permissions and grant consent in Teams admin center, you must declare webapplicationinfo in the manifest. |
| Web part | A UI component used to build a page or a site in a Teams app created using VS Code and SharePoint Framework. See also: SPFx |
| Webview | A webview is a control that displays web content inside an application. |
| Workbench | Overall VS Code UI that encompasses UI components, such as title bar, panel, and more. See also: Local workbench; Teams workbench |
Y
| Term | Definition |
|---|---|
| Yeoman generator for Teams | Yeoman generator for Teams or YoTeams allows you to create Teams apps using TypeScript and JavaScript on your terms, in your preferred editor, and without any external or online dependencies. |
Samarbeta med oss på GitHub
Källan för det här innehållet finns på GitHub, där du även kan skapa och granska ärenden och pull-begäranden. Se vår deltagarguide för mer information.
Platform Docs