Skip to content

Commit bef6685

Browse files
committed
tech writer pass
1 parent a3512f8 commit bef6685

File tree

1 file changed

+13
-11
lines changed

1 file changed

+13
-11
lines changed

articles/active-directory/authentication/concept-mfa-howitworks.md

Lines changed: 13 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: multi-factor-authentication
66
ms.service: active-directory
77
ms.subservice: authentication
88
ms.topic: conceptual
9-
ms.date: 08/05/2021
9+
ms.date: 01/07/2022
1010

1111
ms.author: justinha
1212
author: justinha
@@ -17,21 +17,21 @@ ms.collection: M365-identity-device-management
1717
---
1818
# How it works: Azure AD Multi-Factor Authentication
1919

20-
Multi-factor authentication is a process where a user is prompted during the sign-in process for an additional form of identification, such as to enter a code on their cellphone or to provide a fingerprint scan.
20+
Multi-factor authentication is a process in which users are prompted during the sign-in process for an additional form of identification, such as to enter a code on their cellphone or to provide a fingerprint scan.
2121

22-
If you only use a password to authenticate a user, it leaves an insecure vector for attack. If the password is weak or has been exposed elsewhere, is it really the user signing in with the username and password, or is it an attacker? When you require a second form of authentication, security is increased as this additional factor isn't something that's easy for an attacker to obtain or duplicate.
22+
If you only use a password to authenticate a user, it leaves an insecure vector for attack. If the password is weak or has been exposed elsewhere, an attacker could be using it to gain access. When you require a second form of authentication, security is increased because this additional factor isn't something that's easy for an attacker to obtain or duplicate.
2323

24-
![Conceptual image of the different forms of multi-factor authentication](./media/concept-mfa-howitworks/methods.png)
24+
![Conceptual image of the various forms of multi-factor authentication.](./media/concept-mfa-howitworks/methods.png)
2525

2626
Azure AD Multi-Factor Authentication works by requiring two or more of the following authentication methods:
2727

2828
* Something you know, typically a password.
29-
* Something you have, such as a trusted device that is not easily duplicated, like a phone or hardware key.
29+
* Something you have, such as a trusted device that's not easily duplicated, like a phone or hardware key.
3030
* Something you are - biometrics like a fingerprint or face scan.
3131

32-
Azure AD Multi-Factor Authentication can also further secure password reset. When users register themselves for Azure AD Multi-Factor Authentication, they can also register for self-service password reset in one step. Administrators can choose forms of secondary authentication and configure challenges for MFA based on configuration decisions.
32+
Azure AD Multi-Factor Authentication can also further secure password reset. When users register themselves for Azure AD Multi-Factor Authentication, they can also register for self-service password reset in one step. Administrators can choose forms of secondary authentication and configure challenges for multi-factor authentication based on configuration decisions.
3333

34-
Apps and services don't need changes to use Azure AD Multi-Factor Authentication. The verification prompts are part of the Azure AD sign-in event, which automatically requests and processes the MFA challenge when required.
34+
You don't need to change apps and services to use Azure AD Multi-Factor Authentication. The verification prompts are part of the Azure AD sign-in, which automatically requests and processes the multi-factor authentication challenge when needed.
3535

3636
![Authentication methods in use at the sign-in screen](media/concept-authentication-methods/overview-login.png)
3737

@@ -42,18 +42,20 @@ When a user signs in to an application or service and receives an MFA prompt, th
4242
The following additional forms of verification can be used with Azure AD Multi-Factor Authentication:
4343

4444
* Microsoft Authenticator app
45-
* OATH Hardware token (preview)
46-
* OATH Software token
45+
* Windows Hello for Business
46+
* FIDO2 security key
47+
* OATH hardware token (preview)
48+
* OATH software token
4749
* SMS
4850
* Voice call
4951

5052
## How to enable and use Azure AD Multi-Factor Authentication
5153

5254
All Azure AD tenants can use [security defaults](../fundamentals/concept-fundamentals-security-defaults.md) to quickly enable Microsoft Authenticator for all users. Users and groups can be enabled for Azure AD Multi-Factor Authentication to prompt for additional verification during the sign-in event.
5355

54-
For more granular controls, [Conditional Access](../conditional-access/overview.md) policies can be used to define events or applications that require MFA. These policies can allow regular sign-in events when the user is on the corporate network or a registered device, but prompt for additional verification factors when remote or on a personal device.
56+
For more granular controls, [Conditional Access](../conditional-access/overview.md) policies can be used to define events or applications that require multi-factor authentication. These policies can allow regular sign-in events when the user is on the corporate network or a registered device, but prompt for additional verification factors when remote or on a personal device.
5557

56-
![Overview diagram of how Conditional Access works to secure the sign-in process](media/tutorial-enable-azure-mfa/conditional-access-overview.png)
58+
![Overview diagram of how Conditional Access works to secure the sign-in process.](media/tutorial-enable-azure-mfa/conditional-access-overview.png)
5759

5860
## Next steps
5961

0 commit comments

Comments
 (0)