Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 275/275 feeds/APIs · 469/469 docs · 8/9 advisories · checked 18:10 UTC Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Entra ID: Microsoft-provided SMS and voice authentication to retire for self-service password reset (SSPR)

Returned by 2 reference tenants · Corroborated by Microsoft 365 Message Center Archive by Merill Fernando

Action date

22 Mar 2027 in 4 months Act by , as Microsoft's metadata states

What the notice says

Microsoft’s text, safely structured

What and why

As Microsoft-provided SMS and voice authentication retire in Microsoft Entra ID, these methods will also become unavailable for SSPR. Organizations have 50 days after the applicable sign-in retirement rollout reaches their tenant to prepare alternative recovery methods. Users may still be able to sign in but lose the ability to reset forgotten passwords. Passkeys and other sign-in methods don't automatically satisfy SSPR requirements. Admins should identify affected users and ensure they have enough eligible recovery methods to prevent disruptions and increased helpdesk requests.

Rollout schedule

  • General Availability (Worldwide, GCC): We expect rollout to begin and complete in February 2027
User populationSign-in retirement rollout beginsSSPR transition ends
Users other than Global Administrators and external usersFebruary 1, 202750 days after this rollout reaches your tenant
Global Administrators and external usersJuly 1, 202750 days after this separate rollout reaches your tenant

These are phased rollout start dates, not a single SSPR cutoff for every organization. Each population's 50-day period begins when its applicable rollout reaches your tenant.

Impact on your organization

Who is affected

  • Organizations with users who rely on Microsoft-provided SMS/voice to meet their password-reset verification requirements. This includes users who have another sign-in method but still depend on SMS/voice for password recovery.

Platforms and services

  • Microsoft Entra ID SSPR

What will happen

When the applicable sign-in retirement rollout reaches your tenant:

  • 50-day transition: Existing SMS and voice registrations remain usable for SSPR under your current recovery policy.
  • Registration changes: SMS/voice SSPR registration and refresh prompts stop, but prompts for other eligible methods continue.
  • My Sign-Ins: Users can no longer add SMS/voice methods or edit authentication phone numbers. Existing phone registrations appear disabled, even while usable for SSPR during the transition.
  • Customer-managed telephony (CYOT): Recovery through supported providers remains available.

After the 50-day transition period:

Microsoft-provided SMS and voice are no longer available as SSPR recovery options.

User's remaining eligible recovery methodsPassword-reset experience
Enough methods to meet the applicable SSPR requirementUser can continue resetting their password with those methods
Not enough methods to meet the applicable SSPR requirementUser cannot complete SSPR and is directed to contact their administrator

The applicable one/two method requirement still applies. To retain SMS/voice for recovery, your organization must configure a supported CYOT.

Microsoft will not automatically change your SSPR policy or enable Allow password change after secure sign-in for your tenant.

Action required and recommendations

Prepare affected users before their applicable 50-day transition period ends:

  1. Identify affected users. Find users relying on SMS/voice for SSPR, even if they have other sign-in methods registered. Use the SMS and voice retirement and migration guidance.
  2. Prepare alternative recovery methods. Ensure users have enough eligible methods to meet SSPR policy requirements without Microsoft-provided SMS/voice. Passkeys alone don't satisfy SSPR requirements. If phone recovery is needed, configure and test a supported telephony provider before the transition ends.
  3. Test and communicate. Verify password recovery works with your SSPR policies and Conditional Access settings. Inform users and helpdesk staff about deadlines, registration steps, and support options.

Recommended: Let passkey users change a forgotten password

  • Where available, administrators can enable Allow password change after secure sign-in for eligible users. Users can then sign in with their passkey and change their password in My Sign-Ins without knowing/entering their current password.

Compliance considerations

If your organization needs phone-based recovery for regulatory or operational reasons, plan and validate a supported customer-managed provider before the applicable SSPR cutoff.

What changed

Between the versions this installation saw, newest first

This installation has seen one version of this notice, first on 3 Nov 2026. Later changes will show here.

These are the archive's capture times. They are separate from the versions returned by our reference tenants.

Read the archive's current copy

What and why As Microsoft-provided SMS and voice authentication retire in Microsoft Entra ID, these methods will also become unavailable for SSPR. Organizations have 50 days after the applicable sign-in retirement rollout reaches their tenant to prepare alternative recovery methods. Users may still be able to sign in but lose the ability to reset forgotten passwords. Passkeys and other sign-in methods don't automatically satisfy SSPR requirements. Admins should identify affected users and ensure they have enough eligible recovery methods to prevent disruptions and increased helpdesk requests. Rollout schedule General Availability (Worldwide, GCC): We expect rollout to begin and complete in February 2027 User population Sign-in retirement rollout begins SSPR transition ends Users other than Global Administrators and external users February 1, 2027 50 days after this rollout reaches your tenant Global Administrators and external users July 1, 2027 50 days after this separate rollout reaches your tenant These are phased rollout start dates, not a single SSPR cutoff for every organization. Each population's 50-day period begins when its applicable rollout reaches your tenant.  Impact on your organization Who is affected Organizations with users who rely on Microsoft-provided SMS/voice to meet their password-reset verification requirements. This includes users who have another sign-in method but still depend on SMS/voice for password recovery. Platforms and services Microsoft Entra ID SSPR What will happen When the applicable sign-in retirement rollout reaches your tenant: 50-day transition: Existing SMS and voice registrations remain usable for SSPR under your current recovery policy. Registration changes: SMS/voice SSPR registration and refresh prompts stop, but prompts for other eligible methods continue. My Sign-Ins: Users can no longer add SMS/voice methods or edit authentication phone numbers. Existing phone registrations appear disabled, even while usable for SSPR during the transition. Customer-managed telephony (CYOT): Recovery through supported providers remains available. After the 50-day transition period: Microsoft-provided SMS and voice are no longer available as SSPR recovery options. User's remaining eligible recovery methods Password-reset experience Enough methods to meet the applicable SSPR requirement User can continue resetting their password with those methods Not enough methods to meet the applicable SSPR requirement User cannot complete SSPR and is directed to contact their administrator The applicable one/two method requirement still applies. To retain SMS/voice for recovery, your organization must configure a supported CYOT. Microsoft will not automatically change your SSPR policy or enable Allow password change after secure sign-in for your tenant. Action required and recommendations Prepare affected users before their applicable 50-day transition period ends: Identify affected users. Find users relying on SMS/voice for SSPR, even if they have other sign-in methods registered. Use the SMS and voice retirement and migration guidance. Prepare alternative recovery methods. Ensure users have enough eligible methods to meet SSPR policy requirements without Microsoft-provided SMS/voice. Passkeys alone don't satisfy SSPR requirements. If phone recovery is needed, configure and test a supported telephony provider before the transition ends. Test and communicate. Verify password recovery works with your SSPR policies and Conditional Access settings. Inform users and helpdesk staff about deadlines, registration steps, and support options. Recommended: Let passkey users change a forgotten password Where available, administrators can enableAllow password change after secure sign-in for eligible users. Users can then sign in with their passkey and change their password in My Sign-Ins without knowing/entering their current password. Learn more SMS and voice retirement and migration guidance How Microsoft Entra self-service password reset works Choose a telephony provider for SMS and voice authentication Compliance considerations If your organization needs phone-based recovery for regulatory or operational reasons, plan and validate a supported customer-managed provider before the applicable SSPR cutoff.

  1. Microsoft Entra ID: Microsoft-provided SMS and voice authentication to retire for self-service password reset (SSPR) Action date: 22 Mar 2027

Learn more

Links from the notice and their documentation checks

This site links to Microsoft's pages instead of copying them. Installations inside an organization can keep a copy for comparison.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
  • Some history or links were left out of the website export to keep it within its size limits.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 9 Nov 18:10 UTC · 275 of 275 readable · 273 fully read · documentation 469/469 current