You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
title: Configure multi-factor authentication in Microsoft Entra ID
3
+
title: Configure multifactor authentication in Microsoft Entra ID
4
4
metadata:
5
-
title: Configure Multi-Factor Authentication in Microsoft Entra ID
6
-
description: Learn how to deploy and configure multi-factor authentication (MFA) in Microsoft Entra ID using Conditional Access policies, named locations, and secure user registration.
5
+
title: Configure multifactor Authentication in Microsoft Entra ID
6
+
description: Learn how to deploy and configure multifactor authentication (MFA) in Microsoft Entra ID using Conditional Access policies, named locations, and secure user registration.
Copy file name to clipboardExpand all lines: learn-pr/wwl-sci/manage-implement-authentication-methods/includes/1-introduction.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
-
In this module, you implement and manage authentication methods in Microsoft Entra ID, including multi-factor authentication (MFA), passwordless authentication, and self-service password reset (SSPR). You learn to deploy modern authentication solutions that balance security with user experience.
1
+
In this module, you implement and manage authentication methods in Microsoft Entra ID, including multifactor authentication (MFA), passwordless authentication, and self-service password reset (SSPR). You learn to deploy modern authentication solutions that balance security with user experience.
2
2
3
3
## Scenario
4
4
5
-
You're a security engineer at Contoso Corporation, a healthcare technology company that's modernizing from on-premises Active Directory to a hybrid cloud environment. Your CISO has issued a mandate: all users must use multi-factor authentication and passwordless sign-in within 90 days to meet new compliance requirements and reduce the risk of credential-based attacks.
5
+
You're a security engineer at Contoso Corporation, a healthcare technology company that's modernizing from on-premises Active Directory to a hybrid cloud environment. Your CISO has issued a mandate: all users must use multifactor authentication and passwordless sign-in within 90 days to meet new compliance requirements and reduce the risk of credential-based attacks.
6
6
7
7
Your help desk currently processes over 200 password reset requests weekly, costing approximately $50 per incident. Recent phishing attempts targeting employee credentials have heightened security concerns, especially as Contoso expands into AI-powered healthcare analytics using Azure AI Foundry and Microsoft Copilot for Microsoft 365.
8
8
@@ -12,7 +12,7 @@ Your task is to implement a comprehensive authentication strategy that strengthe
12
12
13
13
In this module, you will:
14
14
15
-
- Configure and deploy multi-factor authentication (MFA) for users and groups.
15
+
- Configure and deploy multifactor authentication (MFA) for users and groups.
16
16
- Implement passwordless authentication methods including FIDO2, Windows Hello for Business, and Microsoft Authenticator.
17
17
- Configure self-service password reset (SSPR) with appropriate authentication methods.
18
18
- Design authentication policies that balance security requirements with user experience.
Copy file name to clipboardExpand all lines: learn-pr/wwl-sci/manage-implement-authentication-methods/includes/2-explore-authentication-methods.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,9 +14,9 @@ Modern passwordless methods eliminate the password entirely. Instead of typing a
14
14
15
15
:::image type="content" source="../media/authentication-methods-spectrum.png" alt-text="Diagram showing the spectrum from password-only authentication on the left, through password plus MFA in the middle, to fully passwordless methods on the right, with security strength increasing from left to right.":::
16
16
17
-
## Multi-factor authentication as the bridge
17
+
## multifactor authentication as the bridge
18
18
19
-
For organizations that can't immediately move to passwordless, **multi-factor authentication (MFA)** provides a critical intermediate security layer. MFA requires users to verify their identity using two or more factors from different categories — for example, something they know (a password) combined with something they have (a registered phone).
19
+
For organizations that can't immediately move to passwordless, **multifactor authentication (MFA)** provides a critical intermediate security layer. MFA requires users to verify their identity using two or more factors from different categories — for example, something they know (a password) combined with something they have (a registered phone).
20
20
21
21
Microsoft Entra ID supports several MFA methods:
22
22
@@ -34,7 +34,7 @@ Microsoft Entra ID supports several MFA methods:
34
34
> [!IMPORTANT]
35
35
> SMS and voice call verification are considered legacy MFA methods. They're vulnerable to SIM-swapping attacks. Microsoft recommends migrating users away from these methods toward app-based or hardware-based alternatives.
36
36
37
-
The next unit on multi-factor authentication explores how to configure and enforce these methods across your user population.
37
+
The next unit on multifactor authentication explores how to configure and enforce these methods across your user population.
38
38
39
39
## Authentication strength and security hierarchy
40
40
@@ -60,4 +60,4 @@ When a user signs in, the request flows through the **Microsoft identity platfor
60
60
61
61
For devices joined to Microsoft Entra ID, a **Primary Refresh Token (PRT)** is issued after the first successful sign-in. The PRT enables single sign-on (SSO) across apps and services without requiring re-authentication — a meaningful gain in user experience that complements the security improvements from stronger authentication methods.
62
62
63
-
Understanding this architecture helps you anticipate how changes to authentication policies affect users and applications across the organization. Importantly, the same authentication policies that govern access to Microsoft 365 and Azure management also apply to AI-powered services like Azure AI Foundry and Microsoft Copilot for Microsoft 365 — making strong authentication the first line of defense for Contoso's AI investments as well. With this foundation in place, you're ready to dive into configuring multi-factor authentication in the next unit.
63
+
Understanding this architecture helps you anticipate how changes to authentication policies affect users and applications across the organization. Importantly, the same authentication policies that govern access to Microsoft 365 and Azure management also apply to AI-powered services like Azure AI Foundry and Microsoft Copilot for Microsoft 365 — making strong authentication the first line of defense for Contoso's AI investments as well. With this foundation in place, you're ready to dive into configuring multifactor authentication in the next unit.
Copy file name to clipboardExpand all lines: learn-pr/wwl-sci/manage-implement-authentication-methods/includes/3-configure-mfa.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
With Contoso's authentication strategy defined, your team is ready to enforce multi-factor authentication (MFA) for users, services, and emerging AI-driven workloads. For organizations with Microsoft Entra ID P1 or P2 licenses, **Conditional Access policies** remain the recommended way to require MFA in context, not on every sign-in.
1
+
With Contoso's authentication strategy defined, your team is ready to enforce multifactor authentication (MFA) for users, services, and emerging AI-driven workloads. For organizations with Microsoft Entra ID P1 or P2 licenses, **Conditional Access policies** remain the recommended way to require MFA in context, not on every sign-in.
0 commit comments