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
@@ -3,7 +3,7 @@ title: What happens when Microsoft-provided SMS and voice retire description: Understand the SMS and voice retirement experience for users and administrators, including sign-in, password reset, NPS, and apps that don't support passkeys. ms.topic: concept-article ms.custom: msecd-doc-authoring-1026-ms.date: 11/13/2026+ms.date: 11/16/2026 ai-usage: ai-generated # Customer intent: As an IT administrator, I want to understand retirement behavior so that I can prepare users, authentication policies, and recovery paths before enforcement. ---@@ -14,9 +14,6 @@ Microsoft-provided SMS and voice authentication retirement starts rolling out on 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](concept-sms-voice-retirement.md). -> [!IMPORTANT]-> **Review draft, not ready for publication.** This article describes behavior from product specifications approved for this draft. Confirm the SSPR timing, final UI, and items in [Review before publication](#review-before-publication) before publishing.- ## 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.@@ -151,8 +148,6 @@ If SMS or voice is still required, configure a supported [customer-managed telep If a user reaches this screen, direct them to [My Sign-Ins](https://aka.ms/mysignins) 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. -<!-- TODO: Confirm error-specific retry behavior and helpdesk actions if the user can't register another method through My Sign-Ins. -->- ### 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.@@ -188,7 +183,7 @@ Test with representative users under the affected policies. Verify both passkey ## What changes in My Sign-Ins -When sign-in retirement reaches the tenant, the product specification describes these changes for Microsoft-provided SMS and voice registrations:+When sign-in retirement reaches the tenant, these changes apply 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.@@ -283,7 +278,7 @@ Unlike Scenario 5, this user has no permitted passkey registration path on the i ### 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.+The following table summarizes the 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 | | --- | --- | --- |@@ -310,7 +305,7 @@ Sign-in and self-service password reset are separate. A user can retain sign-in ### SSPR has a separate grace period -The approved source specification describes a **tenant-specific 50-day SSPR grace period**:+SSPR has a **tenant-specific 50-day grace period**: | Stage | Sign-in | SSPR | | --- | --- | --- |@@ -354,7 +349,7 @@ The retirement doesn't automatically enable [password change after secure sign-i This feature lets eligible users change their cloud password from **Security info** in [My Sign-Ins](https://aka.ms/mysignins) 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 a banner at the SSPR entry point for tenants where this feature is enabled. It doesn't automatically redirect **Forgot my password** to [My Sign-Ins](https://aka.ms/mysignins).+A 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](https://aka.ms/mysignins). ## What happens to NPS and RADIUS @@ -384,8 +379,6 @@ If SMS or voice is still required, configure a supported [customer-managed telep 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. -<!-- TODO: Confirm final NPS failure text with the NPS owners and align existing NPS documentation that lists Microsoft-provided SMS or voice before publication. -->- ## 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.@@ -403,8 +396,6 @@ Registering a passkey on another device can prepare a user for supported passkey Don't weaken Conditional Access or turn off MFA as a retirement workaround. Test a replacement path that meets your security requirements. -<!-- TODO: Confirm any additional app/protocol scenarios and their exact failure behavior. The supplied sources cover unsupported browser/device sessions and NPS, but don't establish a complete protocol list, error text, or automatic redirects. -->- ## Prepare your organization Complete the following before the applicable retirement rollout starts:@@ -454,18 +445,6 @@ Within the SMS/voice-only retirement flow, **the blocking retirement prompt take 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](#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 - [SMS and voice retirement overview](concept-sms-voice-retirement.md). 