Skip to content

Commit 957cf14

Browse files
committed
Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)
2 parents a682617 + 82a74a8 commit 957cf14

File tree

253 files changed

+2004
-1284
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

253 files changed

+2004
-1284
lines changed

.openpublishing.redirection.json

+5
Original file line numberDiff line numberDiff line change
@@ -45212,6 +45212,11 @@
4521245212
"source_path_from_root": "/articles/azure/sentinel/connect-windows-virtual-desktop.md",
4521345213
"redirect_url": "/azure/sentinel/connect-azure-virtual-desktop",
4521445214
"redirect_document_id": true
45215+
},
45216+
{
45217+
"source_path_from_root": "/articles/azure/cognitive-services/translator/custom-translator/v2-preview/project-overview.md",
45218+
"redirect_url": "/azure/cognitive-services/translator/custom-translator/v2-preview/beginners-guide",
45219+
"redirect_document_id": true
4521545220
}
4521645221
]
4521745222
}

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

+15-13
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,43 +17,45 @@ 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 a code on their cellphone or 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

3232
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.
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 MFA challenge when needed.
3535

36-
![Authentication methods in use at the sign-in screen](media/concept-authentication-methods/overview-login.png)
36+
![MFA sign-in screen.](media/concept-mfa-howitworks/sign-in-screen.png)
3737

3838
## Available verification methods
3939

40-
When a user signs in to an application or service and receives an MFA prompt, they can choose from one of their registered forms of additional verification. Users can access [My Profile](https://myprofile.microsoft.com) to edit or add verification methods.
40+
When users sign in to an application or service and receive an MFA prompt, they can choose from one of their registered forms of additional verification. Users can access [My Profile](https://myprofile.microsoft.com) to edit or add verification methods.
4141

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

52-
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.
54+
You can use [security defaults](../fundamentals/concept-fundamentals-security-defaults.md) in Azure AD tenants to quickly enable Microsoft Authenticator for all users. You can enable Azure AD Multi-Factor Authentication to prompt users and groups for additional verification during sign-in.
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, you can use [Conditional Access](../conditional-access/overview.md) policies to define events or applications that require MFA. These policies can allow regular sign-in when the user is on the corporate network or a registered device but prompt for additional verification factors when the user is 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+
![Diagram that shows 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)