Skip to content

Commit cd7fd02

Browse files
authored
PR review edit
1 parent 51cb63d commit cd7fd02

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,9 +23,11 @@ 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)
27-
> [!NOTE] We recently changed the color of the “verified” badge from blue to grey. We will revert that change sometime in the last half of February so that the "verified" badge will show up as blue
2828

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.
2931
3032
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/).
3133

0 commit comments

Comments
 (0)