Study guide

3.4 Authentication Methods and Sign-in Assurance

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.4 Authentication Methods and Sign-in Assurance

Key Takeaways Explain This Topic AI

An authentication method is the kind of proof an identity presents at sign-in; Entra ID supports passwords, MFA factors, and passwordless and phishing-resistant methods.

Passwordless methods include Windows Hello for Business, FIDO2 security keys / passkeys, and the Microsoft Authenticator app.

Phishing-resistant methods (Windows Hello for Business, passkeys/FIDO2, certificate-based authentication) are Microsoft's most secure recommendation.

A Temporary Access Pass (TAP) is a time-limited passcode used to bootstrap registration of passwordless methods or recover account access.

Authentication methods are managed centrally via the Authentication methods policy and combined security information registration.

Last updated: June 2026

What an authentication method is

An authentication method is the specific kind of proof an identity presents during sign-in. Microsoft Entra ID supports a spectrum of methods, and the SC-900 theme is that not all proofs are equally strong : a reusable secret like a password is the weakest, while cryptographic, device-bound, phishing-resistant methods are the strongest.

Authentication methods are categorized by the classic MFA factors :

  • Factor category Examples
  • Something you know Password, PIN, security questions
  • Something you have Phone (Authenticator app/SMS), FIDO2 security key, certificate
  • Something you are Biometric — fingerprint or facial recognition (Windows Hello)

Microsoft Entra ID supports passwords, Microsoft Authenticator (push/passwordless), OATH hardware/software tokens, SMS and voice call, Windows Hello for Business , FIDO2 security keys / passkeys , and certificate-based authentication (CBA) . Admins control which methods are available through the Authentication methods policy in the Microsoft Entra admin center, where they can enable or disable each method and scope it to specific users or groups.

The exam's recurring theme is that the choice of method directly determines the assurance of the sign-in — a password yields low confidence that the requester is genuine, while a phishing-resistant, device-bound credential yields high confidence. 4 questions for that outcome (more sign-in assurance, less credential risk) is more reliable than memorizing every method's mechanics.

Passwordless and phishing-resistant methods

Microsoft is actively moving customers away from passwords . Passwordless authentication replaces the password with something you have plus something you are/know, so there is no reusable secret to phish, guess, or reuse. The three passwordless options SC-900 emphasizes:

Windows Hello for Business — biometric (face/fingerprint) or PIN unlocking a key bound to the device's hardware (TPM). Local gesture; the credential never leaves the device.

FIDO2 security keys / passkeys — external hardware keys or device-bound passkeys based on the open FIDO2 standard; phishing-resistant by design. (Microsoft introduced Entra passkeys on Windows , storing device-bound passkeys in the Windows Hello container, in 2026.)

Microsoft Authenticator app — passwordless phone sign-in where the user approves a notification and matches a displayed number ( number matching ) plus a biometric/PIN on the phone.

Phishing-resistant methods — Windows Hello for Business , passkeys/FIDO2 , and certificate-based authentication — are Microsoft's recommended strongest tier because credentials cannot be replayed or captured by a fake site.

Temporary Access Pass and registration

Getting users onto passwordless methods needs a secure bootstrap, because a brand-new user has no method to register their first one. A Temporary Access Pass (TAP) is a time-limited passcode issued by an admin that a user enters to sign in and then register Windows Hello, a passkey, or Authenticator — or to recover access when they have lost their other methods. A TAP can be configured as one-time or usable for a limited window.

Users manage their methods through combined security information registration (the same place they enroll MFA and self-service password reset methods — see 3.6), typically at the My Sign-Ins / Security info page.

  • Capability Purpose
  • Authentication methods policy Admin control of which methods are allowed and to whom
  • Combined registration One place for users to register MFA + SSPR methods
  • Temporary Access Pass (TAP) Time-limited passcode to onboard passwordless or recover access
  • Number matching Anti-fatigue control in Authenticator push approvals

Choosing the right method — exam cues

Read 3.4 questions for the security outcome the scenario wants:

Eliminate the password entirely / no reusable secret → a passwordless method (Windows Hello, passkey/FIDO2, Authenticator).

Strongest, phishing-resistant sign-in → Windows Hello for Business, FIDO2/passkeys, or CBA .

Add a second proof on top of the password → multifactor authentication (covered fully in 3.5).

Onboard a new user to passwordless or recover a locked-out user → Temporary Access Pass .

Common traps: SMS and voice calls are additional factors but are not considered phishing-resistant, so they are not the "strongest" answer. Windows Hello credentials are bound to the device and use biometrics/PIN — they are not a roaming password. And don't confuse the method (the proof) with authorization (what access is granted afterward). Keep authentication strength and access decisions in separate lanes.

The strength ladder you should carry into the exam

It helps to picture authentication methods as a ladder from weakest to strongest, because SC-900 frequently asks you to pick the most secure option from a list:

Password alone — weakest; a single reusable secret that can be phished, guessed, or reused.

Password + SMS/voice — better (two factors) but the second factor is not phishing-resistant .

Password + Authenticator push with number matching — strong, resists push-fatigue attacks.

Passwordless (Authenticator passwordless, Windows Hello, passkeys) — no password to steal.

Phishing-resistant ( Windows Hello for Business, FIDO2/passkeys, certificate-based auth ) — strongest; credentials can't be replayed against a fake site.

When a question lists several methods and asks for the most secure , climb to the phishing-resistant rung. When it asks merely to add a factor to an existing password, an MFA method one or two rungs up is enough. This ladder, combined with the rule that the proof step is separate from authorization, resolves the majority of 3.4 questions quickly.