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/mark-app-as-publisher-verified.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Mark an app as publisher verified
2
+
title: Mark an app as publisher verified | Azure
3
3
description: Describes how to mark an app as publisher verified. When an application is marked as publisher verified, it means that the publisher has verified their identity using a Microsoft Partner Network account that has completed the verification process and has associated this MPN account with their application registration.
4
4
services: active-directory
5
5
author: rwike77
@@ -37,27 +37,27 @@ Make sure you have met the [pre-requisites](publisher-verification-overview.md#r
37
37
38
38
1. Ensure you are signed in with an organizational (Azure AD) account that is authorized to make changes to the app(s) you want to mark as Publisher Verified and on the MPN Account in Partner Center.
39
39
40
-
1. In Azure AD this user must either be the Owner of the app or have one of the following roles: Application Admin, Cloud Application Admin, Global Admin.
40
+
- In Azure AD this user must either be the Owner of the app or have one of the following roles: Application Admin, Cloud Application Admin, Global Admin.
41
41
42
-
1. In Partner Center this user must have of the following roles: MPN Admin, Accounts Admin, or a Global Admin (this is a shared role mastered in Azure AD).
42
+
- In Partner Center this user must have of the following roles: MPN Admin, Accounts Admin, or a Global Admin (this is a shared role mastered in Azure AD).
43
43
44
44
1. Navigate to the preview version of the App Registration portal:
45
45
46
46
1. Click on an app you would like to mark as Publisher Verified and open the Branding blade.
47
47
48
48
1. Ensure the app’s Publisher Domain is set appropriately. This domain must be:
49
49
50
-
1. Be added to the Azure AD tenant as a DNS-verified custom domain,
50
+
- Be added to the Azure AD tenant as a DNS-verified custom domain,
51
51
52
-
1. Match the domain of the email address used during the verification process for your MPN account.
52
+
- Match the domain of the email address used during the verification process for your MPN account.
53
53
54
54
1. Click **Add MPN ID to verify publisher** near the bottom of the page.
55
55
56
56
1. Enter your **MPN ID**. This MPN ID must be for:
57
57
58
-
1. A valid Microsoft Partner Network account that has completed the verification process.
58
+
- A valid Microsoft Partner Network account that has completed the verification process.
59
59
60
-
1. The Partner global account (PGA) for your organization.
60
+
- The Partner global account (PGA) for your organization.
Copy file name to clipboardExpand all lines: articles/active-directory/develop/publisher-verification-overview.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Publisher verification overview
2
+
title: Publisher verification overview | Azure
3
3
description: Provides an overview of the publisher verification program (preview) for the Microsoft identity platform. Lists the benefits, program requirements, and frequently asked questions. When an application is marked as publisher verified, it means that the publisher has verified their identity using a Microsoft Partner Network account that has completed the verification process and has associated this MPN account with their application registration.
4
4
services: active-directory
5
5
author: rwike77
@@ -36,19 +36,19 @@ Publisher verification provides the following benefits:
36
36
## Requirements
37
37
There are a few pre-requisites for publisher verification, some of which will have already been completed by many Microsoft partners. They are:
38
38
39
-
1. 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.
39
+
- 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.
40
40
41
-
1. An Azure AD tenant with a DNS-verified [custom domain](/azure/active-directory/fundamentals/add-custom-domain). The custom domain must match the domain of the email address used during verification in the previous step.
41
+
- An Azure AD tenant with a DNS-verified [custom domain](/azure/active-directory/fundamentals/add-custom-domain). The custom domain must match the domain of the email address used during verification in the previous step.
42
42
43
-
1. An app registered in an Azure AD tenant, with a [Publisher Domain](howto-configure-publisher-domain.md) configured using the same domain as previously used.
43
+
- An app registered in an Azure AD tenant, with a [Publisher Domain](howto-configure-publisher-domain.md) configured using the same domain as previously used.
44
44
45
-
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.
45
+
- 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.
46
46
47
-
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.
47
+
- 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.
48
48
49
-
1. In Partner Center this user must have 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).
49
+
- In Partner Center this user must have 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).
50
50
51
-
1. The publisher agrees to the [Microsoft identity platform for developers Terms of Use]
51
+
- The publisher agrees to the [Microsoft identity platform for developers Terms of Use]
52
52
(/legal/microsoft-identity-platform/terms-of-use)
53
53
54
54
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.
description: Describes how to troubleshoot publisher verification (preview) for Microsoft identity platform by calling Microsoft Graph APIs.
4
4
services: active-directory
5
5
author: rwike77
@@ -17,44 +17,44 @@ ms.reviewer: jesakowi
17
17
# Troubleshoot publisher verification (preview)
18
18
If you are unable to complete the process or are experiencing unexpected behavior with [publisher verification (preview)](publisher-verification-overview.md), you should start by doing the following if you are receiving errors or seeing unexpected behavior:
19
19
20
-
1. Review the [requirements](publisher-verification-overview.md#requirements) and ensure they have all been met
20
+
1. Review the [requirements](publisher-verification-overview.md#requirements) and ensure they have all been met.
21
21
22
-
1. Review the instructions to [mark an app as publisher verified](mark-app-as-publisher-verified.md) and ensure all steps have been performed successfully
22
+
1. Review the instructions to [mark an app as publisher verified](mark-app-as-publisher-verified.md) and ensure all steps have been performed successfully.
23
23
24
-
1. Review the list of [common issues](#common-issues)
24
+
1. Review the list of [common issues](#common-issues).
25
25
26
26
1. Reproduce the request using [Graph Explorer](#making-microsoft-graph-api-calls) to gather additional info and rule out any issues in the UI.
27
27
28
28
## Common Issues
29
29
Below are some common issues that may occur during the process.
30
30
31
31
-**I don’t know my Microsoft Partner Network ID (MPN ID) or I don’t who the primary contact for the account is**
32
-
1. Navigate to the [MPN enrollment page](https://partner.microsoft.com/dashboard/account/v3/enrollment/joinnow/basicpartnernetwork/new)
33
-
1. Sign in with a user account in the org's primary Azure AD tenant
34
-
1. If an MPN account already exists, this will be recognized and you will be added to the account
35
-
1. Navigate to the [partner profile page](https://partner.microsoft.com/en-us/pcv/accountsettings/connectedpartnerprofile) where the MPN ID and primary account contact will be listed
32
+
1. Navigate to the [MPN enrollment page](https://partner.microsoft.com/dashboard/account/v3/enrollment/joinnow/basicpartnernetwork/new)
33
+
1. Sign in with a user account in the org's primary Azure AD tenant
34
+
1. If an MPN account already exists, this will be recognized and you will be added to the account
35
+
1. Navigate to the [partner profile page](https://partner.microsoft.com/en-us/pcv/accountsettings/connectedpartnerprofile) where the MPN ID and primary account contact will be listed
36
36
37
37
-**I don’t know who my Azure AD Global Admin (also known as Company Admin or Tenant Admin) is, how do I find them? What about the App Administrator, or a different admin role?**
38
-
1. Sign in to the [Azure AD Portal](https://aad.portal.azure.com) using a user account in your organization's primary tenant
39
-
1. Navigate to [Role Management](https://aad.portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/RolesAndAdministrators)
40
-
1. Click “Global Administrator”, or the desired admin role
41
-
1. The list of users assigned that role will be displayed
38
+
1. Sign in to the [Azure AD Portal](https://aad.portal.azure.com) using a user account in your organization's primary tenant
39
+
1. Navigate to [Role Management](https://aad.portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/RolesAndAdministrators)
40
+
1. Click “Global Administrator”, or the desired admin role
41
+
1. The list of users assigned that role will be displayed
42
42
43
43
-**I don't know who the admin(s) for my MPN account are**
44
-
1. Go to the [MPN User Management page](https://partner.microsoft.com/en-us/pcv/users) and filter the user list to see what users are in various admin roles.
44
+
Go to the [MPN User Management page](https://partner.microsoft.com/en-us/pcv/users) and filter the user list to see what users are in various admin roles.
45
45
46
46
-**I am getting an error saying that my MPN ID is invalid or that I do not have access to it.**
47
-
1. Go to your [partner profile](https://partner.microsoft.com/en-us/pcv/accountsettings/connectedpartnerprofile) and verify that:
48
-
1. The MPN ID is correct.
49
-
1. There are no errors or “pending actions” shown, and the verification status under Legal business profile and Partner info both say “authorized” or “success”.
50
-
1. Go to the [MPN tenant management page](https://partner.microsoft.com/en-us/dashboard/account/v3/tenantmanagement) and confirm that the tenant the app is registered in and that you are signing with a user account from is on the list of associated tenants.
51
-
1. Go to the [MPN User Management page](https://partner.microsoft.com/en-us/pcv/users) and confirm the user you are signing in as is either a Global Admin, MPN Admin, or Accounts Admin.
47
+
1. Go to your [partner profile](https://partner.microsoft.com/en-us/pcv/accountsettings/connectedpartnerprofile) and verify that:
48
+
- The MPN ID is correct.
49
+
- There are no errors or “pending actions” shown, and the verification status under Legal business profile and Partner info both say “authorized” or “success”.
50
+
1. Go to the [MPN tenant management page](https://partner.microsoft.com/en-us/dashboard/account/v3/tenantmanagement) and confirm that the tenant the app is registered in and that you are signing with a user account from is on the list of associated tenants.
51
+
1. Go to the [MPN User Management page](https://partner.microsoft.com/en-us/pcv/users) and confirm the user you are signing in as is either a Global Admin, MPN Admin, or Accounts Admin.
52
52
53
53
-**When I sign into the Azure AD portal, I do not see any apps registered. Why?**
54
-
Your app registrations may have been created using a different user account, or in a different tenant. Ensure you are signed in with the correct account in the tenant where your app registrations were created.
54
+
Your app registrations may have been created using a different user account, or in a different tenant. Ensure you are signed in with the correct account in the tenant where your app registrations were created.
55
55
56
56
-**How do I know who the owner of an app registration in Azure AD is?**
57
-
When signed into a tenant where the app is registered, navigate to the App Registrations blade, click an app, and then click Owners.
57
+
When signed into a tenant where the app is registered, navigate to the App Registrations blade, click an app, and then click Owners.
0 commit comments