You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/develop/publisher-verification-overview.md
+17-19Lines changed: 17 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,9 @@ ms.reviewer: jesakowi
16
16
17
17
# Publisher verification
18
18
19
-
Publisher verification allows developers with a verified (or “vetted”) Microsoft Partner Center (MPN) account to mark one or more app registrations as Publisher Verified.
19
+
Publisher verification allows developers with a verified (or “vetted”) Microsoft Partner Center (MPN) account to mark one or more app registrations as publisher verified.
20
+
21
+
This feature is primarily targeted at 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 to request access to data using APIs like [Microsoft Graph](https://developer.microsoft.com/graph/).
20
22
21
23
## Benefits
22
24
Publisher verification provides the following benefits:
@@ -28,10 +30,6 @@ Publisher verification provides the following benefits:
28
30
29
31
- Risk evaluation- Microsoft’s detections for “risky” consent requests will include publisher verification as a signal.
30
32
31
-
## What types of apps is this relevant for?
32
-
33
-
This feature is primarily targeted at 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 to request access to data using APIs like [Microsoft Graph](https://developer.microsoft.com/graph/).
34
-
35
33
## Requirements
36
34
There are a few pre-requisites for publisher verification, some of which will have already been completed by many Microsoft partners. They are:
37
35
@@ -57,27 +55,27 @@ If you cannot currently meet these requirements, or don’t know if you can, you
57
55
58
56
-**When will other experiences start showing the badge or using verification status?**
59
57
60
-
- The Enterprise Apps experience will start showing an indication of Publisher Verified apps by Public Preview in mid-May. Admins will be able to set policies using this information in a similar timeframe.
58
+
- The Enterprise Apps experience will start showing an indication of publisher verified apps by Public Preview in mid-May. Admins will be able to set policies using this information in a similar timeframe.
61
59
62
60
- Dates on additional UI surfaces have not been announced.
63
61
64
-
- Microsoft’s Risk-Based Consent capability will start factoring in verification status immediately.
62
+
- Microsoft’s risk-based consent capability will start factoring in verification status immediately.
65
63
66
64
-**I don’t know my MPN ID- where do I find it?** See the [Microsoft Partner Network FAQ](https://support.microsoft.com/help/4515614/frequently-asked-questions-joining-the-microsoft-partner-network-mpn) for guidance on how to find your organization’s MPN ID.
67
65
68
-
-**How do I make sure my MPN verification (also known as vetting/authorization) is complete in Partner Center?** If you are unsure whether vetting has been completed, you can check the [Partner profile](https://partner.microsoft.com/pcv/accountsettings/connectedpartnerprofile) page in Partner Center. It will say “Verification status: Authorized”.
66
+
-**How do I make sure my MPN verification (also known as vetting/authorization) is complete in Partner Center?** If you are unsure whether vetting has been completed, you can check the [partner profile](https://partner.microsoft.com/pcv/accountsettings/connectedpartnerprofile) page in Partner Center. It will say “Verification status: Authorized”.
69
67
70
68
-**I do not have an MPN account and need to create one. How long will verification take?** This process is often quick, especially if you have enrolled in other Microsoft programs before. However, at times of increased load, you should expect three weeks for a net-new vetting to be processed. See [Verify your account information](/partner-center/verification-responses) or [Vetting process for Partners in Partner Center](https://support.microsoft.com/help/4522960/vetting-process-for-partners-in-partner-center) for more details.
71
69
72
-
-**Do I need to complete this process again for each app that my organization publishes?** Most of the steps in this process only need to be performed once. For example, you will only need a single verified/vetted MPN ID. However, this MPN ID will need to be associated with each app you want to mark as Publisher Verified. You can use PowerShell or Microsoft Graph to help mark multiple apps verified in bulk.
70
+
-**Do I need to complete this process again for each app that my organization publishes?** Most of the steps in this process only need to be performed once. For example, you will only need a single verified/vetted MPN ID. However, this MPN ID will need to be associated with each app you want to mark as publisher verified. You can use PowerShell or Microsoft Graph to help mark multiple apps verified in bulk.
73
71
74
72
-**Will I have to go through parts of this process again in the future to renew my app’s publisher verification status?** As of Private Preview, the renewal/attestation process is not yet defined. Microsoft reserves the right to add a required renewal process in the future, which may involve one or more steps needing to be performed again.
75
73
76
-
-**I successfully marked my app Publisher Verified, but the verified Publisher display name is showing up incorrectly. Why?** The display name property is pulled directly from your MPN account in Partner Center when you mark your app registration as Publisher Verified. If it is incorrect, that means it was set incorrectly in Partner Center. You can confirm the display name by visiting the [Partner profile](https://partner.microsoft.com/pcv/accountsettings/connectedpartnerprofile) page in Partner Center. See the next question for instructions on updating it, if necessary.
74
+
-**I successfully marked my app publisher verified, but the verified Publisher display name is showing up incorrectly. Why?** The display name property is pulled directly from your MPN account in Partner Center when you mark your app registration as publisher verified. If it is incorrect, that means it was set incorrectly in Partner Center. You can confirm the display name by visiting the [partner profile](https://partner.microsoft.com/pcv/accountsettings/connectedpartnerprofile) page in Partner Center. See the next question for instructions on updating it, if necessary.
77
75
78
76
-**My organization’s name has changed, or was incorrect initially, and needs to be updated. How do I do this?** You can update your organization’s name on the [Partner profile](https://partner.microsoft.com/pcv/accountsettings/connectedpartnerprofile) page in Partner Center. After doing this, you will need to perform the initial [verification process](/partner-center/verification-responses) again. After that completes, you will need to update your Verified Publisher information in Azure AD using the “update” button on the Branding blade where you initially performed verification.
79
77
80
-
-**My MPN ID has changed, how do I update it on my app(s) in Azure AD?** You will need to remove your old MPN ID from each app that was previously marked as Publisher Verified and go through the binding process again with the new one. The same requirements will apply as the initial process.
78
+
-**My MPN ID has changed, how do I update it on my app(s) in Azure AD?** You will need to remove your old MPN ID from each app that was previously marked as publisher verified and go through the binding process again with the new one. The same requirements will apply as the initial process.
81
79
82
80
-**How much does this cost? Does it require any license?** Microsoft does not charge developers for publisher verification and it does not require any specific license.
83
81
@@ -96,23 +94,23 @@ If you cannot currently meet these requirements, or don’t know if you can, you
96
94
97
95
**What information does publisher verification provide to customers?**
98
96
99
-
The primary goal of publisher verification (Preview) is to help admins and end users better understand the authenticity of application developers integrating with the Microsoft identity platform. In other words, is the publisher a known source or a bad actor disguising themselves as a well-known publisher? When an application is marked as Publisher Verified, it means that the publisher has verified their identity using their Microsoft Partner Network (MPN) account and has associated this MPN account with their application registration.
97
+
The primary goal of publisher verification (Preview) is to help admins and end users better understand the authenticity of application developers integrating with the Microsoft identity platform. In other words, is the publisher a known source or a bad actor disguising themselves as a well-known publisher? When an application is marked as publisher verified, it means that the publisher has verified their identity using their Microsoft Partner Network (MPN) account and has associated this MPN account with their application registration.
100
98
101
99
**What information does Publisher Verification not provide?**
102
100
103
-
When an application is marked Publisher Verified this does not indicate whether the application or its publisher has achieved any specific certifications, complies with industry standards, adheres to best practices, etc. Other Microsoft programs do provide this information, including [Microsoft 365 App Certification](/microsoft-365-app-certification/overview).
101
+
When an application is marked publisher verified this does not indicate whether the application or its publisher has achieved any specific certifications, complies with industry standards, adheres to best practices, etc. Other Microsoft programs do provide this information, including [Microsoft 365 App Certification](/microsoft-365-app-certification/overview).
104
102
105
-
**How does a publisher obtain a Verified Publisher status?**
103
+
**How does a publisher obtain a verified publisher status?**
106
104
107
-
Publisher Verification is performed on an application-by- application basis so a Publisher must verify each application where they would like a Publisher Verification badge to appear.
105
+
Publisher verification is performed on an application-by- application basis so a publisher must verify each application where they would like a publisher verification badge to appear.
108
106
109
-
For a publisher to mark an app as Publisher Verified, the following requirements must be met:
107
+
For a publisher to mark an app as publisher verified, the following requirements must be met:
110
108
111
109
1. The publisher must have a valid [Microsoft Partner Network account](https://partner.microsoft.com/membership).
112
110
113
111
1. This account must have completed the [MPN account verification](/partner-center/verification-responses) process.
114
112
115
-
1. This account must be the Partner global account (PGA) for the publisher’s organization.
113
+
1. This account must be the partner global account (PGA) for the publisher’s organization.
116
114
117
115
1. The app must be registered in an Azure Active Directory tenant.
118
116
@@ -126,9 +124,9 @@ For a publisher to mark an app as Publisher Verified, the following requirements
126
124
127
125
1. The user performing verification must be authorized to make changes to both the app registration in Azure AD and the MPN account in Partner Center.
128
126
129
-
1. In Azure AD this user must either be the Owner of the app or have one of the following [roles](/azure/active-directory/users-groups-roles/directory-assign-admin-roles): Application Admin, Cloud Application Admin, Global Admin.
127
+
1. In Azure AD this user must either be the owner of the app or have one of the following [roles](/azure/active-directory/users-groups-roles/directory-assign-admin-roles): application admin, cloud application admin, global admin.
130
128
131
-
1. In Partner Center this user must have one of the following [roles](/partner-center/permissions-overview): MPN Admin, Accounts Admin, or a Global Admin (this is a shared role mastered in Azure AD).
129
+
1. In Partner Center this user must have one of the following [roles](/partner-center/permissions-overview): MPN admin, accounts admin, or a global admin (this is a shared role mastered in Azure AD).
0 commit comments