Merge pull request #249667 from davidmu1/removeaadportalreference1

removed references to aad.portal.azure.com

Author: prmerger-automator[bot]

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

@@ -18,27 +18,24 @@ ms.reviewer: xurobert
 If you're unable to complete the process or are experiencing unexpected behavior with [publisher verification](publisher-verification-overview.md), you should start by doing the following if you're receiving errors or seeing unexpected behavior: 
 
 1. Review the [requirements](publisher-verification-overview.md#requirements) and ensure they've all been met.
-
-2. Review the instructions to [mark an app as publisher verified](mark-app-as-publisher-verified.md) and ensure all steps have been performed successfully.
-
-3. Review the list of [common issues](#common-issues).
-
-4. Reproduce the request using [Graph Explorer](#making-microsoft-graph-api-calls) to gather more info and rule out any issues in the UI.
+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.
+1. Review the list of [common issues](#common-issues).
+1. Reproduce the request using [Graph Explorer](#making-microsoft-graph-api-calls) to gather more info and rule out any issues in the UI.
 
 ## Common Issues
 Below are some common issues that may occur during the process. 
 
 - **I don’t know my Cloud Partner Program ID (Partner One ID) or I don’t know who the primary contact for the account is.** 
     1. Navigate to the [Cloud Partner Program enrollment page](https://partner.microsoft.com/dashboard/account/v3/enrollment/joinnow/basicpartnernetwork/new).
-    2. Sign in with a user account in the org's primary Azure AD tenant. 
-    3. If an Cloud Partner Program account already exists, this is recognized and you are added to the account. 
-    4. Navigate to the [partner profile page](https://partner.microsoft.com/pcv/accountsettings/connectedpartnerprofile) where the Partner One ID and primary account contact will be listed.
+    1. Sign in with a user account in the org's primary Azure AD tenant. 
+    1. If an Cloud Partner Program account already exists, this is recognized and you are added to the account. 
+    1. Navigate to the [partner profile page](https://partner.microsoft.com/pcv/accountsettings/connectedpartnerprofile) where the Partner One ID and primary account contact will be listed.
 
 - **I don’t know who my Azure AD Global Administrator (also known as company admin or tenant admin) is, how do I find them? What about the Application Administrator or Cloud Application Administrator?**
-    1. Sign in to the [Azure portal](https://portal.azure.com) using a user account in your organization's primary tenant.
-    1. Browse to **Azure Active Directory** > [Roles and administrators](https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/RolesAndAdministrators).
-    3. Select the desired admin role.
-    4. The list of users assigned that role will be displayed.
+    1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least an [Cloud Application Adminstrator](../roles/permissions-reference.md#cloud-application-administrator).
+    1. Browse to **Identity** > **Roles & admins** > **Roles & admins**.
+    1. Select the desired admin role.
+    1. The list of users assigned that role will be displayed.
 
 - **I don't know who the admin(s) for my CPP account are**
     Go to the [CPP User Management page](https://partner.microsoft.com/pcv/users) and filter the user list to see what users are in various admin roles.
@@ -150,9 +147,9 @@ Most commonly caused by the signed-in user not being a member of the proper role
 1. Go to your [partner profile](https://partner.microsoft.com/pcv/accountsettings/connectedpartnerprofile) and verify that: 
 
     - The Partner One ID is correct. 
-    - There are no errors or “pending actions” shown, and the verification status under Legal business profile and Partner info both say “authorized” or “success”.
-2. Go to the [CPP tenant management page](https://partner.microsoft.com/dashboard/account/v3/tenantmanagement) and confirm that the tenant the app is registered in and that you're signing with a user account from is on the list of associated tenants. To add another tenant, follow the [multi-tenant-account instructions](/partner-center/multi-tenant-account). All Global Admins of any tenant you add will be granted Global Administrator privileges on your Partner Center account.
-3. Go to the [CPP User Management page](https://partner.microsoft.com/pcv/users) and confirm the user you're signing in as is either a Global Administrator, MPN Admin, or Accounts Admin. To add a user to a role in Partner Center, follow the instructions for [creating user accounts and setting permissions](/partner-center/create-user-accounts-and-set-permissions).
+    - There are no errors or "pending actions" shown, and the verification status under Legal business profile and Partner info both say "authorized" or "success".
+1. Go to the [CPP tenant management page](https://partner.microsoft.com/dashboard/account/v3/tenantmanagement) and confirm that the tenant the app is registered in and that you're signing with a user account from is on the list of associated tenants. To add another tenant, follow the [multi-tenant-account instructions](/partner-center/multi-tenant-account). All Global Admins of any tenant you add will be granted Global Administrator privileges on your Partner Center account.
+1. Go to the [CPP User Management page](https://partner.microsoft.com/pcv/users) and confirm the user you're signing in as is either a Global Administrator, MPN Admin, or Accounts Admin. To add a user to a role in Partner Center, follow the instructions for [creating user accounts and setting permissions](/partner-center/create-user-accounts-and-set-permissions).
 
 ### MPNGlobalAccountNotFound
 
@@ -161,8 +158,8 @@ The Partner One ID you provided (`MPNID`) isn't valid. Provide a valid Partner O
 Most commonly caused when an Partner One ID is provided which corresponds to a Partner Location Account (PLA). Only Partner Global Accounts are supported. See [Partner Center account structure](/partner-center/account-structure) for more details.
 
 **Remediation Steps**
-1. Navigate to your [partner profile](https://partner.microsoft.com/pcv/accountsettings/connectedpartnerprofile) > Identifiers blade > Microsoft Cloud Partners Program Tab
-2. Use the Partner ID with type PartnerGlobal
+1. Navigate to your [partner profile](https://partner.microsoft.com/pcv/accountsettings/connectedpartnerprofile) > **Identifiers blade** > **Microsoft Cloud Partners Program Tab**.
+1. Use the Partner ID with type PartnerGlobal.
 
 ### MPNAccountInvalid
 
@@ -171,8 +168,8 @@ The Partner One ID you provided (`MPNID`) isn't valid. Provide a valid Partner O
 Most commonly caused by the wrong Partner One ID being provided.
 
 **Remediation Steps**
-1. Navigate to your [partner profile](https://partner.microsoft.com/pcv/accountsettings/connectedpartnerprofile) > Identifiers blade > Microsoft Cloud Partners Program Tab
-2. Use the Partner ID with type PartnerGlobal
+1. Navigate to your [partner profile](https://partner.microsoft.com/pcv/accountsettings/connectedpartnerprofile) > **Identifiers blade** > **Microsoft Cloud Partners Program Tab**.
+1. Use the Partner ID with type PartnerGlobal.
 
 ### MPNAccountNotVetted
 
@@ -182,7 +179,7 @@ Most commonly caused by when the CPP account hasn't completed the [verification]
 
 **Remediation Steps**
 1. Navigate to your [partner profile](https://partner.microsoft.com/pcv/accountsettings/connectedpartnerprofile) and verify that there are no errors or **pending actions** shown, and that the verification status under Legal business profile and Partner info both say **authorized** or **success**.
-2. If not, view pending action items in Partner Center and troubleshoot with [here](/partner-center/verification-responses)
+1. If not, view pending action items in Partner Center and troubleshoot with [here](/partner-center/verification-responses).
 
 ### NoPublisherIdOnAssociatedMPNAccount
 
@@ -191,8 +188,8 @@ The Partner One ID you provided (`MPNID`) isn't valid. Provide a valid Partner O
 Most commonly caused by the wrong Partner One ID being provided.
 
 **Remediation Steps**
-1. Navigate to your [partner profile](https://partner.microsoft.com/pcv/accountsettings/connectedpartnerprofile) > Identifiers blade > Microsoft Cloud Partners Program Tab
-2. Use the Partner ID with type PartnerGlobal
+1. Navigate to your [partner profile](https://partner.microsoft.com/pcv/accountsettings/connectedpartnerprofile) > **Identifiers blade** > **Microsoft Cloud Partners Program Tab**.
+1. Use the Partner ID with type PartnerGlobal.
 
 ### MPNIdDoesNotMatchAssociatedMPNAccount
 
@@ -201,19 +198,20 @@ The Partner One ID you provided (`MPNID`) isn't valid. Provide a valid Partner O
 Most commonly caused by the wrong Partner One ID being provided.
 
 **Remediation Steps**
-1. Navigate to your [partner profile](https://partner.microsoft.com/pcv/accountsettings/connectedpartnerprofile) > Identifiers blade > Microsoft Cloud Partners Program Tab
-2. Use the Partner ID with type PartnerGlobal
+1. Navigate to your [partner profile](https://partner.microsoft.com/pcv/accountsettings/connectedpartnerprofile) > **Identifiers blade** > **Microsoft Cloud Partners Program Tab**.
+1. Use the Partner ID with type PartnerGlobal.
 
 ### ApplicationNotFound
 
-The target application (`AppId`) can’t be found. Provide a valid application ID and try again.
+The target application (`AppId`) can't be found. Provide a valid application ID and try again.
 
 Most commonly caused when verification is being performed via Graph API, and the ID of the application provided is incorrect. 
 
 **Remediation Steps**
-1. The Object ID of the application must be provided, not the AppId/ClientId. See **id** on the list of application properties [here](/graph/api/resources/application)
-2. Log in to [Azure Active Directory](https://aad.portal.azure.com/) with a user account in your organization's primary tenant > Azure Active Directory > App Registrations blade
-3. Find your app's registration to view the Object ID
+1. The Object ID of the application must be provided, not the AppId/ClientId. See **id** on the list of application properties [here](/graph/api/resources/application).
+1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least an [Cloud Application Administrator](../roles/permissions-reference.md#cloud-application-administrator).
+1. Browse to **Identity** > **Applications** > **Application registrations**.
+1. Find your app's registration to view the Object ID.
 
 
 ### ApplicationObjectisInvalid 
@@ -223,9 +221,10 @@ The target application's object ID is invalid. Please provide a valid ID and try
 Most commonly caused when the verification is being performed via Graph API, and the ID of the application provided does not exist. 
 
 **Remediation Steps**
-1. The Object ID of the application must be provided, not the AppId/ClientId. See **id** on the list of application properties [here](/graph/api/resources/application)
-2. Log in to [Azure Active Directory](https://aad.portal.azure.com/) with a user account in your organization's primary tenant > Azure Active Directory > App Registrations blade
-3. Find your app's registration to view the Object ID
+1. The Object ID of the application must be provided, not the AppId/ClientId. See **id** on the list of application properties [here](/graph/api/resources/application).
+1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least an [Cloud Application Administrator](../roles/permissions-reference.md#cloud-application-administrator).
+1. Browse to **Identity** > **Applications** > **Application registrations**.
+1. Find your app's registration to view the Object ID.
 
 
 ### B2CTenantNotAllowed
@@ -243,7 +242,7 @@ The target application (`AppId`) must have a Publisher Domain set. Set a Publish
 Occurs when a [Publisher Domain](howto-configure-publisher-domain.md) isn't configured on the app.
 
 **Remediation Steps**
-1. Follow the directions [here](./howto-configure-publisher-domain.md#set-a-publisher-domain-in-the-azure-portal) to set a Publisher Domain
+Follow the directions [here](./howto-configure-publisher-domain.md#set-a-publisher-domain-in-the-azure-portal) to set a Publisher Domain.
 
 ### PublisherDomainMismatch
 
@@ -255,10 +254,11 @@ See [requirements](publisher-verification-overview.md) for a list of allowed dom
 
 **Remediation Steps**
 1. Navigate to your [partner profile](https://partner.microsoft.com/pcv/accountsettings/connectedpartnerprofile), and view the email listed as Primary Contact
-2. The domain used to perform email verification in Partner Center is the portion after the “@” in the Primary Contact’s email
-3. Log in to [Azure Active Directory](https://aad.portal.azure.com/) > Azure Active Directory > App Registrations blade > (`Your App`) > Branding and Properties
-4. Select **Update Publisher Domain** and follow the instructions to **Verify a New Domain**.
-5. Add the domain used to perform email verification in Partner Center as a New Domain
+1. The domain used to perform email verification in Partner Center is the portion after the "@" in the Primary Contact's email
+1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least an [Cloud Application Administrator](../roles/permissions-reference.md#cloud-application-administrator).
+1. Browse to **Identity** > **Applications** > **Application registrations** > **Branding and Properties**.
+1. Select **Update Publisher Domain** and follow the instructions to **Verify a New Domain**.
+1. Add the domain used to perform email verification in Partner Center as a New Domain.
 
 
 ### NotAuthorizedToVerifyPublisher
@@ -268,10 +268,10 @@ You aren't authorized to set the verified publisher property on application (<`A
 Most commonly caused by the signed-in user not being a member of the proper role for the CPP account in Azure AD- see [requirements](publisher-verification-overview.md#requirements) for a list of eligible roles and see [common issues](#common-issues) for more information.
 
 **Remediation Steps**
-1. Sign in to the [Azure AD Portal](https://aad.portal.azure.com) using a user account in your organization's primary tenant.
-2. Navigate to [Role Management](https://aad.portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/RolesAndAdministrators).
-3. Select the desired admin role and click “Add Assignment” if you have sufficient permissions.
-4. If you do not have sufficient permissions, contact an admin role for assistance
+1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least an [Cloud Application Administrator](../roles/permissions-reference.md#cloud-application-administrator).
+1. Browse to **Identity** > **Applications** > **Roles & admins** > **Roles & admins**.
+1. Select the desired admin role and select **Add Assignment** if you have sufficient permissions.
+1. If you do not have sufficient permissions, contact an admin role for assistance.
 
 
 ### MPNIdWasNotProvided
@@ -281,8 +281,8 @@ The Partner One ID wasn't provided in the request body or the request content ty
 Most commonly caused when the verification is being performed via Graph API, and the Partner One ID wasn’t provided in the request. 
 
 **Remediation Steps**
-1. Navigate to your [partner profile](https://partner.microsoft.com/pcv/accountsettings/connectedpartnerprofile) > Identifiers blade > Microsoft Cloud Partners Program Tab
-2. Use the Partner ID with type PartnerGlobal in the request
+1. Navigate to your [partner profile](https://partner.microsoft.com/pcv/accountsettings/connectedpartnerprofile) > **Identifiers blade** > **Microsoft Cloud Partners Program Tab**.
+1. Use the Partner ID with type PartnerGlobal in the request.
 
 ### MSANotSupported 
 
@@ -298,7 +298,7 @@ The error message displayed will be: "Due to a configuration change made by your
 
 **Remediation Steps**
 1. Ensure [multi-factor authentication](../fundamentals/concept-fundamentals-mfa-get-started.md) is enabled and **required** for the user you're signing in with and for this scenario
-2. Retry Publisher Verification
+1. Retry Publisher Verification
 
 ### UserUnableToAddPublisher