| 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 Teams developer documentation. | [App manifest](../resources/schem) | The Teams app manifest describes how the app integrates into the Microsoft Teams product. Your manifest must conform to the [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. | | [App 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) |-| [App scope](../concepts/design/app-structure.md) | 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 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. | | 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) | | [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. | | [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. | Common terms and definitions used in Teams developer documentation. | [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. | | [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) | | [Compose Extension](../resources/schem#composeextensions) | A property in app manifest (`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. | +| [CommandBox](../resources/schem) | A type of context in app manifest (`commandBox`) that you can configure to invoke a message extension from Teams command box. | | [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) | | 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. <br>**See also**: [One-on-one chat](#o); [Group chat](#g); [Channel](#c) | | [Conversational bot](../bots/how-to/conversations/conversation-messages.md) | It lets a user interact with your web service using text, interactive cards, and task modules. <br>**See also** [Chat bot](#c) | Common terms and definitions used in Teams developer documentation. | Term | Definition | | | |+| [Identity provider](../concepts/authentication/authentication.md) | An entity which stores and provides credentials to the user. It also allows users to register themselves. <br>**See also**: [Authentication](#a) | | [Incoming Webhook](../webhooks-and-connectors/how-to/add-incoming-webhook.md) | It lets an external app share content in Teams channels. These webhooks are used as tracking and notifying tools. <br>**See also**: [Webhook](#w); [Outgoing Webhook](#o) | | [In-meeting app experience](../apps-in-teams-meetings/meeting-app-extensibility.md#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. <br>**See also**: [Meeting lifecycle](#m) | Common terms and definitions used in Teams developer documentation. | [Message extension](../messaging-extensions/what-are-messaging-extensions.md) | 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. <br>**See also**: [Search commands](#s); [Action commands](#a) | | [Meeting extension](../apps-in-teams-meetings/design/designing-apps-in-meetings.md) | 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](../toolkit/accounts.md#microsoft-365-developer-account-types) | Microsoft 365 account includes 25 user licenses, including the administrator, for development purposes only. |-| [Microsoft 365 developer program](../toolkit/accounts.md)| The Microsoft 365 Developer Program helps you build apps that extend Microsoft 365. | +| [Microsoft 365 developer program](../toolkit/tools-prerequisites.md)| The Microsoft 365 Developer Program helps you build apps that extend Microsoft 365. | | [Microsoft Graph Explorer](../graph-api/proactive-bots-and-messages/graph-proactive-bots-and-messages.md) | 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](../overview.md) | Microsoft Teams is a group collaboration software that can be used to help teams work together remotely. | | [Microsoft Teams Platform](../concepts/app-fundamentals-overview.md) | The Microsoft Teams developer platform makes it easy for developers to integrate their own apps and services with Teams. | |
| platform | Manifest Schema Dev Preview | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/resources/schema/manifest-schema-dev-preview.md | The Microsoft Teams manifest describes how the app integrates into the Microsoft "scopes": [ "team", "groupchat"- ]"context": [] + ], + "context": [] } ], "staticTabs": [ |
| platform | Integrate Web Apps Overview | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/samples/integrate-web-apps-overview.md | With Power Apps, you can build business apps that connect to your business data ### Power Virtual Agents -Power Virtual Agent is a no code, guided graphical interface solution. It's built on the Microsoft Power Platform and the Bot Framework. It empowers every member of your team to create and maintain rich conversational chatbots that easily integrate with the Teams platform. You can design, develop, and publish intelligent virtual agents for Teams without having to setup a development environment, create a web service, or directly register with the Bot Framework. +Power Virtual Agent is a no code, guided graphical interface solution. It's built on the Microsoft Power Platform and the Bot Framework. It empowers every member of your team to create and maintain rich conversational chatbots that easily integrate with the Teams platform. You can design, develop, and publish intelligent virtual agents for Teams without having to set up a development environment, create a web service, or directly register with the Bot Framework. ### Create Virtual Assistant Moodle is a popular open-source Learning Management System (LMS). It's now integ ## Create a Share-to-Teams button for your website -Third-party websites can use the launcher script to embed Share to Teams buttons on their webpages. When you select the button, it launches the Share to Teams experience in a pop-up window. This allows you to share a link directly to any person or Microsoft Teams channel without switching context. +Third-party websites can use the launcher script to embed Share to Teams buttons on their webpages. When you select the button, it launches the Share to Teams experience in a pop-up window. It allows you to share a link directly to any person or Microsoft Teams channel without switching context. ## Add a Microsoft Teams tab in SharePoint You can also integrate Microsoft 365 identity to build external applications tha * [Add a Teams tab to SharePoint](~/tabs/how-to/tabs-in-sharepoint.md) * [Create deep links](~/concepts/build-and-test/deep-links.md) * [Device capabilities](~/concepts/device-capabilities/device-capabilities-overview.md)-* [people picker control](~/concepts/device-capabilities/people-picker-capability.md) +* [People picker control](~/concepts/device-capabilities/people-picker-capability.md) |
| platform | Integrating Web Apps | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/samples/integrating-web-apps.md | If your app is used by multiple organizations, consider multitenant hosting. It ***Integration scenarios**: Standalone apps, collaboration apps* -Your app's APIs and data structures must support the app when integrating with Teams. To extend the support, you must augment the APIs and data structures with contextual information about Teams for [identity mapping](../concepts/authentication/configure-identity-provider.md), [deep-link support](../concepts/build-and-test/deep-links.md), and [incorporating Microsoft Graph](/graph/teams-concept-overview). +Your app's APIs and data structures must support the app when integrating with Teams. To extend the support, you must augment the APIs and data structures with contextual information about Teams for [identity mapping](../concepts/authentication/authentication.md), [deep-link support](../concepts/build-and-test/deep-links.md), and [incorporating Microsoft Graph](/graph/teams-concept-overview). See how to get context for your Teams [tab](../tabs/how-to/access-teams-context.md) or [bot](../bots/how-to/get-teams-context.md). |
| platform | Tab Sso Register Aad | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/tabs/how-to/authentication/tab-sso-register-aad.md | Registering your tab app in Azure AD and enabling it for SSO requires making app :::image type="content" source="../../../assets/images/authentication/teams-sso-tabs/register-azure-ad.png" alt-text="Configure Azure AD to send access token to Teams Client app"::: -Create a new app registration in Azure AD, and expose its (web) API using scopes (permissions). Configure a trust relationship between the exposed API on Azure AD and your app. This allows Teams Client to obtain an access token on behalf of your application and the logged-in user. You can add client IDs for the trusted mobile, desktop, and web applications that you want to pre-authorize. +Create a new app registration in Azure AD, and expose its (web) API using scopes (permissions). Configure a trust relationship between the exposed API on Azure AD and your app. It allows Teams Client to obtain an access token on behalf of your application and the logged-in user. You can add client IDs for the trusted mobile, desktop, and web applications that you want to pre-authorize. You may also need to configure additional details, such as authenticating app users on the platform or device where you want to target your tab app. Azure AD configuration enables SSO for your tab app in Teams. It responds with a It's helpful if you learn about the configuration for registering your app on Azure AD beforehand. Ensure that you've prepared to configure the following details prior to registering your app: -- **Single- or multi-tenant options**: Will your application be used in only the Microsoft 365 tenant where it is registered, or will many Microsoft 365 tenants use it? Applications written for one enterprise are typically single-tenant; applications written by an independent software vendor and used by many customers need to be multi-tenant so each customer's tenant can access the application.+- **Single- or multi-tenant options**: Will your application be used in only the Microsoft 365 tenant where it's registered, or will many Microsoft 365 tenants use it? Applications written for one enterprise are typically single-tenant. Applications written by an independent software vendor and used by many customers need to be multi-tenant so each customer's tenant can access the application. - **Application ID URI**: It's a globally unique URI that identifies the web API you expose for your app's access through scopes. It's also referred to as an identifier URI. The application ID URI includes the app ID and the subdomain where your app is hosted. Your application's domain name and the domain name you register for your Azure AD application should be the same. Currently, multiple domains per app aren't supported. - **Scope**: It's the permission that an authorized app user or your app can be granted for accessing a resource exposed by the API. Register a new app in Azure AD, and configure the tenancy and app's platform. Yo | Option | Select this to... | | | | | Accounts in this organizational directory only (Microsoft only - Single tenant) | Build an application for use only by users (or guests) in your tenant. <br> Often called LOB application, this app is a single-tenant application in the Microsoft identity platform. |- | Accounts in any organizational directory (Any Azure AD directory - Multi-tenant) | Let users in any Azure AD tenant use your application. This option is appropriate if, for example, you're building a SaaS application, and you intend make it available to multiple organizations. <br> This type of app is known as a multi-tenant application in the Microsoft identity platform.| + | Accounts in any organizational directory (Any Azure AD directory - Multi-tenant) | Let users in any Azure AD tenant use your application. This option is appropriate if, for example, you're building a SaaS application, and you intend to make it available to multiple organizations. <br> This type of app is known as a multi-tenant application in the Microsoft identity platform.| | Accounts in any organizational directory (Any Azure AD directory - Multi-tenant) and personal Microsoft accounts | Target the widest set of customers. <br> By selecting this option, you're registering a multi-tenant application that can support app users who have personal Microsoft accounts also. | | Personal Microsoft accounts only | Build an application only for users who have personal Microsoft accounts. | To configure scope and authorize trusted client applications, you'll need: The **Add a client application** page appears. -1. Enter the appropriate client ID for the Teams Client for the applications that you want to authorize for your appΓÇÖs web application. +1. Enter the appropriate Microsoft 365 client ID for the Teams Client for the applications that you want to authorize for your appΓÇÖs web application. :::image type="content" source="../../../assets/images/authentication/teams-sso-tabs/add-client-app.png" alt-text="Add a client application"::: > [!NOTE] >- > - The client IDs for Teams mobile, desktop, and web application are the actual IDs that you should add. + > - The Microsoft 365 client IDs for mobile, desktop, and web applications for Teams, Office, and Outlook are the actual IDs that you should add. > - For a Teams tab app, you'll need either Web or SPA, as you can't have a mobile or desktop client application in Teams. 1. Choose one of the following client IDs: To configure scope and authorize trusted client applications, you'll need: | | | | 1fec8e78-bce4-4aaf-ab1b-5451cc387264 | Teams mobile or desktop application | | 5e3ce6c0-2b1f-4285-8d4b-75ee78787346 | Teams web application |+ | 4765445b-32c6-49b0-83e6-1d93765276ca | Office web application | + | 0ec893e0-5785-4de6-99da-4ed124e5296c | Office desktop application | + | d3590ed6-52b3-4102-aeff-aad2292ab01c | Outlook desktop, mobile application | + | bc59ab01-8403-45c6-8796-ac3ef710b3e3 | Outlook web application | 1. Select the application ID URI you created for your app in **Authorized scopes** to add the scope to the web API you exposed. |
| platform | What Are Tabs | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/tabs/what-are-tabs.md | You can have multiple channels or group tabs, and up to 16 personal tabs per app ### Tools to build tabs -* [Teams Toolkit for Microsoft Visual Studio Code](../toolkit/visual-studio-code-overview.md) +* [Teams Toolkit for Visual Studio Code](../toolkit/teams-toolkit-fundamentals.md) * [Teams Toolkit for Visual Studio](../toolkit/visual-studio-overview.md) ## Next step |
| platform | Accounts | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/toolkit/accounts.md | - Title: Prepare accounts to build Teams apps- -description: In this module, Learn how to prepare accounts to build Teams apps with Microsoft 365 account and developer program. Azure account to host backend resources -- Previously updated : 03/14/2022--# Prepare accounts to build Teams apps --To create and upload a Teams app, you need to prepare the following accounts: --* [Microsoft 365 account with valid subscription](accounts.md#microsoft-365-account) -* [Azure account to host the backend resources on Azure](accounts.md#azure-account-to-host-backend-resources) --## Microsoft 365 account --To create a Microsoft 365 account, sign-up for a Microsoft 365 developer program subscription. The subscription is free for 90 days and continues to renew as long as you're using it for development activity. --If you have a Visual Studio Enterprise or Professional subscription, both programs include free Microsoft 365 [developer subscription](https://aka.ms/MyVisualStudioBenefits). It's active as long as your Visual Studio subscription is active. For more information, see [Microsoft 365 developer subscription](https://developer.microsoft.com/microsoft-365/dev-program). --### Microsoft 365 developer program --To get a free Teams developer account, join the Microsoft 365 developer program and follow the steps: --1. Go to the [Microsoft 365 developer program](https://developer.microsoft.com/microsoft-365/dev-program). -2. Select **Join Now**. -3. Select **Set up E5 subscription**. -4. Set up your administrator account. -- You can see the following image after the completion of the subscription: -- :::image type="content" source="./images/m365-developer-program.png" alt-text="Diagram that shows Microsoft 365 program"::: --### Microsoft 365 developer account types --You can sign-up for the developer program by using one of the following account types: --* **Microsoft account for personal use** -- The account provides access to Microsoft products and cloud services, such as Outlook, Messenger, OneDrive, MSN, Xbox Live, or Microsoft 365. You can sign-up for an Outlook.com mailbox to create a Microsoft account, which can be used to access consumer-related Microsoft cloud services or Azure. --* **Microsoft work account for business** -- The account provides access to all small, medium, and enterprise business-level Microsoft cloud services, such as Azure, Microsoft Intune, or Microsoft 365. When you sign-up to one of these services as an organization, a cloud-based directory is automatically provisioned in Azure AD to represent your organization. --* **Visual Studio user ID** -- The user ID for Visual Studio Professional or Enterprise subscription can be used to join the developer program within the Visual Studio Gallery to avail full benefits as a Visual Studio subscriber. --## Azure account to host backend resources --Azure account is optional, if your existing application is hosted on other cloud provider and you want to integrate the existing application on Teams platform. --**Visual Studio ID** --If you want to host your application related resources or access resources within Azure, you can [create a free account](https://azure.microsoft.com/free/) before you begin. Alternatively you can select to host your backend resources using another cloud provider, or on your own servers if they're available from the public domain. --## Upload custom app --> [!IMPORTANT] -> After creating the app, you must load your app in Teams without distributing it. This process is known as **sideloading**. -- You can verify if the sideloading permission is enabled using either Visual Studio Code or Teams client. --* **Verify sideloading permission using Visual Studio Code** -- 1. Open **Visual Studio Code**. - 2. Select **Teams Toolkit** from the left panel. If you're unable to see the option ensure that you have installed Teams Toolkit extension. - 3. Select **Accounts** and log in to your Microsoft 365 account. - 4. Check whether you can view the option **Sideloading enabled** as shown in the following image: -- :::image type="content" source="../assets/images/teams-toolkit-v2/sideloading.png" alt-text="Enable sideloading"::: --* **Verify sideloading permission using Teams client** -- 1. Open **Microsoft Teams**. - 2. Select **Apps** in left panel. - 3. Select **Publish an app**. -- :::image type="content" source="../assets/images/teams-toolkit-v2/publish2.png" alt-text="Publish an app"::: -- 4. Check whether you can see the option **Upload a custom app** as shown in the following image: -- :::image type="content" source="../assets/images/teams-toolkit-v2/upload2.png" alt-text="Upload a custom app"::: -- If you are unable to view the option **Upload a custom app,** then it indicates that you don't have the required permission for sideloading. -- * For a tenant admin, enable the sideloading setting for your tenant or organization in the Teams admin center. - * If you aren't a tenant admin, you'll need to contact your tenant admin to enable sideloading. --* **Upload custom app using admin center** -- > [!IMPORTANT] - > To turn on custom app uploading or sideloading for your developer tenant, you must be the admin for your tenant. -- Perform the following steps to upload the custom app: -- 1. Sign-in to [Microsoft 365 admin center](https://admin.microsoft.com/Adminportal/Home?source=applauncher#/homepage#/) with your admin credentials. -- 2. Select **Show All** > **Teams**. -- :::image type="content" source="../assets/images/teams-toolkit-v2/5.png" alt-text="show all"::: -- > [!Note] - > It can take **up to 24 hours** for the **Teams** option to appear. You can [upload your custom app to a Teams environment](/microsoftteams/upload-custom-apps) for testing and validation. -- 3. Go to **Teams apps** > **Setup policies**. -- :::image type="content" source="../assets/images/teams-toolkit-v2/3.png" alt-text="set policies"::: -- 4. Set toggle **Upload custom apps** to **On** position. -- :::image type="content" source="../assets/images/teams-toolkit-v2/4.png" alt-text="toggle"::: -- 5. Select **Save**. -- > [!Note] - > It can take up to 24 hours for sideloading to become active. In the meantime, you can use **upload for your tenant** to test your app. To upload the .zip package file of the app, see [Upload custom apps](/microsoftteams/teams-app-setup-policies). --For more information, see [Manage custom app policies and settings in Teams](/microsoftteams/teams-custom-app-policies-and-settings) and [Manage app setup policies in Teams](/microsoftteams/teams-app-setup-policies). --## See also --* [Create a new Teams app using Teams Toolkit](create-new-project.md) -* [Provision cloud resources](provision.md) -* [Deploy Teams app to the cloud](deploy.md) -* [Publish your Teams app](../concepts/deploy-and-publish/appsource/publish.md) -* [Manage multiple environments](TeamsFx-multi-env.md) |