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

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

-description: Learn how Real-time Media Platform enables bots to interact with Microsoft Teams calls and meetings. Explore, media sessions, frames and frame rate, audio and video format, active speakers, video subscription.

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

-Bots integrate directly into TeamΓÇÖs messaging framework. Users can chat with a bot to get their questions answered or type commands to have the bot perform a narrow or specific set of tasks. Bots can proactively notify users about changes or updates to your app via chat.

-* [Publish your Power Virtual Agents bot](/power-virtual-agents/publication-fundamentals-publish-channels)

-description: Learn how to create new conversation threads, work on user and tag mentions, and send message on install. Explore Teams file upload sample (.NET, JavaScript, Python).

-> * Posting a message or Adaptive Card to a private channel is currently not supported.

-description: In this module, learn about conversation update, message reaction, app installation update events, uninstall behavior, and events and error handling for Microsoft Teams bots.

-Message formatting enables you to bring out the best in bot messages. You can format your bot messages to include rich cards as attachments that contain interactive elements, such as buttons, text, images, and so on.

-Some styles are currently not supported across all platforms. The following table provides a list of styles and which of these styles are supported in text-only messages and rich cards:

-* [SDK reference](/python/api/botbuilder-core/botbuilder.core.teams.teamsinfo?view=botbuilder-py-latest#botbuilder-core-teams-teamsinfo-get-team-members&preserve-view=true)

-description: Understand use cases and Microsoft Teams app features, map use cases, and plan responsive tabs for mobile. Learn about Teams features, availability, and app supports for GCC, GCC-High, and DOD.

-* [Design Adaptive Cards](../../task-modules-and-cards/cards/design-effective-cards.md)

-* [Microsoft Teams Store validation guidelines](../deploy-and-publish/appsource/prepare/teams-store-validation-guidelines.md)

-* [App manifest](../../resources/schem)

-description: Learn how to package your Microsoft Teams app and upload it to Teams. Create app package, enable custom uploading, ensure your app is running and accessible using HTTPs.

-* [Distribute your Microsoft Teams app](../deploy-and-publish/apps-publish-overview.md)

-* [Manage your apps with the Developer Portal for Microsoft Teams](~/concepts/build-and-test/teams-developer-portal.md)

-* [Test your app](test-app-overview.md)

-|`&openInMeeting=false`| Use `openInMeeting` to control the user experience when the target tab is associated with a meeting. If user interacts with the deep link in an ongoing meeting experience, Teams opens the app in the in-meeting side panel. Set this value to `false` to always open the app in the meeting chat tab rather than the side panel, regardless of the meeting status. Teams ignores any value other than `false`. | `false` |

-* [Integrate web apps](../../samples/integrate-web-apps-overview.md)

-* [Deep link to an application](deep-link-application.md)

-* [Deep link to Teams chat](deep-link-teams.md)

-* [Deep link to a workflow in Teams](deep-link-workflow.md)

-* [Test your app](test-app-overview.md)

-* [Add test data to your Microsoft 365 test tenant](~/concepts/build-and-test/test-data.md)

-* [Microsoft 365 Multi-Geo](/microsoft-365/enterprise/microsoft-365-multi-geo?view=o365-worldwide&preserve-view=true)

-## See also

-[Integrate web apps](../../samples/integrate-web-apps-overview.md)

-* [Debug your bots](~/bots/how-to/debug/locally-with-an-ide.md)

-* [Test your app](test-app-overview.md)

-## See also

-[Distribute your Microsoft Teams app](apps-publish-overview.md)

-description: Learn to distribute, publish your app to Microsoft Teams Store or to your org. Understand how app's endpoints must comply with your Government Community Cloud(GCC) organization's requirements.

-* [Enable customization for your Microsoft Teams app](../design/enable-app-customization.md)

-* [Distribute your Microsoft Teams app](apps-publish-overview.md)

-## See also

-[Strategize and execute growth for your app](overview-app-growth.md)

-## See also

-[Strategize and execute growth for your app](overview-app-growth.md)

-## See also

-[Strategize and execute growth for your app](overview-app-growth.md)

-description: Maintain your published Microsoft Teams app. Analyze app usage, publish updates, promote your app, check Teams Store marketing guidelines, and complete Microsoft 365 Certification.

-description: Understand Microsoft Teams Store ranking parameters like historical usage and user engagement data. Other parameters include app quality and values, audience relevance, and app update.

-* [Monetize your app](monetize-overview.md)

-* [Include a SaaS offer with your Microsoft Teams app](include-saas-offer.md)

-## See also

-[Publish your app to the Microsoft Teams Store](../publish.md)

-* [Monetize your app](monetize-overview.md)

-* [Set up Microsoft license management for third-party apps](manage-third-party-apps-license.md)

-## See also

-* [Monetize your app](monetize-overview.md)

-* [App Manifest](../../../../resources/schem)

-description: Learn to monetize your Microsoft Teams app by selling subscription plans directly from your Microsoft Teams Store listing. Understand publish app, end-user, admin purchase experience.

-* [Monetize your app](monetize-overview.md)

-* [Maintaining and supporting your published app](../post-publish/overview.md)

-## See also

-[Monetize your app](monetize-overview.md)

-description: Final steps before you submit your Microsoft Teams app to be listed on the Microsoft Teams Store. Validate app package and complete publisher verification and attestation.

-* [Publish your app to the Microsoft Teams Store](../publish.md)

-* [Prepare your Microsoft 365 tenant](../../../build-and-test/prepare-your-o365-tenant.md)

-* [Resolve issues if your Microsoft Teams Store submission fails](~/concepts/deploy-and-publish/appsource/resolve-submission-issues.md)

-description: Know how to increase the chances of your app to pass the Microsoft Teams Store submission process. Understand the mandatory and suggested fixes. Explore the validation guidelines.

-description: Learn how to use UI components from Teams UI kit to build Microsoft Teams apps. Learn to use UI components such a Fluent kit, breadcrumb, button card, carousel, dropdown, and toggle.

- * [See full avatar guidelines (Figma)](https://www.figma.com/community/file/916836509871353159)

- * [See full copy and content guidelinesΓÇöincluding writing for bots (Figma)](https://www.figma.com/community/file/916836509871353159)

-* Authenticate users

-* Manage app features

-* [Customize apps in the Teams admin center](/microsoftteams/customize-apps)

-* [Distribute your Microsoft Teams app](../deploy-and-publish/apps-publish-overview.md)

-> - Users using multiple Teams platform capabilities are 20 ΓÇô 35pp better retained than single capability users.

-description: Learn about Microsoft Teams app capabilities such as, tabs, bots, meeting extensions, message extensions, webhook connectors, personal app experience, and shared app experience.

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

-> * Support for `location` is enabled through [**getLocation API**](/javascript/api/@microsoft/teams-js/microsoftteams.location?.view=msteams-client-js-latest#getLocation_LocationProps___error__SdkError__location__Location_____void_&preserve-view=true). You must use this `getLocation API` for location, as HTML5 geolocation API is currently not fully supported on Teams desktop.

-* [Integrate web apps](../../samples/integrate-web-apps-overview.md)

-RSC permissions are only available to Teams apps installed on the Teams client and are currently not part of the Microsoft Entra admin center and are declared in the app manifest (previously called Teams app manifest) (JSON) file. You can manage RSC permissions for Teams apps in Developer Portal from the **Permissions** section under **Configure**.

-When a bot or messaging extension is registered on Microsoft Entra admin center, it will have a Microsoft Entra app ID associated with it, which can be found in **Microsoft Entra admin center** > **App Registrations**. Endpoints and other bot configurations are managed in the Azure portal.

-When a bot or messaging extension is registered in the Developer or Bot Framework portal, it will not have a Microsoft Entra app ID. However, the bot or messaging extension ID can be found on the Bot Framework portal. Endpoints and other bot configurations are managed in the Bot Framework portal.

-description: In this article, learn how to grant resource-specific consent (RSC) permissions, which allows team, chat owners, users, and meeting organizers to grant consent for an app.

-* [Test resource-specific consent permissions in Teams](test-resource-specific-consent.md)

-* [Resource-specific consent](resource-specific-consent.md)

-* [Test resource-specific consent permissions in Teams](test-resource-specific-consent.md)

-* [Resource-specific consent](resource-specific-consent.md)

-> Microsoft's cloud services, including web versions of Teams (*teams.microsoft.com*), Outlook (*outlook.com*), and Microsoft 365 (*microsoft365.com*) domains are migrating to the *cloud.microsoft* domain. Perform the following steps before June 2024 to ensure your app continues to render on the Teams web client:

-> 1. Update TeamsJS SDK to v.2.19.0 or higher. For more information about the latest release of TeamsJS SDK, see [Microsoft Teams JavaScript client library](https://www.npmjs.com/package/@microsoft/teams-js).

-> 2. Update your [Content Security Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP) headers in your Teams app to allow your app to access the ***teams.cloud.microsoft*** domain. If your Teams app extends across Outlook and Microsoft 365, ensure you allow your app to access ***teams.cloud.microsoft***, ***outlook.cloud.microsoft***, and ***m365.cloud.microsoft*** domains.

-| **Microsoft 365 app host** | **frame-ancestor permission** |

-|--|--|

-| Teams | `teams.microsoft.com`, `*.teams.microsoft.com`, `teams.cloud.microsoft` |

-| Microsoft 365 app | `*.microsoft365.com`, `*.office.com`, `m365.cloud.microsoft` |

-| Outlook | `outlook.live.com`, `outlook.office.com`, `outlook.office365.com`, `outlook-sdf.office.com`, `outlook-sdf.office365.com`, `outlook.cloud.microsoft` |

-description: Learn how to add an Outlook Add-in to a Teams app. This article walks you through the steps to add an Outlook Add-in to a Teams app, test it, then deploy it to Azure.

-description: Requirements to set up your dev environment for extending Teams apps across Microsoft 365. Know configurations required to run builds of Microsoft Teams and Microsoft 365 applications.

- 1. At the top right, select **Org-wide app settings**.

- 1. Under Custom apps, turn on the **Interaction with custom apps** toggle and **Save**.

- :::image type="content" source="images/teams-admin-enable-sideloading.png" alt-text="The screenshot is an example that enables custom app upload from the Teams Admin Center":::

- 1. Apart from Org-wide app settings, custom app policy settings also allow users to upload custom apps to Teams. For more information, see [manage custom app policies and settings](/microsoftteams/teams-custom-app-policies-and-settings#custom-app-policy-and-settings).

- 1. In the Teams admin center, go to **Teams apps** > **Setup policies**, and then select **Global (Org-wide default) policy**.

- 1. Turn on **Upload custom apps**, and select **Save**.

-description: Learn how to make your Microsoft 365-enabled Teams apps discoverable to users in Teams, Outlook, and Microsoft 365 app through single tenant and multitenant distribution.

-description: Understand the level of support for different TeamsJS library capabilities running in different hosts for Teams apps, including Microsoft Teams, Outlook, and Microsoft 365 app.

-description: Learn how to build a message extension from an OpenAPI description document (OAD) using using Developer Portal for Teams, Visual Studio Code, Teams Toolkit CLI, or Visual Studio.

-description: Learn how to design a Teams message extension and get the Microsoft Teams UI Kit. Describes about Teams design guidelines reference message extensions tips and best practice.

-Action-based message extensions frequently require users to complete a form or some other kind of configuration within a modal. You can create these experiences with [dialogs ](../../task-modules-and-cards/task-modules/design-teams-task-modules.md)(referred as task modules in TeamsJS v1.x).

-description: Learn how to create and send dialogs (task modules). Handle the initial invoke action and respond with a dialog (task module) from an action message extension command.

-description: Learn to define messaging extension action commands with app manifest example in Microsoft Teams. Sample (.NET, Node.js) how to define action commands, create dialog (task module), and respond to dialog (task module) submit action.

-* [Sample code reference](https://github.com/OfficeDev/Microsoft-Teams-Samples/blob/main/samples/msgext-action/nodejs/bots/teamsMessagingExtensionsActionBot.js#L24-L61)

-description: Add link unfurling with messaging extension in a Microsoft Teams app with app manifest or manually. Add link unfurling using Developer Portal. How to update your web service code to handle the invoke request.

-* [Sample code reference](https://github.com/OfficeDev/Microsoft-Teams-Samples/blob/main/samples/msgext-search-quickstart/js/botActivityHandler.js#L30-L53)

-* [Sample code reference](https://github.com/OfficeDev/Microsoft-Teams-Samples/blob/main/samples/msgext-search/nodejs/bots/teamsMessagingExtensionsSearchBot.js#L16)

-* [Sample code reference](https://github.com/OfficeDev/Microsoft-Teams-Samples/blob/main/samples/msgext-search-quickstart/js/botActivityHandler.js#L35)

-description: Learn how message extensions are used, its types, and scenarios where it's used on the Microsoft Teams platform. Samples on action and searched based message extension.

-Many features enabled in developer preview require alterations to your app manifest (previously called Teams app manifest) JSON file. To do so, you need to use the [developer preview app manifest schema](~/resources/schem) to make these changes, nor you can use it to upload your app for testing. To upload your app, you need to select the `More apps` icon on the app bar, then select the `Upload a custom app link`. Using this method, you can only upload a zipped version of your app package.

-You might find it useful to use Developer Portal for Teams to create the non-developer preview portions of your app package, then export that package and manually edit the `manifest.json` file to add the developer preview features you wish to use. After you added the developer preview features to the `manifest.json` file, you can't reimport the package into Developer Portal for Teams.

-* [Integrate web apps](../../samples/integrate-web-apps-overview.md)

-* [Partner apps for Moodle](partner-apps-for-moodle.md)

-* [Moodle FAQ](faqs.md)

-description: Learn partner apps for Moodle, key benefits of partner apps for Moodle, SaaS offerings and mConnect. Enable singe-sign-on SSO for users of Teams.

-* [Moodle FAQ](faqs.md)

-description: Learn about Types of cookies, including SameSite cookies, their attributes, their implications in Teams tabs, dialogs (task modules), and message extensions, and their authentication in Teams

- "websiteUrl": "https://website.com/",

- "privacyUrl": "https://website.com/privacy",

- "termsOfUseUrl": "https://website.com/app-tos",

-Defines a set of tabs that can be "pinned" by default, without the user adding them manually. Static tabs declared in `personal` scope are always pinned to the app's personal experience. Static tabs declared in the `team` scope are currently not supported.

-description: In this article, you'll have the latest version of the public manifest schema for Microsoft Teams reference, schema and sample full manifest.

- "publisherDocsUrl": "https://website.com/app-info",

-|`full`|100 characters|✔️|The full name of the app, used if the full app name exceeds 30 characters. Use `full` property where there is more space, such as the app catalog or the app details page.|

-|`tabs.groups.controls.items.overriddenByRibbonApi`| Boolean | | | Specifies whether a group, button, menu, or menu item hidden on application and platform combinations which support the API ([Office.ribbon.requestCreateControls](/javascript/api/office/office.ribbon#office-office-ribbon-requestcreatecontrols-member(1))) that installs custom contextual tabs on the ribbon. <br>Default value: `false`|

-|`tabs.groups.controls.actionId`| String | 64 characters | | Required if the control type is `button`. Do not use if the control type is `menu`. Specifies the ID of the action that is taken when a user selects the control. The `actionId` must match the `runtime.actions.id` property of an action in the `runtimes` object.|

-|`tabs.groups.controls.overriddenByRibbonApi`| Boolean | | | Specifies whether a group, button, menu, or menu item is hidden on application and platform combinations which support the API ([Office.ribbon.requestCreateControls](/javascript/api/office/office.ribbon#office-office-ribbon-requestcreatecontrols-member(1))) that installs custom contextual tabs on the ribbon. <br>Default value: `false`|

-|`tabs.customMobileRibbonGroups.controls.icons` | Array | 9 | ✔️ | Specifies the icons that will appear on the control depending on the dimensions and DPI of the mobile device screen. There must be exactly 9 icons.|

-|`tabs.customMobileRibbonGroups.controls.icons.size` | Number enum | | ✔️ | Size in pixels of the icon. The possible sizes are 25, 32, and 48. There must be exactly one of each size for each possible value of the icons's `scale` property. |

-|`tabs.customMobileRibbonGroups.controls.icons.scale` | Number enum | | ✔️ | Specifies the UIScreen.scale property for iOS devices. The possible values are 1, 2, and 3. There must be exactly one of each value for each possible value of the icons's `size` property. |

-|`officeUIFabricIconName`| String | 255 characters | | Office UI Fabric or Fluent UI icon friendly name for the card. This value is used if *iconUrl* is not specified. |

-* By late 2022, bots can't proactively retrieve the `userPrincipalName` or `email` properties for members of a chat or team. Bots must use the Graph APIs to retrieve the required information. The new `GetConversationPagedMembers` API can't return the `userPrincipalName` and `email` properties from late 2022.

-description: In this article, you get started with integrating web applications and device capabilities with Microsoft Teams app. Power platform to create Power apps, Power Virtual Agents, Virtual Assistant, app templates, Shift connectors, Moodle LMS.

-* [Map your app's use cases to Teams platform capabilities](~/concepts/design/map-use-cases.md)

-* [Considerations for Teams integration](~/samples/integrating-web-apps.md)

-* [Device capabilities](~/concepts/device-capabilities/device-capabilities-overview.md)

-description: Learn best practices or considerations for integrating existing web apps with Microsoft Teams. It gives information on API requirements, authentication, and deep-linking of your app with Teams.

-* [Integrate web apps](~/samples/integrate-web-apps-overview.md)

- "websiteUrl": "https://contoso.yourwebsite.com",

- "privacyUrl": "https://contoso.yourwebsite.com/privacy.html",

- "termsOfUseUrl": "https://contoso.yourwebsite.com/terms.html"

- "contoso.yourwebsite.com",

- websiteUrl: "https://yourWebsite.com",

- contentUrl: "https://yourWebsite.com/gray",

- websiteUrl: "https://yourWebsite.com",

- contentUrl: "https://yourWebsite.com/red",

- websiteUrl: "https://yourWebsite.com",

- contentUrl: "https://yourWebsite.com/gray",

- websiteUrl: "https://yourWebsite.com",

- contentUrl: "https://yourWebsite.com/red",

-1. If your application doesn't load, you can call `app.notifyFailure({reason: app.FailedReason.Timeout, message: "failure message"});` to let Teams know about the failure. The `message` property is currently not used, therefore the failure message doesn't appear in the UI, and a generic error screen appears to the user. The following code shows the enumeration that defines the possible reasons you can indicate for the application's failure to load:

-description: In this module, learn how to add modal pop-up experiences to collect or display information to your users from your Microsoft Teams apps.

-* Show an `<iframe>`-based widget such as a YouTube or Microsoft Stream video.

- > It is currently not possible to detect the `err` event when a dialog is invoked from a bot.

-import { AzureKeyCredential, SearchClient } from "@azure/search-documents";

-import { DataSource, Memory, OpenAIEmbeddings, RenderedPromptSection, Tokenizer } from "@microsoft/teams-ai";

-import { TurnContext } from "botbuilder";

-export interface Doc {

- id: string,

- content: string, // searchable

- filepath: string,

- // contentVector: number[] // vector field

- // ... other fields

-export class MyDataSource implements DataSource {

- public readonly name = "my-datasource";

- private readonly embeddingClient: OpenAIEmbeddings;

- private readonly searchClient: SearchClient<Doc>;

- this.searchClient = new SearchClient<Doc>(searchEndpoint, searchIndexName, new AzureKeyCredential(searchApiKey));

- public async renderData(context: TurnContext, memory: Memory, tokenizer: Tokenizer, maxTokens: number): Promise<RenderedPromptSection<string>> {

- const input = memory.getValue("temp.input") as string;

- }

- // Append do to output

-# [iOS](#tab/ios1)

- To clear the Teams app data, go to **Settings** > **Teams** > **Clear App Data**.

- :::image type="content" source="../assets/images/debug-mobile/clear-app-data-ios-option.PNG" alt-text="Screenshot shows how to clear the app data in iOS mobile client for tab." lightbox="../assets/images/debug-mobile/clear-app-data-ios.PNG":::

-# [Android](#tab/android1)

- To clear the Teams app data, go to **Teams** > **Settings** > **Data and storage** > **Clear app data** > **Clear data**.

- :::image type="content" source="../assets/images/debug-mobile/clear-app-data-android-option.PNG" alt-text="Screenshot shows how to clear the app data in android mobile client for tab." lightbox="../assets/images/debug-mobile/clear-app-data-android.PNG":::

-

-# [iOS](#tab/ios2)

- To clear the Teams app data, go to **Settings** > **Teams** > **Clear App Data**.

- :::image type="content" source="../assets/images/debug-mobile/clear-app-data-ios-option.PNG" alt-text="Screenshot shows how to clear the app data in iOS mobile client for bot." lightbox="../assets/images/debug-mobile/clear-app-data-ios.PNG":::

-# [Android](#tab/android2)

- To clear the Teams app data, go to **Teams** > **Settings** > **Data and storage** > **Clear app data** > **Clear data**.

- :::image type="content" source="../assets/images/debug-mobile/clear-app-data-android-option.PNG" alt-text="Screenshot shows how to clear the app data in android mobile client for bot." lightbox="../assets/images/debug-mobile/clear-app-data-android.PNG":::

-

- * Update OpenAI `ApiKey` in the `appsettings.TestTool.json` file.

- :::image type="content" source="../../assets/images/teams-toolkit-v2/teams-toolkit-vs/app-seetings-test-tool.png" alt-text="Screenshot displays the updated OpenAI key.":::