Study guide

2.3 MFA and Passwordless Authentication

Microsoft Certified: Cloud and AI Security Engineer Associate SC-500

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 Current Exam Facts 1.2 Skills Measured & Weightings 1.3 Study Path, Prerequisites & Exam Strategy

2 Microsoft Entra ID Secure Access

2.1 Privileged Identity Management (PIM) 2.2 Conditional Access Policies 2.3 MFA and Passwordless Authentication 2.4 Application Identities, OAuth Consent & Managed Identities

3 Azure Key Vault Secrets and Keys

3.1 Deploy and Configure Key Vault 3.2 Access Control and Firewall for Key Vault 3.3 Keys, Secrets, Certificates & Defender for Key Vault

4 Governance, Policy & RBAC

4.1 Azure Policy for Security Controls 4.2 Defender for Cloud Compliance & Security Standards 4.3 Resource Locks and Azure RBAC 4.4 Custom Roles, Overprivileged Access, Backup & IaC Security

5 Secure Storage Accounts

5.1 Storage Account Security Fundamentals 5.2 Storage Firewalls and Access Policies 5.3 Defender for Storage

6 Secure Databases

6.1 Azure SQL Platform Security 6.2 Database Auditing 6.3 Defender for Databases

7 Network Security Groups & Virtual Network Manager

7.1 Network Security Groups and Application Security Groups 7.2 Azure Virtual Network Manager Security Admin Rules 7.3 Virtual WAN and VPN Security

8 Private Access, Private Link & Azure Firewall

8.1 Microsoft Entra Private Access 8.2 Private Endpoints and Private Link 8.3 Azure Firewall 8.4 Network Watcher Diagnostics and Effective Rules

9 Security for AI Workloads

9.1 Purview DSPM for AI and Data Overexposure 9.2 Copilot Studio Protection and Agent Management 9.3 Microsoft Entra Agent ID Security 9.4 Defender for AI, Foundry Guardrails & AI Gateway

10 Secure Servers and Virtual Machines

10.1 Disk Encryption 10.2 Azure Bastion and JIT VM Access 10.3 Azure Arc and Defender for Servers 10.4 Trusted Launch, VM Security Features & Machine Configuration

11 Application Platform Security

11.1 Containers: AKS, ACR, ACI, Container Apps & Defender for Containers 11.2 Azure Functions and Logic Apps Security 11.3 Azure App Service Security 11.4 Web Application Firewall and API Management Protection

12 Defender for Cloud Security Posture

12.1 Defender CSPM and Secure Score 12.2 Workload Protection Plans and Multicloud Connectors 12.3 Vulnerability Management and Defender EASM

13 Microsoft Sentinel Activity and Event Collection

13.1 Workspaces, Roles & Content Hub 13.2 Data Connectors, Syslog/CEF & Windows Event Collection 13.3 Custom Tables, Retention & Purview Audit 13.4 Automation Rules and Playbooks

14 Microsoft Security Copilot & Final Review

14.1 Microsoft Security Copilot Workspaces and Roles 14.2 Plugins and Security Agents 14.3 Final Review and Exam-Day Strategy

2.3 MFA and Passwordless Authentication

Key Takeaways Explain This Topic AI

MFA means more than one authentication factor; passwordless means the primary sign-in does not use a password (methods can still satisfy MFA when combined with device PIN/biometric)

Phishing-resistant methods include FIDO2/passkeys, Windows Hello for Business, and certificate-based authentication; SMS and voice are phishable and weaker

Authentication strengths in Conditional Access specify allowed method combinations: MFA strength, passwordless MFA strength, and phishing-resistant MFA strength

Temporary Access Pass (TAP) is a time-limited passcode used to onboard or recover passwordless methods; registration campaigns drive Authenticator adoption

SSPR resets passwords; MFA challenges during sign-in—related but different features that often share registered methods

Last updated: July 2026

2.3 MFA and Passwordless Authentication

Quick Answer: MFA requires multiple factors at sign-in; passwordless removes the password from the primary credential. Prefer phishing-resistant methods (FIDO2/passkeys, Windows Hello for Business, certificate-based auth) and enforce them with authentication strengths in Conditional Access. Use Temporary Access Pass and registration campaigns to onboard users; treat SMS as legacy/phishable.

Authentication is the front door for every Entra-protected resource. On SC-500, “implement MFA and passwordless” means designing method policy, registration, recovery, and Conditional Access enforcement—not just enabling a checkbox.

MFA vs Passwordless (Exam Distinction)

Concept Definition Example

Multifactor authentication (MFA) Sign-in uses at least two independent factors (something you know / have / are) Password + Authenticator notification; or FIDO2 key with PIN

Passwordless User does not enter a password as the primary credential Windows Hello for Business, FIDO2 passkey, Authenticator phone sign-in

Phishing-resistant MFA Methods that resist adversary-in-the-middle / credential replay phishing FIDO2, Windows Hello for Business, certificate-based MFA

Phishable MFA Second factor that can be socially engineered or intercepted SMS OTP, voice call, some push-fatigue scenarios without number matching

Key exam nuance: Passwordless methods are often also multifactor (device + biometric/PIN). Conversely, classic MFA can still be password-based (password + SMS). “Passwordless” describes the credential type ; “MFA” describes factor count ; “phishing-resistant” describes attack resistance .

  • Microsoft’s direction for privileged and high-risk access is phishing-resistant passwordless , not “any MFA.”
  • Authentication Methods You Must Know
  • Microsoft Authenticator
  • Push notifications (with number matching recommended to reduce MFA fatigue attacks)
  • TOTP codes
  • Passwordless phone sign-in (user approves on the phone without typing a password)

Authenticator is the common enterprise default for broad MFA rollout. It is stronger than SMS but not as phishing-resistant as hardware-backed FIDO2 in high-assurance designs.

  • Passkeys (FIDO2) and FIDO2 security keys
  • Phishing-resistant credentials bound to the relying party origin
  • Hardware keys or platform/synced passkeys depending on configuration
  • Excellent for admins and users who need portable strong auth
  • Windows Hello for Business
  • Device-bound credentials unlocked by biometric or PIN
  • Strong for corporate Windows fleets; pairs well with hybrid or cloud trust deployments
  • Counts toward phishing-resistant authentication strength scenarios
  • Temporary Access Pass (TAP)
  • Time-limited passcode issued by an admin
  • Configurable for one-time or multiple-use within a short lifetime

Primary uses: onboard passwordless methods for new hires; recover access when a user loses a FIDO2 key or phone

  • Treated as a strong method for bootstrap—not a long-term daily credential
  • SMS and voice
  • Widely available but phishable and vulnerable to SIM swap / interception

Acceptable only as fallback in low-assurance scenarios or during migration—not for Global Administrators or sensitive admin portals in a modern design

  • Certificate-based authentication (CBA)
  • Smart card / certificate scenarios for regulated environments
  • Can satisfy multifactor/phishing-resistant strengths when configured as multifactor CBA
  • Authentication Strengths in Conditional Access

Authentication strength is a grant control that whitelists allowed method combinations.

Built-in strength Typical included methods (conceptual) Use when

Multifactor authentication strength Broad MFA combinations, including password + something you have; may include TAP Baseline MFA mandate

Passwordless MFA strength Methods that satisfy MFA without using a password Passwordless adoption programs

Phishing-resistant MFA strength FIDO2, Windows Hello for Business, multifactor CBA (not SMS, not password+OTP) Admins, high-value apps, privileged portals

You can also define custom strengths. SC-500 loves questions that pair admin portals with phishing-resistant strength and standard users with broader MFA strength.

  • How this differs from “Require MFA”
  • Require MFA — any registered method that completes MFA may work (including weaker ones if enabled)
  • Require authentication strength — only methods in that strength are accepted

If the exam asks how to prevent SMS for Global Administrators while still allowing FIDO2, the answer is authentication strength (and method enablement policy), not merely “enable MFA.”

Registration Campaigns and Method Lifecycle

Users cannot use Authenticator or FIDO2 until methods are registered .

Registration campaign (Authenticator) prompts users during sign-in to set up the app—drives adoption without a help-desk ticket for every user

  • Authentication methods policy enables/disables methods (SMS, TAP, FIDO2, etc.) and scopes them to groups
  • Combined registration experiences let users set MFA and SSPR methods in one flow when configured

Lifecycle controls:

  • Enable strong methods in the authentication methods policy
  • Scope TAP to help desk / identity admins for issuance
  • Run registration campaigns for Authenticator
  • Issue TAP for FIDO2/Windows Hello onboarding where users have no existing strong method
  • Enforce strengths via Conditional Access once registration metrics look healthy
  • Remove SMS for privileged groups when ready
  • SSPR vs MFA

Feature Purpose When it runs

Self-Service Password Reset (SSPR) User recovers/changes a forgotten password without a help desk Password reset / change flows

MFA Extra proof at sign-in (or step-up) Authentication challenges

They often share registered methods (mobile app, email, phone) but solve different problems. Enabling SSPR does not equal enforcing MFA at sign-in. Conditional Access / security defaults / per-user MFA settings govern sign-in MFA; SSPR policies govern reset.

Exam trap: A user who can reset a password via SSPR may still be blocked by Conditional Access if they lack a required phishing-resistant method for an admin portal.

  • Passwordless Rollout Pattern (SC-500 Design)
  • Discover — inventory who still uses SMS; identify admin population
  • Enable methods — Authenticator passwordless, FIDO2, Windows Hello for Business, TAP
  • Register — campaigns + TAP-assisted onboarding
  • Enforce lightly — CA require MFA for all users (report-only → on)
  • Enforce strongly — CA phishing-resistant strength for admins and sensitive apps
  • Decommission weak methods — disable SMS for privileged groups; monitor fallback usage
  • Recover — documented TAP process for lost keys/devices; break-glass accounts remain separate
  • SC-500 Scenario Table
  • Requirement Configuration focus
  • All users must complete MFA CA grant: MFA (or MFA authentication strength); enable Authenticator
  • Admins must not use SMS Disable SMS for admin group; CA phishing-resistant strength on admin portals
  • New hire has no phone yet Issue TAP; user registers FIDO2 or Authenticator; TAP expires
  • Executive loses FIDO2 key Admin issues short-lived TAP; re-register passkey; revoke old key

Reduce password spray risk Passwordless + Conditional Access; smart lockout still helps residual password users

  • Audit asks “is MFA phishing-resistant?” Authentication strength reports + method registration inventory
  • Common Exam Traps

Passwordless is not the opposite of MFA — many passwordless methods are MFA.

SMS counts as MFA but fails phishing-resistant designs — do not recommend SMS for GA.

TAP is temporary onboarding/recovery , not a permanent replacement for FIDO2.

SSPR ≠ MFA enforcement — different control planes.

Authentication strength is the precision tool when “require MFA” is too broad.

Strong authentication protects human sign-ins. Applications and Azure resources also need identities—without embedding secrets in code. The next section covers app registrations, OAuth consent, and managed identities.