MC1536049: Microsoft Entra ID Retires Microsoft-Provided SMS and Voice Authentication for Self-Service Password Reset

MWPRO IMPACT SCORE
OPERATIONAL IMPACT
70
0 25 50 75 100
HIGH IMPACT • REVIEW RECOMMENDED
Recommended Action:
Review the update and plan any required actions before rollout.
▶ What is MWPro Impact Score? Watch our 60‑second explainer

Primary Audience

Tenant AdminsMicrosoft 365 AdminsSecurity TeamsCompliance TeamsIT ManagersService Owners
Why this score?
AI Confidence
HIGH
Enough detail is available to trust this assessment.
Assessment Reasoning
This announcement confirms retirement of Microsoft-provided SMS and voice authentication for self-service password reset in Entra ID from 2027, requiring admins to prepare alternative recovery options. Admins must identify affected users, configure supported telephony or other SSPR methods, and update helpdesk processes. User experience is indirectly affected due to potential loss of password recovery capability. As the change is future-dated, urgency is moderate but implementation planning is significant.
85
🛡️ Admin Impact
60
👥 User Impact
55
⚡ Urgency
70
🔧 Effort
ℹ️ WHAT YOU NEED TO KNOW
📌

AT A GLANCE

Microsoft-provided SMS and voice authentication will retire for Entra ID self-service password reset. Admins must plan new recovery options to avoid users losing password reset capability.
👥

END USERS

Users relying on Microsoft SMS or voice for password reset may lose this option after the transition period.
🛡️

IT ADMINS

Identify affected users and set up alternative recovery methods or supported telephony providers well before rollout reaches your tenant.
📅

ROLLOUT TIMELINE

Upcoming:
February 2027

📢 Official Microsoft Message Center Announcement


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

[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.

Learn more

[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.

Source: Microsoft Message Center • Analysed by MWPro

Share This Update