Microsoft Entra ID
Authentication

Customer intent: As an IT administrator, I want to understand retirement behavior so that I can prepare users, authentication policies, and recovery…

In brief

The article now presents the retirement behavior directly, including the 50-day SSPR grace period, entry-point banner, and editable passkey and retirement settings.

What Entra admins need to know

Administrators can use the revised article as the current reference for the retirement experience; no action is specified.

This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

This article explains the user and admin experiences when retirement reaches your tenant. For preparation steps and the full timeline, see Passkeys by default and retirement of Microsoft-provided SMS and voice authentication.

At a glance

The key distinction is whether the user has already registered an alternative authentication method other than SMS or voice and can use it for the current sign-in. A device-bound passkey on another device doesn't provide an alternative for a session where that passkey isn't available.

If a user reaches this screen, direct them to My Sign-Ins and have them use their existing SMS or voice registration to verify their identity and register another method. If they can't complete registration or still can't sign in, contact your support team. Don't tell them to skip registration or assume another SMS code allows them to continue to the application. Confirm the replacement method works with their actual session and access policies, not just their primary browser.

Scenario 5: The user's only alternative is a device-bound passkey on another device

The user has SMS or voice registered, but their only other registered authentication method is a device-bound passkey. If that passkey isn't available for the current sign-in, its registration alone doesn't prevent the blocking passkey prompt.

What changes in My Sign-Ins

When sign-in retirement reaches the tenant, the product specification describes these changes forapply to Microsoft-provided SMS and voice registrations:

  • Existing SMS and voice registrations appear disabled or greyed out.
  • Users can't edit or replace the phone number for those registrations.

When settings become editable again

The following table summarizes the planned admin experience after retirement reaches the tenant. Retirement-locked SMS and voice group targeting remains read-only until you configure a telephony provider (CYOT), even if you turn both methods off. Passkey settings and the retirement profile remain editable.

Tenant state SMS and voice settings Passkey settings

SSPR has a separate grace period

The approved source specification describesSSPR has a tenant-specific 50-day SSPR grace period:

Stage Sign-in SSPR

This feature lets eligible users change their cloud password from Security info in My Sign-Ins without entering their current password, after signing in with a supported passwordless method such as a passkey. It's separate from SSPR and doesn't require SSPR registration.

The source specification describes aA banner appears at the SSPR entry point for tenants where this feature is enabled. It doesn't automatically redirect Forgot my password to My Sign-Ins.

What happens to NPS and RADIUS

Customer-managed telephony doesn't change the methods supported by the client. Validate the provider, deployment, and connection together rather than assuming every telephony option works with every NPS flow.

Apps and protocols that don't support passkeys

Passkey support is a property of the complete sign-in path, not just your tenant. Check the app, protocol, browser or broker, device, and tenant policy together.

Don't weaken Conditional Access or turn off MFA as a retirement workaround. Test a replacement path that meets your security requirements.

Prepare your organization

Complete the following before the applicable retirement rollout starts:

This precedence is about the prompt shown to the user, not a policy bypass. Passkey registration still respects the user's assigned profiles, and completing registration doesn't override Conditional Access requirements for access to the application. See Custom authentication strengths can prevent passkey sign-in.

Review before publication

This section is for the documentation and product reviewers. The following bullets are independent verification items, not sequential procedure steps. Resolve them and remove all review notes before publishing.

  • Confirm the 50-day SSPR grace period and timing rules. The three newly supplied sources don't cover SSPR, so its existing guidance still needs source confirmation.
  • Confirm final admin labels, banners, passkey profile behavior, and the registration campaign's editable controls.
  • Confirm method-management behavior for users migrated to a telephony provider.
  • Confirm final screen text, helpdesk recovery actions, and error-specific retries. For unsupported browser/device sessions, the supplied screen points to aka.ms/addpasskey on another device or the help desk. Preserve the separate, author-confirmed My Sign-Ins recovery path for registering another method.
  • Confirm final NPS error text and any additional unsupported-protocol scenarios without inventing error codes or redirect promises. Preserve the deployment-specific TOTP restrictions and supported customer-managed telephony option.
  • Align the retirement overview and FAQ with the more detailed SSPR timing and identity verification behavior described here.
  • Confirm password change after secure sign-in availability and links.

Related content

Daily Entra.News

Get daily email updates

Get a concise summary of the latest Microsoft Entra updates delivered straight to your inbox.

Loading the secure signup form…