Merge pull request #191787 from rwike77/metadata

updating metadata

Author: jborsecnik

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

@@ -11,7 +11,7 @@ ms.workload: identity
 ms.date: 09/27/2021
 ms.author: ryanwi
 ms.custom: aaddev
-ms.reviewer: jesakowi
+ms.reviewer: ardhanap, jesakowi
 ---
 
 # Mark your app as publisher verified

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

@@ -11,7 +11,7 @@ ms.workload: identity
 ms.date: 06/01/2021
 ms.author: ryanwi
 ms.custom: aaddev
-ms.reviewer: jesakowi
+ms.reviewer: ardhanap, jesakowi
 ---
 
 # Publisher verification
@@ -58,7 +58,7 @@ There are a few pre-requisites for publisher verification, some of which will ha
 
     -  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).
 
--  The user performing verification must sign in using [multifactor authentication](../authentication/howto-mfa-getstarted.md).
+-  The user performing verification must sign in using [multi-factor authentication](../authentication/howto-mfa-getstarted.md).
 
 -  The publisher agrees to the [Microsoft identity platform for developers Terms of Use](/legal/microsoft-identity-platform/terms-of-use).
 

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

@@ -12,13 +12,13 @@ ms.workload: identity
 ms.date: 10/21/2021
 ms.author: ryanwi
 ms.custom: aaddev
-ms.reviewer: jesakowi
+ms.reviewer: ardhanap, jesakowi
 ---
 
 # Troubleshoot publisher verification
-If you are 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 are receiving errors or seeing unexpected behavior: 
+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 have all been met.
+1. Review the [requirements](publisher-verification-overview.md#requirements) and ensure they've all been met.
 
 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.
 
@@ -32,13 +32,13 @@ Below are some common issues that may occur during the process.
 - **I don’t know my Microsoft Partner Network ID (MPN ID) or I don’t know who the primary contact for the account is** 
     1. Navigate to the [MPN enrollment page](https://partner.microsoft.com/dashboard/account/v3/enrollment/joinnow/basicpartnernetwork/new)
     1. Sign in with a user account in the org's primary Azure AD tenant 
-    1. If an MPN account already exists, this will be recognized and you will be added to the account 
+    1. If an MPN account already exists, this will be recognized and you'll be added to the account 
     1. Navigate to the [partner profile page](https://partner.microsoft.com/pcv/accountsettings/connectedpartnerprofile) where the MPN 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 AD Portal](https://aad.portal.azure.com) using a user account in your organization's primary tenant
     1. Navigate to [Role Management](https://aad.portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/RolesAndAdministrators)
-    1. Click the desired admin role
+    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 MPN account are**
@@ -48,23 +48,23 @@ Below are some common issues that may occur during the process.
     1. Go to your [partner profile](https://partner.microsoft.com/pcv/accountsettings/connectedpartnerprofile) and verify that: 
         - The MPN 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”.
-    1. Go to the [MPN tenant management page](https://partner.microsoft.com/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. To add an additional tenant, follow the instructions [here](/partner-center/multi-tenant-account). Be aware that all Global Admins of any tenant you add will be granted Global Admin privileges on your Partner Center account.
-    1. Go to the [MPN User Management page](https://partner.microsoft.com/pcv/users) and confirm the user you are signing in as is either a Global Admin, MPN Admin, or Accounts Admin. To add a user to a role in Partner Center, follow the instructions [here](/partner-center/create-user-accounts-and-set-permissions).
+    1. Go to the [MPN 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 instructions [here](/partner-center/multi-tenant-account). Be aware that all Global Admins of any tenant you add will be granted Global Admin privileges on your Partner Center account.
+    1. Go to the [MPN User Management page](https://partner.microsoft.com/pcv/users) and confirm the user you're signing in as is either a Global Admin, MPN Admin, or Accounts Admin. To add a user to a role in Partner Center, follow the instructions [here](/partner-center/create-user-accounts-and-set-permissions).
 
 - **When I sign into the Azure AD portal, I do not see any apps registered. Why?** 
-    Your app registrations may have been created using a different user account in this tenant, a personal/consumer account, or in a different tenant. Ensure you are signed in with the correct account in the tenant where your app registrations were created.
+    Your app registrations may have been created using a different user account in this tenant, a personal/consumer account, or in a different tenant. Ensure you're signed in with the correct account in the tenant where your app registrations were created.
 
 - **I'm getting an error related to multi-factor authentication. What should I do?** 
-    Ensure [multifactor authentication](../fundamentals/concept-fundamentals-mfa-get-started.md) is enabled and **required** for the user you are signing in with and for this scenario. For example, MFA could be:
-    - Always required for the user you are signing in with
+    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. For example, MFA could be:
+    - Always required for the user you're signing in with
     - [Required for Azure management](../conditional-access/howto-conditional-access-policy-azure-management.md).
-    - [Required for the type of administrator](../conditional-access/howto-conditional-access-policy-admin-mfa.md) you are signing in with.
+    - [Required for the type of administrator](../conditional-access/howto-conditional-access-policy-admin-mfa.md) you're signing in with.
 
 ## Making Microsoft Graph API calls 
 
-If you are having an issue but unable to understand why based on what you are seeing in the UI, it may be helpful to perform further troubleshooting by using Microsoft Graph calls to perform the same operations you can perform in the App Registration portal.
+If you're having an issue but unable to understand why based on what you are seeing in the UI, it may be helpful to perform further troubleshooting by using Microsoft Graph calls to perform the same operations you can perform in the App Registration portal.
 
-The easiest way to make these requests is using [Graph Explorer](https://developer.microsoft.com/graph/graph-explorer). You may also consider other options like using [Postman](https://www.postman.com/), or using PowerShell to [invoke a web request](/powershell/module/microsoft.powershell.utility/invoke-webrequest).  
+The easiest way to make these requests is to use [Graph Explorer](https://developer.microsoft.com/graph/graph-explorer). You may also consider other options like using [Postman](https://www.postman.com/), or using PowerShell to [invoke a web request](/powershell/module/microsoft.powershell.utility/invoke-webrequest).  
 
 You can use Microsoft Graph to both set and unset your app’s verified publisher and check the result after performing one of these operations. The result can be seen on both the [application](/graph/api/resources/application) object corresponding to your app registration and any [service principals](/graph/api/resources/serviceprincipal) that have been instantiated from that app. For more information on the relationship between those objects, see: [Application and service principal objects in Azure Active Directory](app-objects-and-service-principals.md).  
 
@@ -147,97 +147,97 @@ The following is a list of the potential error codes you may receive, either whe
 
 ### MPNAccountNotFoundOrNoAccess
 
-The MPN ID you provided (`MPNID`) does not exist, or you do not have access to it. Provide a valid MPN ID and try again.
+The MPN ID you provided (`MPNID`) doesn't exist, or you don't have access to it. Provide a valid MPN ID and try again.
 
 Most commonly caused by the signed-in user not being a member of the proper role for the MPN account in Partner Center- see [requirements](publisher-verification-overview.md#requirements) for a list of eligible roles and see [common issues](#common-issues) for more information. Can also be caused by the tenant the app is registered in not being added to the MPN account, or an invalid MPN ID.
 
 ### MPNGlobalAccountNotFound
 
-The MPN ID you provided (`MPNID`) is not valid. Provide a valid MPN ID and try again.
+The MPN ID you provided (`MPNID`) isn't valid. Provide a valid MPN ID and try again.
 
 Most commonly caused when an MPN 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.
 
 ### MPNAccountInvalid
 
-The MPN ID you provided (`MPNID`) is not valid. Provide a valid MPN ID and try again.
+The MPN ID you provided (`MPNID`) isn't valid. Provide a valid MPN ID and try again.
 
 Most commonly caused by the wrong MPN ID being provided.
 
 ### MPNAccountNotVetted
 
-The MPN ID (`MPNID`) you provided has not completed the vetting process. Complete this process in Partner Center and try again. 
+The MPN ID (`MPNID`) you provided hasn't completed the vetting process. Complete this process in Partner Center and try again. 
 
-Most commonly caused by when the MPN account has not completed the [verification](/partner-center/verification-responses) process.
+Most commonly caused by when the MPN account hasn't completed the [verification](/partner-center/verification-responses) process.
 
 ### NoPublisherIdOnAssociatedMPNAccount
 
-The MPN ID you provided (`MPNID`) is not valid. Provide a valid MPN ID and try again. 
+The MPN ID you provided (`MPNID`) isn't valid. Provide a valid MPN ID and try again. 
 
 Most commonly caused by the wrong MPN ID being provided.
 
 ### MPNIdDoesNotMatchAssociatedMPNAccount
 
-The MPN ID you provided (`MPNID`) is not valid. Provide a valid MPN ID and try again.
+The MPN ID you provided (`MPNID`) isn't valid. Provide a valid MPN ID and try again.
 
 Most commonly caused by the wrong MPN ID being provided.
 
 ### ApplicationNotFound
 
-The target application (`AppId`) cannot 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. Note- the ID of the application must be provided, not the AppId/ClientId.
 
 ### B2CTenantNotAllowed
 
-This capability is not supported in an Azure AD B2C tenant.
+This capability isn't supported in an Azure AD B2C tenant.
 
 ### EmailVerifiedTenantNotAllowed
 
-This capability is not supported in an email verified tenant.
+This capability isn't supported in an email verified tenant.
 
 ### NoPublisherDomainOnApplication
 
 The target application (`AppId`) must have a Publisher Domain set. Set a Publisher Domain and try again.
 
-Occurs when a [Publisher Domain](howto-configure-publisher-domain.md) is not configured on the app.
+Occurs when a [Publisher Domain](howto-configure-publisher-domain.md) isn't configured on the app.
 
 ### PublisherDomainMismatch
 
-The target application's Publisher Domain (`publisherDomain`) does not match the domain used to perform email verification in Partner Center (`pcDomain`). Ensure these domains match and try again. 
+The target application's Publisher Domain (`publisherDomain`) doesn't match the domain used to perform email verification in Partner Center (`pcDomain`). Ensure these domains match and try again. 
 
 Occurs when neither the app's [Publisher Domain](howto-configure-publisher-domain.md) nor one of the [custom domains](../fundamentals/add-custom-domain.md) added to the Azure AD tenant match the domain used to perform email verification in Partner Center.
 
 ### NotAuthorizedToVerifyPublisher
 
-You are not authorized to set the verified publisher property on application (<`AppId`) 
+You aren't authorized to set the verified publisher property on application (<`AppId`) 
 
 Most commonly caused by the signed-in user not being a member of the proper role for the MPN 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.
 
 ### MPNIdWasNotProvided
 
-The MPN ID was not provided in the request body or the request content type was not "application/json".
+The MPN ID wasn't provided in the request body or the request content type wasn't "application/json".
 
 ### MSANotSupported 
 
-This feature is not supported for Microsoft consumer accounts. Only applications registered in Azure AD by an Azure AD user are supported.
+This feature isn't supported for Microsoft consumer accounts. Only applications registered in Azure AD by an Azure AD user are supported.
 
 ### InteractionRequired
 
-Occurs when multifactor authentication has not been performed before attempting to add a verified publisher to the app. See [common issues](#common-issues) for more information. Note: MFA must be performed in the same session when attempting to add a verified publisher. If MFA is enabled but not required to be performed in the session, the request will fail. 
+Occurs when multi-factor authentication hasn't been performed before attempting to add a verified publisher to the app. See [common issues](#common-issues) for more information. Note: MFA must be performed in the same session when attempting to add a verified publisher. If MFA is enabled but not required to be performed in the session, the request will fail. 
 
-The error message displayed will be: "Due to a configuration change made by your administrator, or because you moved to a new location, you must use multifactor authentication to proceed."
+The error message displayed will be: "Due to a configuration change made by your administrator, or because you moved to a new location, you must use multi-factor authentication to proceed."
 
 ### UnableToAddPublisher
 
-One of these error messages are displayed: "A verified publisher cannot be added to this application. Contact your administrator for assistance.", or "You are unable to add a verified publisher to this application. Contact your administrator for assistance."
+One of these error messages are displayed: "A verified publisher can’t be added to this application. Contact your administrator for assistance.", or "You're unable to add a verified publisher to this application. Contact your administrator for assistance."
 
 First, verify you've met the [publisher verification requirements](publisher-verification-overview.md#requirements).
 
-When a request to add a verified publisher is made, many signals are used to make a security risk assessment. If the request is determined to be risky an error will be returned. For security reasons, Microsoft does not disclose the specific criteria used to determine whether a request is risky or not. If you received this error and believe the "risky" assessment is incorrect, try waiting and resubmitting the verification request. Some customers have reported success after multiple attempts.
+When a request to add a verified publisher is made, many signals are used to make a security risk assessment. If the request is determined to be risky an error will be returned. For security reasons, Microsoft doesn't disclose the specific criteria used to determine whether a request is risky or not. If you received this error and believe the "risky" assessment is incorrect, try waiting and resubmitting the verification request. Some customers have reported success after multiple attempts.
 
 ## Next steps
 
-If you have reviewed all of the previous information and are still receiving an error from Microsoft Graph, gather as much of the following information as possible related to the failing request and [contact Microsoft support](developer-support-help-options.md#create-an-azure-support-request).
+If you've reviewed all of the previous information and are still receiving an error from Microsoft Graph, gather as much of the following information as possible related to the failing request and [contact Microsoft support](developer-support-help-options.md#create-an-azure-support-request).
 
 - Timestamp 
 - CorrelationId