From 5f4ef81aaef9884e3bca4427bdf88e9c214da0fa Mon Sep 17 00:00:00 2001 From: v-shalinir Date: Mon, 20 Jan 2025 22:18:49 +0530 Subject: [PATCH 1/7] Update teams-faq.md Added details for the Zoom support in Teams --- msteams-platform/teams-faq.md | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/msteams-platform/teams-faq.md b/msteams-platform/teams-faq.md index 9979f5900bf..756a4b21c2c 100644 --- a/msteams-platform/teams-faq.md +++ b/msteams-platform/teams-faq.md @@ -1220,3 +1220,30 @@ Shared references to deploy the code using toolkit: You can call Graph API to get the app user's profile photo. + +## Zoom for Teams + +
+How can I support Zoom in Teams? + +Publisher Verification is not supported for applications registered with Personal/Consumer (MSA) User accounts. In order to complete the process, a new App Registration will need to be created with your Organizational account in an Entra (Azure AD) tenant. In order for the app to become eligible while minimizing disruption, the following steps are recommended. We are happy to support Zoom throughout this process which will need cross engineering coordination. However, as a caution, Zoom must note that there is no way available currently to do this without existing end users having to re-consent to the app once this update is published. + +| Step # | Action for Zoom | MSFT PoC | +| --- | --- | --- | +| 1 | Zoom to contact with Microsoft (M365 CAPE Store Ops) - [Rajarshi Mandal](rmandal@microsoft.com) 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/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](teamsubm@microsoft.com) to M365 CAPE Store Ops | 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 back to Zoom on steps to ensure backward compatibility for their app. | +| 8 | Rename existing app in Partner Center: Using the Consumer account in Partner Center - rename the app to **Zoom For Teams - Legacy**. (This will help 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 Zoom has confirmation from M365 CAPE Store Ops that the app name is released, Zoom [should 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/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 to work with AppSource engineering to migrate the Ratings and Reviews of the existing app onZoom’s current appsource.microsoft.com page to the AppSource page for the new app. | AppSource engineering | From aaf2a5daa2ae2c33725ff5ca6c1bf03edad58d1c Mon Sep 17 00:00:00 2001 From: v-shalinir Date: Mon, 20 Jan 2025 22:27:46 +0530 Subject: [PATCH 2/7] Update teams-faq.md --- msteams-platform/teams-faq.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/msteams-platform/teams-faq.md b/msteams-platform/teams-faq.md index 756a4b21c2c..0d74a180493 100644 --- a/msteams-platform/teams-faq.md +++ b/msteams-platform/teams-faq.md @@ -1230,12 +1230,12 @@ Publisher Verification is not supported for applications registered with Persona | Step # | Action for Zoom | MSFT PoC | | --- | --- | --- | -| 1 | Zoom to contact with Microsoft (M365 CAPE Store Ops) - [Rajarshi Mandal](rmandal@microsoft.com) while performing the steps for any clarification or guidance required. | M365 CAPE Store Ops | +| 1 | Zoom to contact with Microsoft (M365 CAPE Store Ops) - [Rajarshi Mandal](mailto:rmandal@microsoft.com) 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/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](teamsubm@microsoft.com) to M365 CAPE Store Ops | M365 CAPE Store Ops | +| 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:teamsubm@microsoft.com) to M365 CAPE Store Ops | 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 back to Zoom on steps to ensure backward compatibility for their app. | | 8 | Rename existing app in Partner Center: Using the Consumer account in Partner Center - rename the app to **Zoom For Teams - Legacy**. (This will help 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 | From 3ae865a9ba0bcee9fd1bb8bc4511221336314b2a Mon Sep 17 00:00:00 2001 From: v-shalinir Date: Mon, 20 Jan 2025 22:29:50 +0530 Subject: [PATCH 3/7] Update teams-faq.md --- msteams-platform/teams-faq.md | 1 + 1 file changed, 1 insertion(+) diff --git a/msteams-platform/teams-faq.md b/msteams-platform/teams-faq.md index 0d74a180493..faa6c1c960f 100644 --- a/msteams-platform/teams-faq.md +++ b/msteams-platform/teams-faq.md @@ -1223,6 +1223,7 @@ You can call Graph API to get the app user's profile photo. ## Zoom for Teams +
How can I support Zoom in Teams? From b7b8e215344a3dac67f1a5d05c4113f921cc4022 Mon Sep 17 00:00:00 2001 From: v-shalinir Date: Mon, 20 Jan 2025 22:34:55 +0530 Subject: [PATCH 4/7] Update teams-faq.md --- msteams-platform/teams-faq.md | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/msteams-platform/teams-faq.md b/msteams-platform/teams-faq.md index faa6c1c960f..b20444b6be1 100644 --- a/msteams-platform/teams-faq.md +++ b/msteams-platform/teams-faq.md @@ -1227,24 +1227,24 @@ You can call Graph API to get the app user's profile photo.
How can I support Zoom in Teams? -Publisher Verification is not supported for applications registered with Personal/Consumer (MSA) User accounts. In order to complete the process, a new App Registration will need to be created with your Organizational account in an Entra (Azure AD) tenant. In order for the app to become eligible while minimizing disruption, the following steps are recommended. We are happy to support Zoom throughout this process which will need cross engineering coordination. However, as a caution, Zoom must note that there is no way available currently to do this without existing end users having to re-consent to the app once this update is published. +Publisher Verification is not supported for applications registered with Personal or Consumer (MSA) User accounts. In order to complete the process, a new App Registration will need to be created with your Organizational account in an Entra (Azure AD) tenant. In order for the app to become eligible while minimizing disruption, the following steps are recommended. We are happy to support Zoom throughout this process which will need cross engineering coordination. However, as a caution, Zoom must note that there is no way available currently to do this without existing end users having to re-consent to the app once this update is published. | Step # | Action for Zoom | MSFT PoC | | --- | --- | --- | | 1 | Zoom to contact with Microsoft (M365 CAPE Store Ops) - [Rajarshi Mandal](mailto:rmandal@microsoft.com) 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/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 | +| 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:teamsubm@microsoft.com) to M365 CAPE Store Ops | 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 back to Zoom on steps to ensure backward compatibility for their app. | +| 6 | Submit this manifest and app package over [email](mailto:teamsubm@microsoft.com) to M365 CAPE Store Ops. | 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 back to Zoom on steps to ensure backward compatibility for their app. | App Ingestion Services | | 8 | Rename existing app in Partner Center: Using the Consumer account in Partner Center - rename the app to **Zoom For Teams - Legacy**. (This will help 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 Zoom has confirmation from M365 CAPE Store Ops that the app name is released, Zoom [should 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/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 | +| 11 | M365 CAPE Store Ops validates the app by manually overriding an error/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 | +| 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 to work with AppSource engineering to migrate the Ratings and Reviews of the existing app onZoom’s current appsource.microsoft.com page to the AppSource page for the new app. | AppSource engineering | From 8027c3bb9dd9f817ca6365b4b15b959e516d8934 Mon Sep 17 00:00:00 2001 From: v-shalinir Date: Wed, 22 Jan 2025 13:19:15 +0530 Subject: [PATCH 5/7] Update teams-faq.md --- msteams-platform/teams-faq.md | 22 ++++++++++++---------- 1 file changed, 12 insertions(+), 10 deletions(-) diff --git a/msteams-platform/teams-faq.md b/msteams-platform/teams-faq.md index b20444b6be1..708345e828a 100644 --- a/msteams-platform/teams-faq.md +++ b/msteams-platform/teams-faq.md @@ -1221,30 +1221,32 @@ You can call Graph API to get the app user's profile photo.
-## Zoom for Teams +## Publisher verification for Teams apps
-How can I support Zoom in Teams? +How can I ensure publisher verification for my app if I have a personal or consumer (MSA) user account? -Publisher Verification is not supported for applications registered with Personal or Consumer (MSA) User accounts. In order to complete the process, a new App Registration will need to be created with your Organizational account in an Entra (Azure AD) tenant. In order for the app to become eligible while minimizing disruption, the following steps are recommended. We are happy to support Zoom throughout this process which will need cross engineering coordination. However, as a caution, Zoom must note that there is no way available currently to do this without existing end users having to re-consent to the app once this update is published. +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. -| Step # | Action for Zoom | MSFT PoC | +To enable the app to become eligible while minimizing disruption, the following steps are recommended: + +| Step # | Action for app verification | MSFT PoC | | --- | --- | --- | -| 1 | Zoom to contact with Microsoft (M365 CAPE Store Ops) - [Rajarshi Mandal](mailto:rmandal@microsoft.com) while performing the steps for any clarification or guidance required. | M365 CAPE Store Ops | +| 1 | Contact Microsoft (M365 CAPE Store Ops) - [Rajarshi Mandal](mailto:rmandal@microsoft.com) 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:teamsubm@microsoft.com) to M365 CAPE Store Ops. | 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 back to Zoom on steps to ensure backward compatibility for their app. | App Ingestion Services | -| 8 | Rename existing app in Partner Center: Using the Consumer account in Partner Center - rename the app to **Zoom For Teams - Legacy**. (This will help unreserve the app name, while submitting the app in step 10.) | Partner Center Engineering | +| 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 Zoom has confirmation from M365 CAPE Store Ops that the app name is released, Zoom [should 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/conflict in OMEX to allow ingestion into AppSource. | M365 CAPE Store Ops | +| 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 to work with AppSource engineering to migrate the Ratings and Reviews of the existing app onZoom’s current appsource.microsoft.com page to the AppSource page for the new app. | AppSource engineering | +| 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](appsource.microsoft.com) page to the AppSource page for the new app. | AppSource engineering | From ed6bc91f30b159f4675c4ee4af0d2350d4287526 Mon Sep 17 00:00:00 2001 From: v-shalinir Date: Wed, 22 Jan 2025 13:40:26 +0530 Subject: [PATCH 6/7] Update teams-faq.md --- msteams-platform/teams-faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/msteams-platform/teams-faq.md b/msteams-platform/teams-faq.md index 708345e828a..c7f98cf7a24 100644 --- a/msteams-platform/teams-faq.md +++ b/msteams-platform/teams-faq.md @@ -1249,4 +1249,4 @@ To enable the app to become eligible while minimizing disruption, the following | 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](appsource.microsoft.com) page to the AppSource page for the new app. | AppSource engineering | +| 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 | From d93beeb9d6ad21e9dd41a43cc29d0d6553b4bbaa Mon Sep 17 00:00:00 2001 From: v-shalinir Date: Wed, 22 Jan 2025 13:48:41 +0530 Subject: [PATCH 7/7] Update teams-faq.md --- msteams-platform/teams-faq.md | 62 ++++++++++++++++++----------------- 1 file changed, 32 insertions(+), 30 deletions(-) diff --git a/msteams-platform/teams-faq.md b/msteams-platform/teams-faq.md index c7f98cf7a24..0ff2c62e74e 100644 --- a/msteams-platform/teams-faq.md +++ b/msteams-platform/teams-faq.md @@ -968,6 +968,38 @@ The following resources can also assist:
+## Publisher verification for Teams apps + +
+
+How can I ensure publisher verification for my app if I have a personal or consumer (MSA) user account? + +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:rmandal@microsoft.com) 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:teamsubm@microsoft.com) 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 | + +
+ ## Single sign-on
@@ -1220,33 +1252,3 @@ Shared references to deploy the code using toolkit: You can call Graph API to get the app user's profile photo.
- -## Publisher verification for Teams apps - -
-
-How can I ensure publisher verification for my app if I have a personal or consumer (MSA) user account? - -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:rmandal@microsoft.com) 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:teamsubm@microsoft.com) 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 |