Content reviewed: 13 October 2026

Microsoft Entra is changing the experience for organizations that still rely on text messages or voice calls. From 1 September 2026, users enabled for SMS or voice are automatically enabled for passkeys and can be prompted to register one during an eligible sign-in. This is not the date when telephone methods stop working. Microsoft-provided SMS and voice delivery ends in stages in 2027. The work is therefore broader than turning on a policy: identify affected people, prepare their devices, provide safe recovery, test real sign-in flows and document legitimate exceptions. The Microsoft retirement timeline separates the populations and deadlines.

This timeline applies to public-cloud environments. Azure AD B2C is outside its scope, and Microsoft Entra External ID tenants are to receive a separate announcement. These tenants are different from an external B2B guest in a workforce tenant. Microsoft also plans passkey availability for B2B and internal guests by the end of 2026; verify actual availability in the pilot instead of assuming it already works. The Microsoft FAQ specifies this scope and plan.

Transition dates

September 2026 starts automatic passkey enablement and the registration nudge; it does not retire SMS. From 1 February 2027, Microsoft-provided telephone authentication is retired for most users, including internal guest users. Global Administrators and external users have the later date of 1 July 2027. After the applicable date, a person whose only available MFA method is SMS or voice must register a passkey before continuing to sign in; Microsoft describes this as a blocking prompt. A temporary opt-out from automatic enablement in the earlier phase does not remove the 2027 enforcement. Check the official timeline and retirement FAQ before setting internal deadlines.

Transition timeline
DateWhat changesWhat to do
1 September 2026Eligible SMS/voice users get passkey enablement and a registration nudgeInventory users, communicate and run a pilot
1 February 2027Microsoft telephony delivery retires for most users, including internal guestsFinish registration and test recovery
1 July 2027Later retirement for Global Administrators and external usersTest privileged and B2B scenarios separately

The practical implication is to set your own completion date well before Microsoft's enforcement. Leave time for a pilot, help-desk training, support for unusual devices and a retry if a passkey profile blocks registration. Do not infer readiness from a policy that says enabled. The person must be able to register and then complete a subsequent sign-in to the applications they use. A representative test group should include office staff, frontline workers, privileged administrators and people who do not carry a company-managed smartphone.

Who still uses telephony

Inventory accounts enabled for SMS or voice in the Authentication Methods Policy or legacy MFA settings. Then distinguish permission to use a method from observed usage: an account can retain a phone method while normally signing in with a stronger one. Microsoft provides a script and specifies the reading roles needed to find affected users in its migration guidance. Divide the result by device type, account class, support needs and critical application. Include frontline staff, shared workstations, internal guests, operational exceptions and highly privileged users. An enabled passkey policy is not evidence that an individual has finished registration, and a one-time registration does not prove that recovery works.

  • Record the user, account type, enabled methods, observed phone use and responsible team
  • Check devices, browser support, credential manager and access to a backup sign-in path
  • Document any genuine regulatory or operational requirement for telephony with an owner
  • Keep a recovery procedure and next review date for each exception

Choosing a passkey

Passkeys use cryptographic keys and resist phishing, code forwarding, SIM swapping and replay more effectively than SMS. Microsoft Entra supports synced passkeys stored in a platform credential manager and device-bound passkeys such as Microsoft Authenticator, Entra passkeys on Windows and FIDO2 security keys. A physical key is not mandatory for every employee. In its passkey FAQ, Microsoft recommends device-bound passkeys for administrators and other highly privileged users, while synced passkeys are suitable for ordinary non-admin users. Choose with the organization's device model, recovery path and assurance requirement in mind. Test the combinations of operating system, browser and credential provider that staff actually use.

An Entra passkey on Windows and a Windows Hello for Business credential are different. A local Windows passkey can be registered without Entra device join or registration, but it does not provide Windows device sign-in. WHfB also supports device sign-in and SSO. If a WHfB credential already exists for the same account, registering a Windows passkey can return an already-registered error. Check whether a usable phishing-resistant method is already present before changing the setup; do not remove working WHfB merely to fix this message. Microsoft explains the distinction.

Policy and registration

Before starting a registration campaign, enable Passkey (FIDO2) for the target group in Authentication Methods Policy and allow self-service setup when users should register their own credential. Passkey profiles control the types permitted for different groups. Changes to attestation or AAGUID restrictions require careful testing: a restrictive change can affect already registered credentials. The Microsoft enablement guide documents these controls. In the pilot, verify a new registration, a repeat sign-in and the experience after changing or replacing a device. Also check that staff know which passkey provider is approved by the organization rather than choosing one without guidance.

Campaigns and adoption

A registration campaign prompts eligible people after an interactive MFA sign-in. Microsoft's managed passkey setting allows unlimited snoozes by default, so a campaign can be active while a meaningful group still has no passkey. Measure successful registrations, SMS-only accounts, platform-specific failures and subsequent sign-ins without telephone MFA. You can scope the campaign to groups, but one campaign targets one authentication method at a time. The registration campaign documentation explains prerequisites and prompt behavior. Tell users why they see the prompt and where to get help if their device cannot create the requested credential. Avoid interpreting the number of sent emails as adoption.

Campaign state and its effects
StateWho receives the nudgeSnoozing
Microsoft managed, PasskeyUsers in at least one eligible passkey profileUnlimited snoozes by default
Enabled, PasskeyTargeted users in a passkey profile; no additional managed eligibility testAdministrator controls interval and limits
DisabledThis campaign sends no nudgeDoes not disable other registration policies or final enforcement

In Enabled state with limited snoozes, users can skip three times. An interval of zero therefore does not prohibit every skip. The count persists across campaign restarts and configuration changes. Skipping a registration error screen does not count toward that limit. Nudge eligibility also does not bypass actual registration controls: a Security info policy requiring the internal network can prevent prompts outside it. Microsoft documents these campaign conditions.

  1. 01

    Define affected populations

    Inventory SMS/voice users, separate administrators and guests, and check actual sign-in patterns

  2. 02

    Enable suitable passkey profiles

    Set FIDO2 policy and self-service registration for a small pilot with varied devices

  3. 03

    Launch the nudge and support path

    Prepare user guidance, campaign scope, help desk and a lost-device process

  4. 04

    Verify access and coverage

    Test repeat sign-in, core applications, a second device and recovery before expanding

Account recovery

A migration is fragile if people can create a passkey but cannot safely recover after losing a device. Microsoft Entra offers Temporary Access Pass (TAP), a time-limited passcode used to bootstrap or recover passwordless methods. It can be restricted by lifetime and, according to policy, to a single use. Define who verifies the requester's identity, who issues TAP, how it is delivered and how completion is recorded. TAP is not a permanent replacement for a password. The Microsoft procedure also notes limitations for external guest accounts. Exercise scenarios such as a lost phone, a replaced work laptop and a new hire who has not yet registered another MFA method.

With a single-use TAP, passwordless method registration must finish within ten minutes of signing in with that TAP. This registration window is different from the passcode lifetime. A longer device enrollment can require a second single-use TAP for subsequent credential registration. TAP expiry also does not retroactively terminate every established session; session controls affect access duration. These limits are in the TAP procedure.

Guests need different recovery paths
AccountTAP in the resource tenantWhat to verify
Internal guestCan be issued subject to TAP policyActual identity source; UserType Guest alone is insufficient
External B2B guestCannot be issued hereHome-tenant recovery and cross-tenant MFA trust
External guest with home-tenant TAPAccess may work under the documented conditionsHome requirements and trust settings; no automatic exemption

The interface can offer Add TAP for an external guest even though the operation fails. Agree with the partner support team who verifies identity and restores the home credential. Accepting a home-tenant TAP does not mean it satisfies any authentication strength in the resource tenant. Microsoft distinguishes internal and external guests.

Telephony exceptions

As of 13 October 2026, Choose Your Own Telephony Provider cannot yet be configured. Microsoft schedules the configuration experience to start on 30 October and lists Soprano and Telesign as initial private-preview providers; this is not confirmation of general availability. For a documented telephony requirement, prepare commercial and operational conditions, then verify availability and run a pilot. Recheck the current provider status before implementation. Native Microsoft telephony retirement also covers SSPR according to the FAQ; include password reset and assign an owner to exceptions.

When Conditional Access blocks registration

Requiring an Authenticator passkey for All resources can create a loop: the user needs the credential to sign in to the app where it must first be registered. Microsoft describes targeting specific applications or separating desktop and mobile policies, allowing TAP or another specified method for the mobile registration path. Register security info policies must also be satisfied. TAP does not automatically bypass a strict authentication strength. Test the route with a small group, an accountable owner and a plan to restore restrictions. The conditions and workarounds explain why adding users to a FIDO2 group alone is insufficient.

Pilot: three editorial test scenarios
SituationTestEvidence of completion
New internal employee without a credentialRegister with an allowed bootstrap method under actual Conditional AccessSubsequent sign-in to work applications
Lost phone holding an Authenticator passkeyVerify identity, issue suitable TAP and register a replacement deviceNew method works and old credential is removed
External partnerRecover in the home tenant and enter our resource tenantMFA trust and our access policies are both satisfied

A successful test on one platform does not cover all others. Repeat each relevant scenario on the operating systems, browsers and phone profiles people use. Android personal and work profiles are separate; a passkey in one is not automatically usable from the other. This table is an editorial pilot design, not a report of a customer deployment. Microsoft describes Authenticator profile constraints.

When migration is complete

Completion is neither a policy switch nor a mail-merge campaign. For every population, confirm that people have a usable phishing-resistant method, can repeat sign-in on their normal platforms and have a tested recovery route. Run a separate privileged-account exercise because of the higher risk. The later July deadline applies to Global Administrators, not automatically to every administrative role. Keep unresolved registrations, guests and exceptions in an owned register. Before tightening Conditional Access, check application and client dependencies; after rollout, review sign-in logs and support requests. Stable, verified access is the outcome to measure. If a failure requires a fallback, the team should know which approved recovery method is allowed and how to revoke a compromised credential.

  1. Reduce users with telephone-only MFA to zero or a documented, supported exception
  2. Test registration and later sign-in on devices used in real work
  3. Practice recovery without the missing credential
  4. Verify administrator, guest and SSPR scenarios separately

Frequently asked questions

Frequently asked questions

Does SMS stop working on 1 September 2026?

No. That date introduces automatic passkey enablement and registration nudges for in-scope users. Microsoft-delivered SMS and voice retire at the applicable 2027 dates in the official timeline.

Does everyone need a hardware FIDO2 key?

No. Entra supports synced and device-bound passkeys. The right choice depends on role, device, assurance and recovery; Microsoft's FAQ describes both options.

Can a regulated organization retain telephone MFA?

A supported telephony provider may be appropriate for a documented requirement, with its own contract, configuration and pilot. Microsoft still recommends passkeys as the primary path; see its provider guidance.

Is an enabled registration campaign enough?

No. A passkey nudge can be postponed. Measure registration, telephone-only accounts, sign-in success and recovery rather than campaign status alone, as the campaign guidance indicates.

Why can a valid TAP still fail to allow passkey registration?

Check TAP policy scope, single-use status, the registration window and effective Conditional Access. A strict authentication strength for All resources can block bootstrap access to Authenticator. A valid TAP is not a universal policy exemption; the registration path must explicitly support it.