Update 10-secure-local-guest.md

Author: v-edmckillop

articles/active-directory/fundamentals/10-secure-local-guest.md

@@ -16,57 +16,50 @@ ms.collection: M365-identity-device-management
 
 # Convert local guest accounts to Azure Active Directory B2B guest accounts
 
-With Azure Active Directory (Azure AD B2B), external users collaborate with their identities. Organizations can issue local usernames and passwords to external users. This approach isn't recommended because Azure AD B2B has improved security, lower cost, and less complexity, compared to creating local accounts. In addition, if your organization issues local credentials that external users manage, you can use Azure AD B2B instead, this document provides a guide to make the transition as seamlessly as possible.
+With Azure Active Directory (Azure AD B2B), external users collaborate with their identities. Although organizations can issue local usernames and passwords to external users, this approach isn't recommended. Azure AD B2B has improved security, lower cost, and less complexity, compared to creating local accounts. In addition, if your organization issues local credentials that external users manage, you can use Azure AD B2B instead. Use the guidance in this document to make the transition.
 
 Learn more: [Plan an Azure AD B2B collaboration deployment](secure-external-access-resources.md)
 
 ## Identify external-facing applications
 
-Before migrating local accounts to Azure AD B2B, admins should understand what applications and workloads these external users need to access. For example, if external users need access to an application that is hosted on-premises, admins will need to validate that the application is integrated with Azure AD and that a provisioning process is implemented to provision the user from Azure AD to the application.
-The existence and use of on-premises applications could be a reason why local accounts are created in the first place. Learn more about
-[provisioning B2B guests to on-premises
-applications.](../external-identities/hybrid-cloud-to-on-premises.md)
+Before migrating local accounts to Azure AD B2B, confirm the applications and workloads external users can access. For example, for applications hosted on-premises, validate the application is integrated with Azure AD. On-premises applications are a good reason to create local accounts. 
 
-All external-facing applications should have single-sign on (SSO) and provisioning integrated with Azure AD for the best end user experience.
+Learn more: [Grant B2B users in Azure AD access to your on-premises applications](../external-identities/hybrid-cloud-to-on-premises.md)
+
+We recommend that external-facing applications have single-sign on (SSO) and provisioning integrated with Azure AD for the best end user experience.
 
 ## Identify local guest accounts
 
-Admins will need to identify which accounts should be migrated to Azure AD B2B. External identities in Active Directory should be easily identifiable, which can be done with an attribute-value pair. For example, making ExtensionAttribute15 = `External` for all external users. If these users are being provisioned via Azure AD Connect or Cloud Sync, admins can optionally configure these synced external users
-to have the `UserType` attributes set to `Guest`. If these users are being
-provisioned as cloud-only accounts, admins can directly modify the
-users' attributes. What is most important is being able to identify the
-users who you want to convert to B2B.
+Identify the accounts to be migrated to Azure AD B2B. External identities in Active Directory are identifiable with an attribute-value pair. For example, making ExtensionAttribute15 = `External` for external users. If these users are set up with Azure AD Connect or Cloud Sync, configure synced external users to have the `UserType` attributes set to `Guest`. If the users are set up as cloud-only accounts, you can modify user attributes. Primarily, identify users to convert to B2B.
 
 ## Map local guest accounts to external identities
 
-Once you've identified which external user accounts you want to
-convert to Azure AD B2B, you need to identify the BYOI identities or external emails for each user. For example, admins will need to identify that the local account ([email protected]) is a user whose home identity/email address is [email protected]. How to identify the home identities is up to the organization, but some examples include:
-
-- Asking the external user's sponsor to provide the information.
-
-- Asking the external user to provide the information.
+Identify user identities or external emails. Confirm that the local account ([email protected]) is a user with the home identity and email address: [email protected]. To identify home identities:
 
-- Referring to an internal database if this information is already known and stored by the organization.
+- The external user's sponsor provides the information
+- The external user provides the information
+- Refer to an internal database, if the information is known and stored
 
-Once the mapping of each external local account to the BYOI identity is done, admins will need to add the external identity/email to the user.mail attribute on each local account.
+After mapping external local accounts to identities, add external identities or email to the user.mail attribute on local accounts.
 
 ## End user communications
 
-External users should be notified that the migration will be taking place and when it will happen. Ensure you communicate the expectation that external users will stop using their existing password and post-migration will authenticate with their own home/corporate credentials going forward. Communications can include email campaigns, posters, and announcements.
+Notify external users about migration timing. Communicate expectations, such as when external users must stop using a current password to enable authenticate by home and corporate credentials. Communications can include email campaigns and announcements.
 
 ## Migrate local guest accounts to Azure AD B2B
 
-Once the local accounts have their user.mail attributes populated with the external identity/email that they're mapped to, admins can [convert the local accounts to Azure AD B2B by inviting the local account.](../external-identities/invite-internal-users.md)
-This can be done in the UX or programmatically via PowerShell or the Microsoft Graph API. Once complete, the users will no longer
-authenticate with their local password, but will instead authenticate with their home identity/email that was populated in the user.mail attribute. You've successfully migrated to Azure AD B2B.
+After local accounts have user.mail attributes populated with the external identity and email, convert local accounts to Azure AD B2B by inviting the local account. You can use PowerShell or the Microsoft Graph API.
 
-## Post-migration considerations
+Learn more: [Invite internal users to B2B collaboration](../external-identities/invite-internal-users.md)
 
-If local accounts for external users were being synced from on-premises, admins should take steps to reduce their on-premises footprint and use cloud-native B2B guest accounts moving forward. Some possible actions can include:
+## Post-migration considerations
 
-- Transition existing local accounts for external users to Azure AD B2B and stop creating local accounts. Post-migration, admins should invite external users natively in Azure AD.
+If external user local accounts were synced from on-premises, reduce their on-premises footprint and use B2B guest accounts. You can:
 
-- Randomize the passwords of existing local accounts for external users to ensure they can't authenticate locally to on-premises resources. This will increase security by ensuring that authentication and user lifecycle is tied to the external user's home identity.
+- Transition external user local accounts to Azure AD B2B and stop creating local accounts
+  - Invite external users in Azure AD
+- Randomize external usesr local-account passwords to prevent authentication to on-premises resources 
+  - This action ensures authentication and user lifecycle is connecteed to the external user home identity
 
 ## Next steps