WIP

MicrosoftGuyJFlo · MicrosoftGuyJFlo · commit a17b088258d1 · 2022-10-04T15:10:03.000-04:00
diff --git a/articles/active-directory/identity-protection/concept-identity-protection-policies.md b/articles/active-directory/identity-protection/concept-identity-protection-policies.md
@@ -44,7 +44,7 @@ If risks are detected on a sign-in, users can perform the required access contro
 ![Sign-in Risk-based Conditional Access policy](./media/concept-identity-protection-policies/sign-in-risk-policy.png)
 
 > [!NOTE] 
-> Users must have previously registered for Azure AD Multifactor Authentication before triggering the sign-in risk policy.
+> Users must have previously registered for Azure AD multifactor authentication before triggering the sign-in risk policy.
 
 ## User risk-based Conditional Access policy
 
@@ -71,13 +71,13 @@ If you already have Identity Protection risk policies set up, we encourage you t
 
 ## Azure AD MFA registration policy
 
-Identity Protection can help organizations roll out Azure AD Multifactor Authentication (MFA) using a policy requiring registration at sign-in. Enabling this policy is a great way to ensure new users in your organization have registered for MFA on their first day. Multifactor authentication is one of the self-remediation methods for risk events within Identity Protection. Self-remediation allows your users to take action on their own to reduce helpdesk call volume.
+Identity Protection can help organizations roll out Azure AD multifactor authentication (MFA) using a policy requiring registration at sign-in. Enabling this policy is a great way to ensure new users in your organization have registered for MFA on their first day. Multifactor authentication is one of the self-remediation methods for risk events within Identity Protection. Self-remediation allows your users to take action on their own to reduce helpdesk call volume.
 
-More information about Azure AD Multifactor Authentication can be found in the article, [How it works: Azure AD Multifactor Authentication](../authentication/concept-mfa-howitworks.md).
+More information about Azure AD multifactor authentication can be found in the article, [How it works: Azure AD multifactor authentication](../authentication/concept-mfa-howitworks.md).
 
 ## Next steps
 
 - [Enable Azure AD self-service password reset](../authentication/howto-sspr-deployment.md)
-- [Enable Azure AD Multifactor Authentication](../authentication/howto-mfa-getstarted.md)
-- [Enable Azure AD Multifactor Authentication registration policy](howto-identity-protection-configure-mfa-policy.md)
+- [Enable Azure AD multifactor authentication](../authentication/howto-mfa-getstarted.md)
+- [Enable Azure AD multifactor authentication registration policy](howto-identity-protection-configure-mfa-policy.md)
 - [Enable sign-in and user risk policies](howto-identity-protection-configure-risk-policies.md)
diff --git a/articles/active-directory/identity-protection/concept-identity-protection-user-experience.md b/articles/active-directory/identity-protection/concept-identity-protection-user-experience.md
@@ -19,7 +19,7 @@ ms.collection: M365-identity-device-management
 
 With Azure Active Directory Identity Protection, you can:
 
-* Require users to register for Azure AD Multi-Factor Authentication (MFA)
+* Require users to register for Azure AD multifactor authentication (MFA)
 * Automate remediation of risky sign-ins and compromised users
 
 All of the Identity Protection policies have an impact on the sign in experience for users. Allowing users to register for and use tools like Azure AD MFA and self-service password reset can lessen the impact. These tools along with the appropriate policy choices gives users a self-remediation option when they need it.
@@ -34,7 +34,7 @@ Enabling the Identity Protection policy requiring multi-factor authentication re
    
     ![More information required](./media/concept-identity-protection-user-experience/identity-protection-experience-more-info-mfa.png)
 
-1. Complete the guided steps to register for Azure AD Multi-Factor Authentication and complete your sign-in.
+1. Complete the guided steps to register for Azure AD multifactor authentication and complete your sign-in.
 
 ## Risky sign-in remediation
 
diff --git a/articles/active-directory/identity-protection/howto-identity-protection-configure-mfa-policy.md b/articles/active-directory/identity-protection/howto-identity-protection-configure-mfa-policy.md
@@ -15,20 +15,20 @@ ms.reviewer: sahandle
 
 ms.collection: M365-identity-device-management
 ---
-# How To: Configure the Azure AD Multifactor Authentication registration policy
+# How To: Configure the Azure AD multifactor authentication registration policy
 
-Azure Active Directory (Azure AD) Identity Protection helps you manage the roll-out of Azure AD Multifactor Authentication (MFA) registration by configuring a Conditional Access policy to require MFA registration no matter what modern authentication app you're signing in to.
+Azure Active Directory (Azure AD) Identity Protection helps you manage the roll-out of Azure AD multifactor authentication (MFA) registration by configuring a Conditional Access policy to require MFA registration no matter what modern authentication app you're signing in to.
 
-## What is the Azure AD Multifactor Authentication registration policy?
+## What is the Azure AD multifactor authentication registration policy?
 
-Azure AD Multifactor Authentication provides a means to verify who you are using more than just a username and password. It provides a second layer of security to user sign-ins. In order for users to be able to respond to MFA prompts, they must first register for Azure AD Multifactor Authentication.
+Azure AD multifactor authentication provides a means to verify who you are using more than just a username and password. It provides a second layer of security to user sign-ins. In order for users to be able to respond to MFA prompts, they must first register for Azure AD multifactor authentication.
 
-We recommend that you require Azure AD Multifactor Authentication for user sign-ins because it:
+We recommend that you require Azure AD multifactor authentication for user sign-ins because it:
 
 - Delivers strong authentication through a range of verification options.
 - Plays a key role in preparing your organization to self-remediate from risk detections in Identity Protection.
 
-For more information on Azure AD Multifactor Authentication, see [What is Azure AD Multifactor Authentication?](../authentication/howto-mfa-getstarted.md)
+For more information on Azure AD multifactor authentication, see [What is Azure AD multifactor authentication?](../authentication/howto-mfa-getstarted.md)
 
 ## Policy configuration
 
@@ -54,4 +54,4 @@ For an overview of the related user experience, see:
 
 - [Enable Azure AD self-service password reset](../authentication/howto-sspr-deployment.md)
 
-- [Enable Azure AD Multifactor Authentication](../authentication/howto-mfa-getstarted.md)
+- [Enable Azure AD multifactor authentication](../authentication/howto-mfa-getstarted.md)
diff --git a/articles/active-directory/identity-protection/howto-identity-protection-configure-risk-policies.md b/articles/active-directory/identity-protection/howto-identity-protection-configure-risk-policies.md
@@ -17,7 +17,7 @@ ms.collection: M365-identity-device-management
 ---
 # Configure and enable risk policies
 
-As we learned in the previous article, [Identity Protection policies](concept-identity-protection-policies.md), there are two types of risk policies in Azure Active Directory (Azure AD) Conditional Access you can set up to automate the response to risks and allow users to self-remediate when risk is detected:
+As we learned in the previous article, [Risk-based access policies](concept-identity-protection-policies.md), there are two types of risk policies in Azure Active Directory (Azure AD) Conditional Access you can set up to automate the response to risks and allow users to self-remediate when risk is detected:
 
 - Sign-in risk policy
 - User risk policy
@@ -34,7 +34,7 @@ Configured trusted [network locations](../conditional-access/location-condition.
 
 ### Risk remediation
 
-Organizations can choose to block access when risk is detected. Blocking sometimes stops legitimate users from doing what they need to. A better solution is to allow self-remediation using Azure AD Multi-Factor Authentication (MFA) and secure self-service password reset (SSPR).
+Organizations can choose to block access when risk is detected. Blocking sometimes stops legitimate users from doing what they need to. A better solution is to allow self-remediation using Azure AD multifactor authentication (MFA) and secure self-service password reset (SSPR).
 
 > [!WARNING]
 > Users must register for Azure AD MFA and SSPR before they face a situation requiring remediation. Users not registered are blocked and require administrator intervention.
@@ -50,7 +50,7 @@ Microsoft recommends the below risk policy configurations to protect your organi
 - Sign-in risk policy
    - Require Azure AD MFA when sign-in risk level is **Medium** or **High**, allowing users to prove it's them by using one of their registered authentication methods, remediating the sign-in risk. 
 
-Requiring access control when risk level is low will introduce more user interrupts. Choosing to block access rather than allowing self-remediation options, like secure password reset and multi-factor authentication, will impact your users and administrators. Weigh these choices when configuring your policies.
+Requiring access control when risk level is low will introduce more user interrupts. Choosing to block access rather than allowing self-remediation options, like secure password reset and multifactor authentication, will impact your users and administrators. Weigh these choices when configuring your policies.
 
 ## Exclusions
 
@@ -103,7 +103,7 @@ After confirming your settings using [report-only mode](../conditional-access/ho
    1. Select **High** and **Medium**.
    1. Select **Done**.
 1. Under **Access controls** > **Grant**.
-   1. Select **Grant access**, **Require multi-factor authentication**.
+   1. Select **Grant access**, **Require multifactor authentication**.
    1. Select **Select**.
 1. Under **Session**.
    1. Select **Sign-in frequency**.
@@ -142,7 +142,7 @@ If you already have risk policies enabled in Identity Protection, we highly reco
 
 ## Next steps
 
-- [Enable Azure AD Multi-Factor Authentication registration policy](howto-identity-protection-configure-mfa-policy.md)
+- [Enable Azure AD multifactor authentication registration policy](howto-identity-protection-configure-mfa-policy.md)
 - [What is risk](concept-identity-protection-risks.md)
 - [Investigate risk detections](howto-identity-protection-investigate-risk.md)
 - [Simulate risk detections](howto-identity-protection-simulate-risk.md)
diff --git a/articles/active-directory/identity-protection/howto-identity-protection-remediate-unblock.md b/articles/active-directory/identity-protection/howto-identity-protection-remediate-unblock.md
@@ -47,7 +47,7 @@ For more information about what happens when confirming compromise, see the sect
 
 ### Self-remediation with risk policy
 
-If you allow users to self-remediate, with Azure AD Multi-Factor Authentication (MFA) and self-service password reset (SSPR) in your risk policies, they can unblock themselves when risk is detected. These detections are then considered closed. Users must have previously registered for Azure AD MFA and SSPR for use when risk is detected.
+If you allow users to self-remediate, with Azure AD multifactor authentication (MFA) and self-service password reset (SSPR) in your risk policies, they can unblock themselves when risk is detected. These detections are then considered closed. Users must have previously registered for Azure AD MFA and SSPR for use when risk is detected.
 
 Some detections may not raise risk to the level where a user self-remediation would be required but administrators should still evaluate these detections. Administrators may determine that extra measures are necessary like [blocking access from locations](../conditional-access/howto-conditional-access-policy-location.md) or lowering the acceptable risk in their policies.
 
diff --git a/articles/active-directory/identity-protection/howto-identity-protection-simulate-risk.md b/articles/active-directory/identity-protection/howto-identity-protection-simulate-risk.md
@@ -38,7 +38,7 @@ More information about each risk detection can be found in the article, What is
 Completing the following procedure requires you to use:
 
 - The [Tor Browser](https://www.torproject.org/projects/torbrowser.html.en) to simulate anonymous IP addresses. You might need to use a virtual machine if your organization restricts using the Tor browser.
-- A test account that isn't yet registered for Azure AD Multi-Factor Authentication.
+- A test account that isn't yet registered for Azure AD multifactor authentication.
 
 **To simulate a sign-in from an anonymous IP, perform the following steps**:
 
@@ -59,7 +59,7 @@ The procedure below uses a newly created:
 Completing the following procedure requires you to use a user account that has:
 
 - At least a 30-day sign-in history.
-- Azure AD Multi-Factor Authentication enabled.
+- Azure AD multifactor authentication enabled.
 
 **To simulate a sign-in from an unfamiliar location, perform the following steps**:
 
