Skip to content

Commit 1064f84

Browse files
authored
Merge pull request #87237 from arpitha-dhanapathi/patch-2
Update publisher-verification-overview.md
2 parents 8356bbd + 463b7b2 commit 1064f84

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

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

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,8 +23,12 @@ Publisher verification helps admins and end users understand the authenticity of
2323
When an application is marked as publisher verified, it means that the publisher has verified their identity using a [Microsoft Partner Network](https://partner.microsoft.com/membership) account that has completed the [verification](/partner-center/verification-responses) process and has associated this MPN account with their application registration.
2424

2525
A blue "verified" badge appears on the Azure AD consent prompt and other screens:
26+
2627
![Consent prompt](./media/publisher-verification-overview/consent-prompt.png)
2728

29+
> [!NOTE]
30+
> We recently changed the color of the "verified" badge from blue to gray. We will revert that change sometime in the last half of February 2022, so the "verified" badge will be blue.
31+
2832
This feature is primarily for developers building multi-tenant apps that leverage [OAuth 2.0 and OpenID Connect](active-directory-v2-protocols.md) with the [Microsoft identity platform](v2-overview.md). These apps can sign users in using OpenID Connect, or they may use OAuth 2.0 to request access to data using APIs like [Microsoft Graph](https://developer.microsoft.com/graph/).
2933

3034
## Benefits

0 commit comments

Comments
 (0)