Skip to content
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

[Doc Improvement][Update FAQs] #12105

Draft
wants to merge 7 commits into
base: main
Choose a base branch
from
Draft

[Doc Improvement][Update FAQs] #12105

Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
5f4ef81
Update teams-faq.md
v-shalinir Jan 20, 2025
aaf2a5d
Update teams-faq.md
v-shalinir Jan 20, 2025
3ae865a
Update teams-faq.md
v-shalinir Jan 20, 2025
b7b8e21
Update teams-faq.md
v-shalinir Jan 20, 2025
8027c3b
Update teams-faq.md
v-shalinir Jan 22, 2025
ed6bc91
Update teams-faq.md
v-shalinir Jan 22, 2025
d93beeb
Update teams-faq.md
v-shalinir Jan 22, 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
32 changes: 32 additions & 0 deletions msteams-platform/teams-faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -968,6 +968,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 is not 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 Entra (Azure AD) tenant.

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

| Step # | Action for app verification | MSFT PoC |
| --- | --- | --- |
| 1 | Contact Microsoft (M365 CAPE Store Ops) - [Rajarshi Mandal](mailto:[email protected]) while performing the steps for any clarification or guidance required. | M365 CAPE Store Ops |
| 2 | Create a business account in Partner Center: Create a new organizational Partner Center or MCPP account and go through the OneVet vetting process. | Vetting (for OneVet 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. | Entra Engineering |
| 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. | Entra Engineering |
| 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. Do not replace the BotId or the Appid in the manifest. | OMEX |
| 6 | Submit this manifest and app package over [email](mailto:[email protected]) to M365 CAPE Store Ops. | M365 CAPE Store Ops |
| 7 | Microsoft Teams Engineering (App Ingestion Services) will analyze this app package alongwith the existing app package, and share guidance with you the steps to ensure backward compatibility for the app. | App Ingestion Services |
| 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.) | Partner Center Engineering |
| 9 | Partner Center App publishing team to work with PC engineering to release the app name (with an SLA of 24h) | Partner Center Engineering |
| 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. | Partner Center Engineering |
| 11 | M365 CAPE Store Ops validates the app by manually overriding an error or conflict in OMEX to allow ingestion into AppSource. | M365 CAPE Store Ops |
| 12 | M365 CAPE Store Ops approves the app on Partner Center. | M365 CAPE Store Ops |
| 13 | App Ingestion Services manually overrides the error or conflict to allow ingestion. | App Ingestion Services |
| 14 | App is published to store as an update to the existing app. | App Ingestion Services |
| 15 | Users see an update of the existing app. | App Ingestion Services |
| 16 | Upgraded and new users see a Consent trigger in the app. | App Ingestion Services |
| 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. | AppSource engineering |

</details>

## Single sign-on

<details>
Expand Down