Study guide
3.5 Multifactor Authentication
Azure SC-900 Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Orientation: SC-900 Audience, Format, Scoring, Retakes, and Study Map
1.1 Credential Purpose and Audience 1.2 Exam Duration, Seat Duration, and Experience 1.3 Scoring, Scaled Score, and Pass-Rate Myths 1.4 Retake Policy and Certification Lifecycle 1.5 Scheduling, Price, and Delivery Options 1.6 Skills Measured and Study Map
2 Security, Compliance, and Identity Concepts: Zero Trust, Shared Responsibility, and GRC
2.1 Shared Responsibility Model 2.2 Defense in Depth and the CIA Triad 2.3 Zero Trust Model 2.4 Encryption, Hashing, and Data States 2.5 Governance, Risk, and Compliance 2.6 Identity Perimeter, Authentication, Authorization, and Federation
3 Microsoft Entra ID: Identities, Hybrid Identity, and Authentication
3.1 Microsoft Entra ID Foundations 3.2 Identity Types and Directory Objects 3.3 Hybrid Identity and Entra Connect Concepts 3.4 Authentication Methods and Sign-in Assurance 3.5 Multifactor Authentication 3.6 Password Protection, Self-Service Password Reset, and External Identities
4 Microsoft Entra Access Management, Governance, PIM, and Identity Protection
4.1 Conditional Access Purpose 4.2 Signals and Controls 4.3 Microsoft Entra Roles and Role-Based Access Control 4.4 Identity Governance, Entitlement Management, and Lifecycle Governance 4.5 Access Reviews and Privileged Identity Management 4.6 Microsoft Entra ID Protection and Risk
5 Azure Infrastructure Security: DDoS, Firewall, WAF, NSGs, Bastion, and Key Vault
5.1 Choose the Right Infrastructure Security Control 5.2 Azure DDoS Protection for Availability 5.3 Azure Firewall for Centralized Network Policy 5.4 Web Application Firewall for HTTP Workloads 5.5 Virtual Networks, Subnets, and Network Security Groups 5.6 Bastion and Key Vault for Administration and Secrets
6 Defender for Cloud: CSPM, Cloud Workload Protection, and Secure Score
6.1 Defender for Cloud Purpose and Exam Role 6.2 CSPM, Foundational Posture, and Defender CSPM 6.3 Policies, Standards, and Security Recommendations 6.4 Secure Score and Remediation Priority 6.5 Regulatory Compliance and Multicloud Posture 6.6 Cloud Workload Protection and Defender Plans
7 Microsoft Sentinel: SIEM, SOAR, Analytics, Hunting, Workbooks, and Playbooks
7.1 Sentinel as SIEM and SOAR 7.2 Data Connectors and Security Signals 7.3 Analytics Rules, Incidents, and Detection 7.4 Workbooks for Visual Review 7.5 Hunting, KQL Awareness, and Notebooks 7.6 Automation Rules and Logic Apps Playbooks
8 Microsoft Defender XDR: Office, Endpoint, Cloud Apps, Identity, Vulnerability, and Threat Intelligence
8.1 Defender XDR Suite and Microsoft Defender Portal 8.2 Defender for Office 365 8.3 Defender for Endpoint 8.4 Defender for Cloud Apps 8.5 Defender for Identity 8.6 Vulnerability Management and Threat Intelligence
9 Microsoft Purview, Service Trust, Privacy, Compliance Manager, and Compliance Score
9.1 Service Trust Portal and Assurance Resources 9.2 Privacy Principles and Microsoft Priva 9.3 Microsoft Purview Portal 9.4 Compliance Manager Assessments 9.5 Compliance Score and Improvement Actions 9.6 Scenario Selection for Trust, Privacy, and Compliance Manager
10 Microsoft Purview Data Classification, Labels, DLP, Retention, eDiscovery, and Audit
10.1 Data Classification Foundations 10.2 Content Explorer and Activity Explorer 10.3 Sensitivity Labels and Label Policies 10.4 Data Loss Prevention 10.5 Retention, Records Management, and Label Policies 10.6 eDiscovery, Audit, and Insider Risk Management
11 SC-900 Product Selection Playbooks and Common Microsoft Rebrand Traps
11.1 Read the Scenario Before Picking a Product 11.2 Entra Playbook for Identity, Access, and Governance 11.3 Defender Playbook for Protection, Detection, and Posture 11.4 Sentinel Playbook for SIEM, SOAR, and Hunting 11.5 Purview Playbook for Compliance, Data, and Risk 11.6 Renamed Products and Similar-Name Traps 11.7 Microsoft Learn Practice Assessment Review Loop
12 Final SC-900 Review, Timed Practice, Exam Day, and Next Certification Path
12.1 Domain-Weighted Final Review Plan 12.2 Timed Practice and Pacing 12.3 Exam Sandbox and Question Experience 12.4 Exam-Day Logistics and Boundaries 12.5 Scoring, Retakes, and After-Exam Decisions 12.6 Final Memory Check and Scenario Drills 12.7 Next Certification Path After SC-900
3.5 Multifactor Authentication
Key Takeaways Explain This Topic AI
Multifactor authentication (MFA) requires two or more proofs from different categories: something you know, have, and are.
A password plus a second factor from the SAME category is not MFA; the factors must be of different types.
Microsoft Entra MFA methods include Microsoft Authenticator (push with number matching), FIDO2/passkeys, Windows Hello, OATH tokens, and SMS/voice.
MFA is most often enforced through Conditional Access policies, and Security defaults provide a free baseline that requires MFA for all users.
MFA dramatically reduces account-compromise risk; Microsoft reports it blocks the vast majority of identity attacks, but it is a sign-in (authentication) control, not authorization.
Last updated: June 2026
What MFA actually requires
Multifactor authentication (MFA) requires an identity to present two or more verification proofs from different categories before sign-in succeeds. The categories are the same three factors from 3.4:
- Something you know — password or PIN
- Something you have — a phone, FIDO2 key, or token
- Something you are — a biometric (fingerprint/face)
The critical exam rule: the factors must come from different categories . A password and a security question are both "something you know," so that combination is not true MFA. A password (know) plus an Authenticator approval on your phone (have) is MFA. This "two factors must be different types" distinction is a favorite SC-900 trap.
MFA matters because it directly addresses the weakness of password-only sign-in: even if an attacker steals or guesses the password, they still lack the second factor. Microsoft has reported that MFA blocks the vast majority (over 99%) of account-compromise attacks, which is why identity is treated as the primary perimeter in Zero Trust .
Entra MFA methods and number matching
Microsoft Entra multifactor authentication can use any of the second-factor methods Entra ID supports:
MFA method Category Strength note
Microsoft Authenticator push approval Have + know/are (PIN/biometric on phone) Uses number matching to stop MFA-fatigue attacks
- FIDO2 security key / passkey Have Phishing-resistant
- Windows Hello for Business Have + are/know Phishing-resistant, device-bound
- OATH hardware/software token Have Time-based one-time codes
- SMS text / voice call Have Convenient but not phishing-resistant
Number matching is an important modern control: instead of just tapping "Approve," the user must type a number shown on the sign-in screen into the Authenticator app, which defeats MFA fatigue / push-bombing attacks where an attacker spams approval prompts hoping the user taps yes. SMS and voice still count as MFA factors but are the weakest because they can be intercepted or SIM-swapped.
How MFA is enforced
MFA is rarely a standalone toggle; it is triggered by policy . Two SC-900-relevant enforcement mechanisms:
Security defaults — a free, tenant-wide baseline that, among other protections, requires all users to register and use MFA and forces MFA for administrators. It is on by default for many newer tenants and is the simple, all-or-nothing option.
Conditional Access — the flexible, policy-based engine (covered in Chapter 4) that requires MFA based on signals such as user/group, app, location, device state, and sign-in risk. For example, "require MFA when accessing finance apps from outside the corporate network."
- Enforcement option Granularity Licensing
- Security defaults All-or-nothing, tenant-wide Free, included with Entra ID
- Conditional Access Targeted by signals/conditions Requires Entra ID P1 or higher
Exam cue: "require MFA for everyone with no configuration" → Security defaults ; "require MFA only under certain conditions " → Conditional Access .
MFA versus its neighbors — staying in lane
MFA strengthens the authentication step only. It does not decide whether someone should be a global administrator, whether their access should be recertified, or how to respond to a risky sign-in. Keep these adjacent capabilities separate:
Stronger proof at sign-in → MFA .
Decide what a signed-in user may access → authorization / roles .
Periodically confirm a user still needs access → access reviews (governance).
Time-bound activation of a privileged role → Privileged Identity Management (PIM) .
Detect and respond to risky sign-ins / leaked credentials → Identity Protection .
Common traps: MFA is not the same as passwordless — passwordless removes the password, while MFA can still include the password as one of its factors (though passwordless methods can themselves satisfy MFA). And MFA does not eliminate the need for authorization; a successfully MFA'd user still only gets the access their roles and policies allow. When a scenario says "add a second verification step" or "reduce risk from stolen passwords," MFA should be at the top of your list.
Putting MFA in the Zero Trust picture
MFA is the clearest, most exam-friendly example of the Zero Trust principle "verify explicitly." Rather than trusting a password because it was correct, the system demands additional, harder-to-forge evidence before granting the sign-in. That is why MFA shows up across multiple SC-900 objective areas — concepts, identity, and security — and why "require MFA" is one of the most common recommended controls.
A few precise points the exam can probe:
MFA can be per-user enabled (legacy), via Security defaults (free baseline), or via Conditional Access (P1+, signal-based). Conditional Access is the modern, recommended approach.
MFA strengthens interactive sign-in ; it does not by itself protect against an already-stolen session token (that's where Conditional Access session controls and Identity Protection add value).
Passwordless phishing-resistant methods (passkeys, Windows Hello) can satisfy the MFA requirement and remove the password at once.
Verify explicitly → require MFA.
All users, no config → Security defaults.
Targeted by conditions → Conditional Access.
Remove the password while keeping MFA-grade assurance → phishing-resistant passwordless.
Grounding MFA in "verify explicitly" ties this section back to Chapter 2 and forward to Conditional Access, which is exactly how the exam connects the dots.