Microsoft 365 text code sign in starts retiring 1 February. Find who still uses it.
Microsoft Entra ID begins retiring its own text message and voice call codes for most users on 1 February 2027. Anyone whose only second factor is a phone number will then have to register a passkey before their sign in can finish.
From 1 February 2027 Microsoft begins retiring the text and voice codes it sends for Microsoft 365 sign in, and there is no opt out. People with only a phone number registered will meet a prompt they cannot skip. Move them to the Authenticator app or a passkey in January, and treat the paid telephony provider route as a last resort.
1 Feb 2027: Microsoft begins retiring text and voice codes
If your organization switched on multifactor sign in the easy way, with a mobile number and a code sent by text, Microsoft is about to take that option away. From 1 February 2027, Microsoft Entra ID, which handles sign in for Microsoft 365, begins retiring the text message and voice call codes that Microsoft delivers itself. From the day this was published, that is 76 days away. Take out weekends, the last two weeks of December and US Thanksgiving, and about 42 working days remain.
What changed
Microsoft announced the plan on 13 July 2026. Since 1 September, anyone enabled for text or voice has also been enabled for passkeys and nudged to register one. A passkey is a sign in key kept on the person's phone, laptop or a small security key, used in place of a code sent by text. By default that nudge can be snoozed without limit.
On 1 February the snooze ends for everyone except Global Administrators and external users, whose date is 1 July 2027. When a person's date arrives, if their only second factor is a phone number, they have to register a passkey before the sign in will finish. Microsoft's FAQ is blunt: "There is no opt out for enforcement." The temporary opt out only delays the passkey nudges, and only until 1 February.
On 5 November Microsoft added a follow up message center post, MC1540327. The dates are phased starting points, and Microsoft says it cannot tell you which day your tenant will be reached. And some sign in sessions cannot register a passkey at all: embedded browsers, certain browser and operating system combinations, apps without a supported authentication broker. Someone with only a phone number on file who signs in through one of those is stuck until an administrator helps.
- 1 Sep 2026Passkeys switched on for everyone enabled for text or voice. Prompts to register begin and can be snoozed.
- 30 Oct 2026Paid telephony providers can be set up through the Microsoft Security Store.
- 1 Feb 2027Retirement begins for all users except Global Administrators and external users. The prompt can no longer be skipped.
- 1 Jul 2027Retirement begins for Global Administrators and external users.
Who this affects
Anyone still enabled for text or voice codes, whether through the current authentication methods policy or the older per user MFA settings. Self service password reset is covered too.
Microsoft says people who already use codes from an authenticator app will not get the blocking prompt.
Size it before you worry about it. Say you have 80 accounts and a quarter still rely on a text code. That is 20 people. Allow ten minutes each and you have 200 minutes of work, a little over three hours. The ten minutes is our allowance, not Microsoft's. Leave it, and the same 20 people meet a prompt they cannot skip on a day you did not choose, some of them inside an app that cannot complete it.
Three ways out
A passkey is what Microsoft wants you to pick, and it says the move itself carries no additional cost. The passkey can sync through iCloud Keychain or Google Password Manager, or stay on one device: the Authenticator app, a Windows PC, a hardware security key.
The Authenticator app, with approvals or codes, remains available after February. Microsoft points out that app codes are not phishing resistant, so they will not satisfy a Conditional Access policy that demands it. If you have no such policy, the app is the quickest fix for people whose devices or apps fight with passkeys.
The third route keeps text and voice by paying for them. Since 30 October you can subscribe to a telephony provider in the Microsoft Security Store (Soprano, Telesign and Infobip are listed) and wire it in through your own Azure subscription. You pay the provider for messages and calls, and Azure for the resources that host the integration. Microsoft frames this as an option for organizations with a regulatory or operational need for a phone channel, and that is the right framing. For a 40 person office it is a lot of plumbing to keep a method Microsoft no longer considers secure.
What to do this month
Start with names. Microsoft publishes a read only analyzer script on GitHub, but it only reports whether the text and voice policies are on and which groups they target. For individuals, open the Entra admin center and go to Entra ID, Authentication methods, Activity, where you can see who is registered for each method. That report needs an Entra ID P1 or P2 license. If MC1540327 is in your message center, it comes with a list of affected users for your tenant.
Then check where people sign in. A current browser on a current laptop is the easy case. An older app with its own built in sign in window is where the trouble hides, so test those first.
Pick one default replacement, give staff a date in January, and work through them in batches. Do the admin accounts first. The July date for Global Administrators is not a reason to leave your most powerful accounts on a text code for five more months.
Where X-Axis fits
X-Axis provides Microsoft 365 services to organizations across the United States and Canada, and sign in cleanup like this is part of that work. If you would rather not spend January chasing phone numbers, tell us how many accounts you have and we will tell you what the job involves.
Do this month
Tick them off as you go. Nothing is saved or sent.
Sources
- Microsoft Learn: Passkeys by default and the retirement of SMS and voice authentication
- Microsoft Learn: Frequently asked questions about the SMS and voice retirement
- Microsoft 365 message center post MC1540327, 5 November 2026 (public mirror)
- Microsoft Learn: Frequently asked questions about telephony providers
- Microsoft Security Blog: passkeys are the default authentication method in Entra ID, 13 July 2026
- Microsoft Learn: Authentication methods activity report
- GitHub: Microsoft's SMS and voice usage analyzer script
Want a second pair of eyes on this?
See our Microsoft 365 services