Microsoft is retiring Microsoft-provided SMS and voice authentication delivery in Microsoft Entra ID in 2027. For identity and security teams, this is not simply a change in which MFA method appears on a sign-in screen. It is a deadline to identify dependencies, validate replacement authentication methods, and avoid disruption for users who still rely on text messages or phone calls.
The immediate question for administrators is practical: Which accounts still depend on SMS or voice, and how do we know when they are ready to migrate? This guide covers the exact retirement scope, a repeatable inventory workflow, KQL queries for recent sign-in activity, and a phased plan for moving users toward phishing-resistant authentication.
What Is Changing—and When?
Microsoft began automatically enabling passkey registration for users enabled for SMS or voice on September 1, 2026, with registration prompts during eligible sign-ins. The actual retirement of Microsoft-provided telephony delivery happens in stages:
| Date | Impact | | --- | --- | | September 1, 2026 | Microsoft began automatically enabling eligible SMS/voice users for passkeys and prompting registration. | | February 1, 2027 | Microsoft-provided SMS/voice delivery retires for most users, including internal guest users. | | July 1, 2027 | The retirement extends to Global Administrators and external users. |
Microsoft says that people in the affected group whose only available MFA option remains Microsoft-provided SMS or voice will face a blocking passkey registration prompt after their deadline if their organization has not configured an alternative telephony provider. That is not the same as an automatic permanent account lockout, but it can interrupt access and generate support tickets.
Important distinction: This is a retirement of Microsoft-provided SMS and voice delivery, not a declaration that every organization must abandon all telephony authentication. Organizations with documented business, regulatory, or operational needs can use a supported telephony provider through the Microsoft Security Store. The goal for most users, however, should be phishing-resistant authentication rather than a like-for-like SMS replacement.
Why SMS and Voice MFA Are No Longer Enough
SMS and voice MFA improve on passwords alone, but they remain vulnerable to phishing, social engineering, SIM swapping, and interception or redirection of one-time codes. Attackers can trick a user into entering a legitimate code into a malicious website or coerce a help desk or carrier into redirecting a phone number.
Passkeys use public-key cryptography and are bound to the legitimate service, making them resistant to the familiar credential-and-code phishing workflow. Microsoft Entra ID supports both synced and device-bound passkeys, including FIDO2 security keys and supported authenticator and platform experiences. Windows Hello for Business is another phishing-resistant option for appropriately managed devices.
There is an important policy distinction: TOTP codes remain supported, but they are not phishing-resistant. An organization that requires a phishing-resistant authentication strength in Conditional Access must select methods that satisfy that strength; moving users from SMS to a six-digit TOTP code does not meet that objective.
Step 1: Identify Users Enabled for SMS or Voice
Start with Microsoft's official SMS/voice inventory PowerShell script, linked from its retirement guidance. Microsoft recommends using it to identify accounts enabled through the authentication methods policy or legacy MFA configuration. Export the results, validate the scope, and segment the population by business unit, account type, and application criticality.
Official guide and inventory script: Passkeys by default and retirement of Microsoft-provided SMS and voice authentication.
Next, review Entra admin center → Protection → Authentication methods → User registration details (navigation may change). Microsoft Graph's userRegistrationDetails report can also help identify registration state. For example, this read-only Microsoft Graph request retrieves the registration report:
GET https://graph.microsoft.com/v1.0/reports/authenticationMethods/userRegistrationDetails
The Graph API requires the appropriate AuditLog.Read.All permission and supported directory role. Review methodsRegistered, isPasswordlessCapable, userType, and related attributes. A registered phone number (for example, mobilePhone) is a signal for investigation, not proof of current SMS-only dependence: users may have additional viable authentication methods, and registration alone does not establish whether a policy permits a method.
Create three operational groups:
- High risk of disruption: SMS/voice-only users with no validated replacement method.
- Migration in progress: Users with an alternative registered, but not yet tested for their relevant sign-in scenarios.
- Ready: Users who have successfully authenticated with an approved replacement and are no longer dependent on Microsoft-provided SMS/voice.
Check privileged accounts, break-glass design, frontline workflows, shared-device scenarios, and guest access separately. Do not assume that all guest identities or all PIM-eligible administrators share the July deadline: Microsoft's FAQ distinguishes internal guests and administrators whose Global Administrator role is not active.
Step 2: Measure Actual SMS and Voice Sign-In Usage with KQL
Registration reports tell you what users can use. Sign-in logs help you see what they actually used recently. If Entra sign-in logs are being sent to a Log Analytics workspace, use the following KQL queries as an investigation starting point.
KQL: Trend SMS and Voice Authentication Usage
SigninLogs
| where TimeGenerated >= ago(30d)
| mv-expand AuthStep = AuthenticationDetails
| extend Method = tostring(AuthStep.authenticationMethod)
| where Method has_any ("SMS", "Text message", "Voice", "Phone call")
| summarize AuthenticationSteps = count(), Users = dcount(UserPrincipalName)
by Day = bin(TimeGenerated, 1d), Method
| order by Day asc, Method asc
This query counts matching authentication steps, not unique completed user sign-ins. It depends on the AuthenticationDetails data available in your workspace and the method labels generated by your tenant. Inspect recent records and adjust the matching terms as necessary. The 30-day lookback also depends on your Log Analytics retention.
KQL: Prioritize Accounts with Recent Telephony Authentication
SigninLogs
| where TimeGenerated >= ago(30d)
| mv-expand AuthStep = AuthenticationDetails
| extend Method = tostring(AuthStep.authenticationMethod)
| where Method has_any ("SMS", "Text message", "Voice", "Phone call")
| summarize LastSeen = max(TimeGenerated),
ObservedMethods = make_set(Method, 10),
AuthenticationSteps = count(),
Apps = make_set(AppDisplayName, 10)
by UserPrincipalName, UserId
| order by LastSeen desc
Use this output to prioritize outreach and correlate with the registration inventory. Neither query proves that SMS/voice is a user's only available method or that an authentication step succeeded. To establish readiness, verify registered methods, authentication policy eligibility, successful replacement sign-ins, and critical application requirements together.
Step 3: Choose the Right Replacement Method
For most organizations, a passkey-first approach offers the clearest long-term security outcome.
| User population | Recommended starting point | | --- | --- | | Managed Windows workforce | Windows Hello for Business or approved passkeys | | Mobile and mixed-device users | Supported synced or device-bound passkeys | | Privileged administrators | Device-bound phishing-resistant methods, with tested recovery procedures | | Shared-device/frontline users | Pilot supported FIDO2/passkey options that fit the workflow | | Documented telephony exceptions | Evaluate a Microsoft Security Store telephony provider, with a defined exception review |
Do not assume that turning on passkeys automatically makes every device, browser, user journey, or relying application ready. Pilot registration, authentication, recovery, and Conditional Access behavior under real conditions. Confirm that users can complete both normal sign-in and recovery without depending on retired delivery channels.
Step 4: Build a Migration Runbook Before February 2027
A practical migration can be managed in five phases:
- Inventory: Export policy-enabled SMS/voice users, registration status, and recent telephony usage; establish a baseline.
- Segment: Separate high-impact users, privileged accounts, internal guests, external users, and genuine telephony exceptions. Assign the applicable deadline.
- Pilot: Enable approved phishing-resistant methods, test sign-in and account recovery, and validate device/browser support and Conditional Access.
- Migrate: Target the remaining dependent users with communications and supported registration campaigns. Track completion and help-desk failures.
- Verify: Confirm successful use of replacement methods, remove unnecessary SMS/voice policy scope when appropriate, and re-run the inventory before the deadline.
Useful program measures include accounts still dependent on SMS/voice, percentage with a tested phishing-resistant method, users blocked during registration, and exceptions with an approved telephony plan. Review these weekly as the deadlines approach.
Microsoft documents a temporary opt-out for portions of automatic passkey enablement and registration campaign behavior, but there is no opt-out from the applicable 2027 retirement enforcement. A temporary delay is not a migration strategy.
Common Mistakes That Can Cause Sign-In Disruption
Mistake 1: Counting registrations instead of dependencies. Having a phone number on file does not mean a user signs in with SMS; having a passkey registered does not guarantee it works in every required scenario.
Mistake 2: Treating February 1 as everyone's deadline. Global Administrators and external users have a different date, while internal guests remain in the February group. Validate role state and user classification.
Mistake 3: Assuming TOTP is equivalent to a passkey. TOTP can be a supported fallback, but it does not deliver phishing resistance or satisfy phishing-resistant Conditional Access requirements.
Mistake 4: Migrating users without testing recovery. Registration, lost-device processes, privileged access, and emergency access procedures should be exercised before legacy delivery is withdrawn.
Mistake 5: Waiting for a blocking prompt to drive migration. A forced registration flow may eventually get users migrated, but a planned rollout gives IT control over communications, readiness, and support demand.
Where AzureWise Fits into MFA Migration Readiness
The 2027 change reinforces a broader identity security principle: MFA coverage is not the same as MFA strength or operational readiness. Security teams need ongoing visibility into risky sign-ins, identity configuration, and privileged access—not only a one-time registration export.
AzureWise provides an Entra ID identity security assessment and KQL-based investigation resources designed to help teams review identity risk and prioritize remediation. Use Microsoft's official retirement inventory together with sign-in telemetry and your own migration tracking; do not treat a general identity scorecard as a substitute for a purpose-built SMS/voice retirement readiness report.
Final Takeaway
The deadline is a reason to act, not a reason to panic. Identify users still dependent on Microsoft-provided SMS and voice, validate replacement methods before the relevant 2027 date, and track real sign-in behavior until the exposure is closed. Organizations that do the inventory now can use the retirement as an opportunity to replace phishable MFA with more resilient authentication—and avoid preventable sign-in disruption.
Microsoft Documentation and Further Reading
- Passkeys by default and retirement of Microsoft-provided SMS and voice authentication
- SMS and voice retirement FAQ
- Microsoft Graph: userRegistrationDetails
Published: November 15, 2026. Review Microsoft's documentation for timeline or product changes before implementing a migration.
Want the Azure identity assessment already built?
AzureWise Identity Security Assessment turns Microsoft Entra ID telemetry into a weighted Security Rating, detailed findings, and prioritized remediation guidance inside Azure Monitor.
Get AzureWise — $99