Entra ID Retires SMS and Voice MFA: Passkeys Become Default on September 1

Entra ID auto-enrolls SMS/voice MFA users into passkeys starting Sept 1, 2026, with full retirement Feb 1, 2027. Here's what admins must do now.

WINDOWS

8/7/20262 min read

a man riding a skateboard down the side of a ramp
a man riding a skateboard down the side of a ramp

Microsoft has locked in a hard deadline for one of the biggest identity changes in Entra ID's history. Starting September 1, 2026, passkeys become the default sign-in experience in Microsoft Entra ID, and any user currently enabled for SMS or voice MFA will be automatically enrolled into a passkey profile. Microsoft-provided SMS and voice delivery is then fully retired on February 1, 2027 — a date Microsoft's documentation, updated August 3, 2026, describes as having "no opt out." The move is framed around phishing resistance: SMS and voice codes are vulnerable to SIM-swap and real-time phishing attacks, while passkeys use device-bound or synced cryptographic keys that can't be replayed or intercepted the same way.

The rollout has two distinct phases admins need to track. On September 1, 2026, any tenant with users enabled for SMS or voice in the Authentication Methods Policy (or legacy MFA settings) will have those users auto-enrolled into a passkey-eligible profile, and the built-in Registration Campaign will start nudging them to register a passkey at their next MFA sign-in. That nudge is a soft prompt by default — Microsoft's documentation notes users get unlimited snoozes unless admins configure it otherwise. The second phase, February 1, 2027, is the hard cutover: users whose only registered MFA method is SMS or voice will hit a blocking prompt requiring passkey registration before they can sign in at all. There's no tenant-level opt-out for that enforcement date.

For admins who want to get ahead of this rather than let the auto-enrollment handle it, Microsoft published a PowerShell-based discovery script (the entra-sms-voice-usage-analyzer on GitHub) to identify exactly which users still rely on SMS or voice, provided you're logged in with Global Reader, Authentication Policy Administrator, or Security Reader rights. From there, the recommended path is to explicitly configure a Registration Campaign in Microsoft Managed state targeting that user group under Entra ID > Authentication methods > Registration campaign, rather than waiting for the automatic September 1 enrollment. Tenants that need more runway can also delay the whole process via Microsoft Graph: a PATCH to /beta/policies/authenticationmethodspolicy setting optOutSettings.passkeyDynamicMigration to true excludes the tenant from automatic passkey enablement during the transition window — though this only buys time, since the February 1, 2027 enforcement applies regardless of the opt-out setting.

Not every organization can walk away from SMS and voice entirely — regulated industries and certain out-of-band compliance scenarios still have a legitimate need. For those cases, Microsoft is routing customers to third-party telecom providers through the Microsoft Security Store rather than continuing to provide the service natively. Provider listings become available for review starting September 18, 2026, and tenants can select and configure a provider beginning October 30, 2026. Admins who know they'll need this path should start documenting the specific regulatory or operational justification now, since standing up a carrier contract and piloting it with a test group takes real lead time before the February deadline.

The practical takeaway for IT admins: this isn't a distant roadmap item, it's five weeks out. Run the discovery script this month, decide which users get proactively migrated versus which need a telecom exception, and get communications queued up — Microsoft's end-user templates (aka.ms/mfatemplates) cover the awareness, action, and reminder stages Microsoft recommends. Tenants that wait for the automatic September 1 enrollment to do the work for them will still end up needing a communication plan, just on a more compressed timeline and with less control over which users see the passkey prompt first.

Connect

Stay updated with latest Microsoft blog news

© 2025. All rights reserved.