Skip to content

Commit ea02d75

Browse files
committed
resolved blocking issues
1 parent 03cabe8 commit ea02d75

File tree

3 files changed

+35
-35
lines changed

3 files changed

+35
-35
lines changed

articles/active-directory/develop/mark-app-as-publisher-verified.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Mark an app as publisher verified
2+
title: Mark an app as publisher verified | Azure
33
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.
44
services: active-directory
55
author: rwike77
@@ -37,27 +37,27 @@ Make sure you have met the [pre-requisites](publisher-verification-overview.md#r
3737

3838
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.
3939

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.
4141

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).
4343

4444
1. Navigate to the preview version of the App Registration portal:
4545

4646
1. Click on an app you would like to mark as Publisher Verified and open the Branding blade.
4747

4848
1. Ensure the app’s Publisher Domain is set appropriately. This domain must be:
4949

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,
5151

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.
5353

5454
1. Click **Add MPN ID to verify publisher** near the bottom of the page.
5555

5656
1. Enter your **MPN ID**. This MPN ID must be for:
5757

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.
5959

60-
1. The Partner global account (PGA) for your organization.
60+
- The Partner global account (PGA) for your organization.
6161

6262
1. Click **Verify and save**.
6363

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

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Publisher verification overview
2+
title: Publisher verification overview | Azure
33
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.
44
services: active-directory
55
author: rwike77
@@ -36,19 +36,19 @@ Publisher verification provides the following benefits:
3636
## Requirements
3737
There are a few pre-requisites for publisher verification, some of which will have already been completed by many Microsoft partners. They are:
3838

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.
4040

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.
4242

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.
4444

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.
4646

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.
4848

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).
5050

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]
5252
(/legal/microsoft-identity-platform/terms-of-use)
5353

5454
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.

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

Lines changed: 20 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Troubleshoot publisher verification
2+
title: Troubleshoot publisher verification | Azure
33
description: Describes how to troubleshoot publisher verification (preview) for Microsoft identity platform by calling Microsoft Graph APIs.
44
services: active-directory
55
author: rwike77
@@ -17,44 +17,44 @@ ms.reviewer: jesakowi
1717
# Troubleshoot publisher verification (preview)
1818
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:
1919

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.
2121

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.
2323

24-
1. Review the list of [common issues](#common-issues)
24+
1. Review the list of [common issues](#common-issues).
2525

2626
1. Reproduce the request using [Graph Explorer](#making-microsoft-graph-api-calls) to gather additional info and rule out any issues in the UI.
2727

2828
## Common Issues
2929
Below are some common issues that may occur during the process.
3030

3131
- **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
3636

3737
- **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
4242

4343
- **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.
4545

4646
- **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.
5252

5353
- **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.
5555

5656
- **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.
5858

5959
## Making Microsoft Graph API calls
6060

0 commit comments

Comments
 (0)