Skip to content

Updated FAQ #13598

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open

Updated FAQ #13598

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
49a9a4f
Updated FAQ
NehaHEDAU-MSFT Nov 25, 2025
048eea4
added team alias and fixed errors
NehaHEDAU-MSFT Nov 27, 2025
e71ff03
Acrolinx changes
NehaHEDAU-MSFT Nov 27, 2025
3f81ca1
minor change
NehaHEDAU-MSFT Nov 27, 2025
5aab5d8
Removed Column 3
NehaHEDAU-MSFT Nov 27, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
52 changes: 42 additions & 10 deletions msteams-platform/teams-faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
---
title: Teams Developer Documentation - FAQs
description: In this article, check FAQS on Adaptive Card Previewer, bots, Live Share, Microsoft 365 Chat, Teams AI library, Teams SDK, Partner Center, and other Teams FAQs.
description: Check FAQs on Adaptive Card Previewer, bots, Live Share, Microsoft 365 Chat, Teams AI library, Teams SDK, Partner Center, and more.
ms.topic: reference
ms.date: 01/23/2025
ms.date: 11/27/2025
ms.localizationpriority: high
ms.owner: angovil
---
Expand Down Expand Up @@ -95,7 +95,7 @@ App registration is disabled for the user or the user doesn't have enough permis
</details>
<details>

<summary>How can I resolve the error "Microsoft.Graph.Communications.Core.Exceptions.ServiceException: 'Code: 9999 Message: Unknown internal server error'"?</summary>
<summary>How can I resolve the error "Microsoft.Graph.Communications.Core.Exceptions.ServiceException: 'Code: 9999 Message: Unknown internal server error'?"</summary>

* Verify that the app has the `Calls.JoinGroupCall.All` and `Calls.InitiateGroupCall.All` permissions and admin consent.
* Sign in to your app to capture more information about the error.
Expand Down Expand Up @@ -153,7 +153,7 @@ Live Share supports scheduled meetings, one-on-one calls, group calls, and meet
<details>
<summary>Will Live Share's media package work with DRM content?</summary>

Live Share's media package doesn't work with DRM content. Teams doesn't support encrypted media for tab applications on desktop. Chrome, Edge, and mobile clients are supported.
Live Share's media package doesn't work with DRM content. Teams doesn't support encrypted media for tab applications on desktop. Chrome, Microsoft Edge, and mobile clients are supported.

For more information, you can [track the issue here](https://github.com/microsoft/live-share-sdk/issues/14).
<br>
Expand Down Expand Up @@ -186,7 +186,7 @@ Live Share only supports having one container using our provided Azure Fluid Rel
Live Share doesn't support adding new `initialObjects` to the Fluid `ContainerSchema` after creating or joining a container. Because Live Share sessions are short-lived, this is most commonly an issue during development after adding new features to your app.

> [!NOTE]
> If you are using the `dynamicObjectTypes` property in the `ContainerSchema`, you can add new types at any point. If you later remove types from the schema, existing DDS instances of those types will gracefully fail.
> If you're using the `dynamicObjectTypes` property in the `ContainerSchema`, you can add new types at any point. If you later remove types from the schema, existing DDS instances of those types will gracefully fail.

To fix errors resulting from changes to `initialObjects` when testing locally in your browser, remove the hashed container ID from your URL and reload the page. If you're testing in a Teams meeting, start a new meeting and try again.

Expand Down Expand Up @@ -257,7 +257,7 @@ If the problem continues, use the thumbs down indicator in the Microsoft 365 Cop

<summary> What descriptions should I include in app manifest? </summary>

Here's an example description that work for NPM Finder.
Here's an example description that works for NPM Finder.

```json
"name": {
Expand Down Expand Up @@ -413,7 +413,7 @@ Yes, both declarative agents and custom engine agents will have the same invocat

<summary>Can Independent Software Vendors (ISVs) enhance their existing wrapped declarative agents moving forward?</summary>

ISVs can continue to improve their message extension agent and submit their app through standard methods or channels. However, they will be limited in terms of adding new instructions or knowledge to their agent.
ISVs can continue to improve their message extension agent and submit their app through standard methods or channels. However, they'll be limited in terms of adding new instructions or knowledge to their agent.
<br>
&nbsp;
</details>
Expand Down Expand Up @@ -540,7 +540,7 @@ No. Azure Marketplace is different than AppSource (and by extension Teams App St

<summary>What are the additional steps to get Buy a subscription option on Teams Store?</summary>

You must add the IDs to the manifest (and uploading through PC to validate) that shows the **Buy a subscription** button in Teams. Partners can continue to have apps available in Teams and require customers to purchase through AppSource. Going through a few additional steps brings the purchase option into the Teams Store.​
You must add the IDs to the manifest (and uploading through PC to validate) that shows the **Buy a subscription** button in Teams. Partners can continue to have apps available in Teams and require customers to purchase through AppSource. Going through a few more steps brings the purchase option into the Teams Store.​

</br>

Expand Down Expand Up @@ -918,7 +918,7 @@ You received this error message because your [account verification status](/part

There are three verification areas, **Email Ownership**, **Employment**, and **Business**. For more information, see [what is verified and how to respond](/partner-center/verification-responses#what-is-verified-and-how-to-respond).

If you're the primary contact, Global Administrator or account admin, you can monitor verification status and track progress on your profile page.
If you're the primary contact, Global Administrator, or account admin, you can monitor verification status and track progress on your profile page.

After the verification process is complete, the status of your enrollment on the profile page changes from *pending* to *authorized*. The primary contact then receives an email from Microsoft within a few business days.
<br>
Expand Down Expand Up @@ -1001,6 +1001,38 @@ The following resources can also assist:

</details>

## Publisher verification for Teams apps

<br>
<details>
<summary>How can I ensure publisher verification for my app if I have a personal or consumer (MSA) user account?</summary>

Publisher Verification isn't supported for applications registered with Personal or Consumer (MSA) user accounts. To complete the process, you must initiate a new app registration with your organizational account in an Microsoft Entra (Azure AD) tenant.

To enable the app to become eligible while minimizing disruption, the following steps are recommended:

| Step # | Action for app verification|
| --- | --- |
| 1 | Contact Microsoft App Validation team (mailto:teamsubm@microsoft.com) while performing the steps for any clarification or guidance required. |
| 2 | Create a business account in Partner Center: Create a new organizational Partner Center or MCPP account and go through the OneVet vetting process. |
| 3 | Create a new [Entra OAuth App Registration](/entra/identity-platform/quickstart-register-app?tabs=certificate) (which will generate a new App ID) using a User account within an organizationally owned Entra tenant. |
| 4 | Go through the Entra [Publisher verification](https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flearn.microsoft.com%2Fen-us%2Fentra%2Fidentity-platform%2Fpublisher-verification-overview&data=05%7C02%7Crmandal%40microsoft.com%7Cabeca4d2db9140aba52e08dd357a7fa2%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638725522430992100%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=0UznYXv0uobW66NwtqwVoIWJ9590ZN9aDuX1NB8ZjrI%3D&reserved=0) process to add a verified publisher to the App Registration created in Step 3, using the MCPP account from Step 2. |
| 5 | Update the manifest of the existing Teams app with the new Entra AppId in the [WebApplicationInfo](/microsoftteams/platform/resources/schema/manifest-schema#webapplicationinfo) section of the Teams app manifest, replace the old Entra Id with the new one generated in Step3. Don't replace the BotId or the Appid in the manifest. |
| 6 | Submit this manifest and app package over [email](mailto:teamsubm@microsoft.com) to M365 CAPE Store Ops. |
| 7 | Microsoft Teams Engineering (App Ingestion Services) will analyze this app package along with the existing app package, and share guidance with you the steps to ensure backward compatibility for the app. |
| 8 | Rename existing app in Partner Center: Using the consumer account in Partner Center, rename the app, following this example: **Contoso For Teams - Legacy**. (This helps unreserve the app name, while submitting the app in step 10.) |
| 9 | Partner Center App publishing team to work with PC engineering to release the app name (with an SLA of 24h) |
| 10 | Once you confirm from M365 CAPE Store Ops that the app name is released, [submit this manifest and app package from the Partner Center](/microsoftteams/platform/concepts/deploy-and-publish/appsource/publish) account created in Step 2 above. |
| 11 | M365 CAPE Store Ops validates the app by manually overriding an error or conflict in OMEX to allow ingestion into AppSource. |
| 12 | M365 CAPE Store Ops approves the app on Partner Center. |
| 13 | App Ingestion Services manually overrides the error or conflict to allow ingestion. |
| 14 | App is published to store as an update to the existing app. |
| 15 | Users see an update of the existing app. |
| 16 | Upgraded and new users see a Consent trigger in the app. |
| 17 | Once the app is published, M365 CAPE Store Ops works with AppSource engineering to migrate ratings and reviews of the existing app on the current appsource.microsoft.com page to the AppSource page for the new app. |

</details>

## Single sign-on

<details>
Expand Down Expand Up @@ -1292,7 +1324,7 @@ Use the `-First` and `-Skip` parameters with `Get-CsAutoAttendant` or `Get-CsCal
<details>
<summary> How can I configure a Teams workflow to wait for manual approval without timing out too quickly?</summary>

Use the **Start and wait for an approval** action in Power Automate. In the action settings, extend the timeout by specifying the duration in ISO 8601 format (for example, `P7D` for 7 days). This ensures the workflow is paused until the approval is granted.
Use the **Start and wait for an approval** action in Power Automate. In the action settings, extend the timeout by specifying the duration in ISO 8601 format (for example, `P7D` for seven days). This ensures the workflow is paused until the approval is granted.
<br>
&nbsp;
</details>
Expand Down