Common terms and definitions used in Teams developer documentation.
|Action command||A type of message extension app that uses a pop-up to collect or display information.
See also: Message extension; Search commands
|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.|
|Anonymous user||A type of participant in a Teams meeting who doesn't have an Azure AD identity and isn't federated with a tenant. They are like external users in a meeting.
See also: Federated user
|App Catalog||A site that stores SharePoint and Office apps for an organization's internal use.
See also: SPFx
|App manifest||The Teams app manifest describes how the app integrates into the Microsoft Teams product. Your manifest must conform to the manifest schema.|
|App package||A Teams app package is a zip file that contains the App manifest file, color icon, and outline icon.|
|App permission||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.
See also: Device permissions
|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.|
|App Studio||An app to start creating or integrating your own Microsoft Teams apps. It has now evolved to Developer Portal.
> 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 is deprecated on August 01, 2022.
See also: Developer Portal
|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.
See also: Teams Mobile
|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.|
|Azure Active Directory||Microsoft’s cloud-based identity and access management service. It helps authenticated users access internal and external Azure resources.|
|Authentication||A process to validate user access for your app's usage. It can be done using Microsoft Graph APIs or web-based authentication.
See also: Identity providers; SSO
|Authentication flow||In Teams, there are two authentication flows to authenticate a user for using an app: web-based authentication and OAuthPrompt flow.|
|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 that executes programmed repetitive tasks.
See also: Conversational bot; Chat bot
|Bot Emulator||A desktop application that lets you test and debug bots, either locally or remotely.|
|Call bot||A bot that participates in audio or video calls and online meetings.
See also: Chat bot; Meeting bot
|Capability||A Teams feature you can build into your app for interacting with app users. An app capability is used to extend Teams to fit your app needs. An app may have one or more core capabilities, such as tab, bot, and message extension.
See also: Device capability; Media capability
|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
|Client secret||The Client secret/password or a public or private key pair that is Certificate. It isn't required for native apps.
See also: Bot
|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.|
|Collaboration app||An app with capabilities for a user to work in a collaborative workspace with other users.
See also: Standalone app
|Compose Extension||A property in app manifest (
See also: App manifest; Message extension
|Command box||A type of context in app manifest (
|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
|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 task modules.
See also Chat bot
|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.|
|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
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
|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
|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
|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
|Federated user||A type of user in a Teams app meeting who is external and is invited to the meeting. This user has valid credentials that are federated by authorized Teams partners. They're also called External users.
See also: Anonymous user
|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
|Identity provider||An entity that stores and provides credentials to the user. Users can register themselves with an identity provider as well.
See also: Authentication
|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
|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 stage view.|
|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 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 currently available only for Teams mobile clients only.
See also: Capability; Media capability; Device Capability; Teams Mobile
|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.|
|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: Stage view
|Message extension||Message extensions 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 that is designed to be used during the meeting lifecycle to make it more productive, such as whiteboard, dashboard, and more.|
|Microsoft 365 account||Microsoft 365 account includes 25 user licenses, including the administrator, for development purposes only.|
|Microsoft 365 developer program||The Microsoft 365 Developer Program helps you build apps that extend Microsoft 365.|
|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 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 Teams UI Library||Microsoft Teams UI Library helps you view and test individual Teams UI templates and related components in your browser.|
|Microsoft Teams UI Toolkit||Microsoft Teams UI Kit includes components and patterns that are designed specifically for building Teams apps.|
|Office 365 Connector||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 Office 365 Connector cards and have the ability to add a limited set of card actions to them.|
|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
|Outlook channel||A feature of Teams message extension app that lets the users interact with it from Microsoft Outlook.|
|One-on-one chat||A type of chat between a Teams personal bot app and a single user.
See also: Group chat; Chat bot
|People Picker||A native control in Teams platform to search and select people, which can be integrated in web apps, Adaptive Cards, and more.|
|Personal app||A personal app 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
|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.|
|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.|
See also: Deploy
|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.|
|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.|
|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 app
|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
|Sideloading||A process where a Teams app is loaded to the Teams client to test it in the Teams environment before distributing it.|
|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.|
|SPFx||SharePoint Framework (SPFx) is a development model to build client-side solutions for Microsoft Teams 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
|Stage view||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. Note that it is not the same as meeting stage.
See also: Meeting stage
|Standalone app||A single-page or large, and complex app. The user can use some aspects of it in Teams.
See also: Collaboration aap
|Static search||A method of typeahead search that lets users search from pre-specified values in the Adaptive Cards payload.
See also: Dynamic search
|Store validation guidelines||A set of Teams-specific guidelines for validating an app before it can be submitted to Teams store.
See also: Teams store
|Tab||Tabs are Teams-aware webpages embedded in Microsoft Teams that point to domains declared in manifest. You can add it inside a team, group chat, or personal app.|
|Tab chat||A type of tab that lets a user have a focused conversation experience in dynamic tabs.|
|Task modules||A feature of Teams app to create modal pop-up for completing tasks, displaying videos, or dashboard.|
|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 Toolkit||The Microsoft Teams Toolkit enables you to create custom Teams apps directly within the Visual Studio Code environment.|
|TeamsFx||TeamsFx is a text-based command line interface that accelerates Teams application development. It's also called TeamsFx CLI.|
|TeamsFx SDK||TeamsFx SDK is pre-configured in scaffolded project using TeamsFx toolkit or CLI.|
|TeamsJS SDK||TeamsJS SDK enables you to create hosted experiences in Teams. Starting with TeamsJS v.2.0.0, you can extend Teams apps to run in Outlook and Office.|
|Teams Mobile||Microsoft Teams available as a mobile app.|
|Teams store||A 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 Store validation guidelines and obtain an approval before it's available to users via the Teams store.
See also: Store validation guidelines
|Teams workbench||A workbench in Visual Studio Code used at build for Teams apps created using SPFx and Teams Toolkit.
See also: Workbench; Local workbench
|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.|
|Virtual Assistant||A Microsoft open-source template that enables you to create a robust conversational solution.|
|Website url||A property in the app manifest file (
See also: App manifest; Teams Mobile
|Web app||An app that runs on a web server. It can be integrated with Microsoft Teams Platform.|
|Webhook||It is a feature of a Teams app used to integrate it with external apps.
See also: Incoming webhook; outgoing webhook
|Web part||A UI component used to build a page or a site in a Teams app created using Visual Studio Code and SharePoint Framework.
See also: SPFx
|Workbench||Overall Visual Studio Code UI that encompasses UI components, such as title bar, panel, and more.
See also: Local workbench; Teams workbench
|YoTeams||A development toolkit for building Microsoft Teams applications based on TypeScript and node.js.|
Submit and view feedback for