Skip to content

Commit f8c0842

Browse files
authored
Merge pull request #196671 from arpitha-dhanapathi/patch-1
Update publisher-verification-overview.md
2 parents e28f59e + fb041c0 commit f8c0842

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

articles/active-directory/develop/publisher-verification-overview.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,13 +38,14 @@ Publisher verification provides the following benefits:
3838

3939
> [!NOTE]
4040
> - Starting in November 2020, end users will no longer be able to grant consent to most newly registered multi-tenant apps without verified publishers if [risk-based step-up consent](../manage-apps/configure-risk-based-step-up-consent.md) is enabled. This will apply to apps that are registered after November 8, 2020, use OAuth2.0 to request permissions beyond basic sign-in and read user profile, and request consent from users in different tenants than the one the app is registered in. A warning will be displayed on the consent screen informing users that these apps are risky and are from unverified publishers.
41-
> - Publisher verification is not supported in national clouds. Applications registered in national cloud tenants can't be publisher-verified at this time.
4241
4342
## Requirements
4443
There are a few pre-requisites for publisher verification, some of which will have already been completed by many Microsoft partners. They are:
4544

4645
- An MPN ID for a valid [Microsoft Partner Network](https://partner.microsoft.com/membership) account that has completed the [verification](/partner-center/verification-responses) process. This MPN account must be the [Partner global account (PGA)](/partner-center/account-structure#the-top-level-is-the-partner-global-account-pga) for your organization.
4746

47+
- The application to be publisher verified must be registered using a Azure AD account. Applications registered using a Microsoft personal account aren't supported for publisher verification.
48+
4849
- The Azure AD tenant where the app is registered must be associated with the Partner Global account. If it's not the primary tenant associated with the PGA, follow the steps to [set up the MPN partner global account as a multi-tenant account and associate the Azure AD tenant](/partner-center/multi-tenant-account#add-an-azure-ad-tenant-to-your-account).
4950

5051
- An app registered in an Azure AD tenant, with a [Publisher Domain](howto-configure-publisher-domain.md) configured.
@@ -63,6 +64,9 @@ There are a few pre-requisites for publisher verification, some of which will ha
6364

6465
Developers who have already met these pre-requisites can get verified in a matter of minutes. If the requirements have not been met, getting set up is free.
6566

67+
## National Clouds and Publisher Verification
68+
Publisher verification is currently not supported in national clouds. Applications registered in national cloud tenants can't be publisher-verified at this time.
69+
6670
## Frequently asked questions
6771
Below are some frequently asked questions regarding the publisher verification program. For FAQs related to the requirements and the process, see [mark an app as publisher verified](mark-app-as-publisher-verified.md).
6872

0 commit comments

Comments
 (0)