Merge pull request #223763 from csmulligan/csmulligan-exid-msa

[EXID] Content engagement update for microsoft-account (ADO-59224)

Author: v-ccolin

articles/active-directory/external-identities/microsoft-account.md

@@ -1,20 +1,20 @@
 ---
 
-title: Microsoft account (MSA) identity provider in Azure AD
+title: Add Microsoft account (MSA) as an identity provider - Azure AD
 description: Use Azure AD to enable an external user (guest) to sign in to your Azure AD apps with their Microsoft account (MSA).
 
 services: active-directory
 ms.service: active-directory
 ms.subservice: B2B
 ms.topic: how-to
-ms.date: 09/29/2022
+ms.date: 01/12/2023
 
 ms.author: mimart
 author: msmimart
 manager: celestedg
-ms.collection: M365-identity-device-management
+ms.collection: engagement-fy23, M365-identity-device-management
 
-#Customer intent: As an Azure AD administrator user, I want to set up invitation flow or a self-service sign-up user flow for guest users, so they can sign into my Azure AD apps with their Microsoft account (MSA).
+#Customer intent: As an Azure AD administrator user, I want to set up an invitation flow or a self-service sign-up user flow for guest users, so they can sign into my Azure AD apps with their Microsoft account (MSA).
 ---
 
 # Add Microsoft account (MSA) as an identity provider for External Identities
@@ -25,7 +25,7 @@ Microsoft accounts are set up by a user to get access to consumer-oriented Micro
 
 ## Guest sign-in using Microsoft accounts
 
-Microsoft account is available by default in the list of **External Identities** > **All identity providers**. No further configuration is needed to allow guest users to sign in with their Microsoft account using either the invitation flow, or a self-service sign-up user flow.
+Microsoft account is available by default in the list of **External Identities** > **All identity providers**. No further configuration is needed to allow guest users to sign in with their Microsoft account, using either the invitation flow, or a self-service sign-up user flow.
 
 :::image type="content" source="media/microsoft-account/microsoft-account-identity-provider.png" alt-text="Screenshot of Microsoft account in the identity providers list.":::
 
@@ -42,7 +42,7 @@ Microsoft account is an identity provider option for your self-service sign-up u
 :::image type="content" source="media/microsoft-account/microsoft-account-user-flow.png" alt-text="Screenshot of the Microsoft account in a self-service sign-up user flow.":::
 
 ## Verifying the application's publisher domain
-As of November 2020, new application registrations show up as unverified in the user consent prompt, unless [the application's publisher domain is verified](../develop/howto-configure-publisher-domain.md), ***and*** the company’s identity has been verified with the Microsoft Partner Network and associated with the application. ([Learn more](../develop/publisher-verification-overview.md) about this change.) For Azure AD user flows, the publisher’s domain appears only when using a Microsoft account or other [Azure AD tenant](azure-ad-account.md) as the identity provider. To meet these new requirements, follow the steps below:
+As of November 2020, new application registrations show up as unverified in the user consent prompt, unless [the application's publisher domain is verified](../develop/howto-configure-publisher-domain.md), ***and*** the company’s identity has been verified with the Microsoft Partner Network and associated with the application.  For Azure AD user flows, the publisher’s domain appears only when using a Microsoft account or another Azure AD tenant as the identity provider. To meet these new requirements, follow the steps below:
 
 1. [Verify your company identity using your Microsoft Partner Network (MPN) account](/partner-center/verification-responses). This process verifies information about your company and your company’s primary contact.
 1. Complete the publisher verification process to associate your MPN account with your app registration using one of the following options:
@@ -51,5 +51,5 @@ As of November 2020, new application registrations show up as unverified in the
 
 ## Next steps
 
-- [Add Azure Active Directory B2B collaboration users](add-users-administrator.md)
-- [Add self-service sign-up to an app](self-service-sign-up-user-flow.md)
+- [Publisher verification overview](../develop/publisher-verification-overview.md)
+- [Add Azure Active Directory (Azure AD) as an identity provider for External Identities](azure-ad-account.md)