Microsoft Entra ID: Reminder to migrate from Microsoft-provided SMS and voice authentication
Returned by 2 reference tenants · Corroborated by Microsoft 365 Message Center Archive by Merill FernandoAction date
What the notice says
Microsoft’s text, safely structuredWhat and why
This is a reminder of the upcoming retirement of Microsoft-provided SMS and voice authentication in Microsoft Entra ID, previously announced in MC1426371 (July 13, 2026) and MC1434201 (GCC, July 20, 2026).
Microsoft-provided SMS and voice authentication will retire starting February 1, 2027. Complete your migration before rollout begins to avoid interrupting users' sign-in experience.
SMS and voice are vulnerable to phishing and SIM-swap attacks. Microsoft recommends passkeys for stronger, phishing-resistant protection. You can also migrate to another supported authentication method or retain SMS and voice by configuring a customer-managed telecom provider (CYOT) through the Microsoft Security Store.
Rollout schedule
- Retirement (Worldwide and GCC): Beginning February 1, 2027, and expected to complete in early February 2027.
- Complete migration or configure CYOT before February 1, 2027, rather than waiting for the rollout to reach your tenant.
Impact on your organization
Who is affected
- Organizations and users that rely on Microsoft-provided SMS or voice authentication
- Customer-managed telecom providers configured through the Microsoft Security Store are not affected.
Platforms and services
- Microsoft Entra ID authentication
What will happen
- Users with another registered sign-in method will use that method. They will not be required to register a passkey to continue signing in.
- Users whose only registered sign-in method is SMS or voice can use SMS or voice one final time to verify their identity. They must then register a passkey before continuing sign-in.
Action required and recommendations
If your organization uses Microsoft-provided SMS or voice, complete these steps before February 1, 2027:
- Identify affected users. Review who relies on SMS or voice, especially users with no other registered sign-in method.
- Complete migration. Help affected users register and start using passkeys or another supported authentication method before rollout begins.
- Configure CYOT if you need to retain SMS or voice. Configure a customer-managed telecom provider through the Microsoft Security Store before rollout begins.
- Notify users and your helpdesk. Explain the deadline, required actions, and the passkey-registration requirement for users who only have SMS or voice registered.
If your organization does not use Microsoft-provided SMS or voice, no action is required for this retirement.
Learn more
Compliance considerations
No compliance considerations identified. Review as appropriate for your organization.
What changed
Between the versions this installation saw, newest firstThis installation has seen one version of this notice, first on 27 Oct 2026. Later changes will show here.
Archive version history
Microsoft 365 Message Center Archive by Merill FernandoThese 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 This is a reminder of the upcoming retirement of Microsoft-provided SMS and voice authentication in Microsoft Entra ID, previously announced in MC1426371 (July 13, 2026) and MC1434201 (GCC, July 20, 2026). Microsoft-provided SMS and voice authentication will retire starting February 1, 2027. Complete your migration before rollout begins to avoid interrupting users' sign-in experience. SMS and voice are vulnerable to phishing and SIM-swap attacks. Microsoft recommends passkeys for stronger, phishing-resistant protection. You can also migrate to another supported authentication method or retain SMS and voice by configuring a customer-managed telecom provider (CYOT) through the Microsoft Security Store. Rollout schedule Retirement (Worldwide and GCC): Beginning February 1, 2027, and expected to complete in early February 2027. Complete migration or configure CYOT before February 1, 2027, rather than waiting for the rollout to reach your tenant. Impact on your organization Who is affected Organizations and users that rely on Microsoft-provided SMS or voice authentication Customer-managed telecom providers configured through the Microsoft Security Store are not affected. Platforms and services Microsoft Entra ID authentication What will happen Users with another registered sign-in method will use that method. They will not be required to register a passkey to continue signing in. Users whose only registered sign-in method is SMS or voice can use SMS or voice one final time to verify their identity. They must then register a passkey before continuing sign-in. Action required and recommendations If your organization uses Microsoft-provided SMS or voice, complete these steps before February 1, 2027: Identify affected users. Review who relies on SMS or voice, especially users with no other registered sign-in method. Complete migration. Help affected users register and start using passkeys or another supported authentication method before rollout begins. Configure CYOT if you need to retain SMS or voice. Configure a customer-managed telecom provider through the Microsoft Security Store before rollout begins. Notify users and your helpdesk. Explain the deadline, required actions, and the passkey-registration requirement for users who only have SMS or voice registered. If your organization does not use Microsoft-provided SMS or voice, no action is required for this retirement. Learn more Migration guidance Passkeys in Microsoft Entra ID Choose a telephony provider for SMS and voice authentication - Microsoft Entra ID | Microsoft Learn Compliance considerations No compliance considerations identified. Review as appropriate for your organization.
- Microsoft Entra ID: Reminder to migrate from Microsoft-provided SMS and voice authentication Action date: 1 Feb 2027
Learn more
Links from the notice and their documentation checks- Migration guidance
- Passkeys in Microsoft Entra IDChecked 9 Nov 2026
- Choose a telephony provider for SMS and voice authentication - Microsoft Entra ID | Microsoft LearnChecked 9 Nov 2026
This site links to Microsoft's pages instead of copying them. Installations inside an organization can keep a copy for comparison.
Notices it cites
Other posts named in this one- MC1426371 · (Updated) Microsoft Entra: Passkeys by default and retirement of Microsoft-provided SMS and voice authenticationPlan for change · changed 15 Sep 2026Returned by 2 reference tenants · Corroborated by Microsoft 365 Message Center Archive by Merill Fernando
- MC1434201 · Cited notice · metadata unavailableCoverage gap · We haven't seen Microsoft's notice.
Related public evidence
- Community source · 1 Nov 2026Entra 🆔 News #173 → This week in Microsoft Entra
- Public source · 8 Oct 2026MC1459133: (Updated) Microsoft Entra ID: Passkey support for B2B users Microsoft 365 Message Center Archive by Merill Fernando
- Community source · 20 Sep 2026Entra 🆔 News #167 → This week in Microsoft Entra
- Public source · 18 Sep 2026MC1474104: Microsoft Entra ID: Follow-up on SMS first-factor sign-in retirement and upcoming changes Microsoft 365 Message Center Archive by Merill Fernando
- Public source · 15 Sep 2026MC1426371: (Updated) Microsoft Entra: Passkeys by default and retirement of Microsoft-provided SMS and voice authentication Microsoft 365 Message Center Archive by Merill Fernando
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.