Microsoft Is Ending Text-Message Sign-In Codes on February 1. What Does Our Office Need to Do?

Microsoft stops sending its own text and phone-call sign-in codes on Feb 1, 2027. Here's who in your office is affected and how to move them to passkeys.

2026-11-20 · Chris Coulson

A hand holding a phone showing a Microsoft verification code text message, crossed out with a big red X, with the headline Text codes are done. Microsoft ends SMS sign-in Feb 1.

If anyone in your office still signs in to Microsoft 365 with a code sent by text message or a phone call, that stops working the way it does today on February 1, 2027. Microsoft is retiring the text and voice codes it sends itself. Your staff need to move to a passkey (in the Microsoft Authenticator app, Windows Hello, or a security key) before then. If they don't, Microsoft will make them set one up the next time they sign in, and they can't skip it.

This isn't a reason to panic, but it's a reason to act this winter instead of the morning of February 1.

What exactly is changing?

Microsoft has published the timeline on its own retirement page.

Microsoft text and phone-call sign-in code timeline: since September 1, 2026, people who use text or phone codes are being asked to set up a passkey when they sign in; on February 1, 2027, Microsoft stops providing text and voice codes for everyone except Global Administrators and external users, and anyone whose only sign-in method is a text or call has to register a passkey before they can get in, with no opt-out; on July 1, 2027, the same thing happens for Global Administrators and external users.
Microsoft's published timeline for retiring the text and phone-call sign-in codes it sends itself.

Microsoft's reason is simple: text codes can be phished, intercepted, or stolen through a SIM swap. Passkeys are built so a fake login page can't capture them.

Who in our office does this affect?

Usually it's a handful of people, not everyone.

Who this usually affects: people who set up their sign-in years ago and never added the Authenticator app; staff who don't want a work app on their personal phone, so they picked "text me"; a shared front-desk or warehouse login that sends its code to an office phone; and the owner or a long-time admin account, which is often the oldest setup in the building. Your IT provider can pull a list of exactly who still uses text or voice. Start there. Don't guess.
It's usually a handful of people. Have your IT provider pull the list rather than guessing.

Microsoft publishes a report script for this, and it takes minutes.

What should we move people to?

In order of what we usually recommend.

What to move people to, in the usual recommended order: a passkey in Microsoft Authenticator on the person's phone, the easiest switch for most staff, who approve sign-ins with their face or fingerprint; Windows Hello on their work computer, for people who mostly sign in from one PC; and a hardware security key, a small USB or tap key, for anyone who won't put a work app on a personal phone, for shared or front-desk situations, and as a strong choice for admin accounts. If someone doesn't want a work app on their personal phone, that's a fair concern, and a security key solves it without a fight.
The usual order: a passkey in Microsoft Authenticator, then Windows Hello, then a hardware security key.

Can't we just keep text codes?

Technically, yes. Microsoft now lets businesses buy text and voice delivery from an outside telephone provider through its Security Store. That requires an eligible paid Azure subscription, a provider contract, and ongoing per-message costs.

For most small and mid-sized offices around here, that's the wrong fix. You'd be paying to keep the weakest sign-in method alive. Microsoft itself says to use it only where there's a real business, regulatory or technical need. We'd rather spend that effort getting people onto passkeys once.

A simple plan for the next ten weeks

Work through it in this order.

A simple plan for the next ten weeks: get the list of who in your tenant still uses text or voice codes; tell your team what's coming with a short email that Microsoft is retiring text codes and you'll help them set up a passkey; do the switch in small groups, in person or on a quick call; handle the odd cases, including shared logins, front-desk phones, people without smartphones, and outside contractors; fix the admin accounts too, even though their deadline is July; and check again in mid-January that nobody is left on text codes only.
A simple ten-week plan to move people off text and phone-call codes before February 1.

Questions owners ask

When does Microsoft stop sending text-message sign-in codes?

Microsoft stops providing its own text and phone-call codes on February 1, 2027 for most users. Global Administrators and external users follow on July 1, 2027.

What happens if someone in our office is still on text codes after February 1?

If text or a phone call is their only sign-in method, Microsoft will require them to register a passkey before they can continue signing in. The prompt can't be skipped.

What is the passkey prompt my staff keep seeing?

Since September 1, 2026, Microsoft has been asking people who use text or phone codes to set up a passkey when they sign in. It's an early nudge ahead of the February 1 retirement.

Do we have to pay for anything?

Not to switch to a passkey in Microsoft Authenticator or Windows Hello. Hardware security keys cost money per key. Keeping text codes means buying delivery from an outside telephone provider, which most small offices don't need.

What if an employee won't use a work app on their personal phone?

Give them a hardware security key, or use Windows Hello on their work computer. Both meet Microsoft's requirement without putting anything on their phone.

Want a hand with it?

Coulson Technologies helps businesses across York, Lancaster, Harrisburg and South Central PA run their Microsoft 365. If you'd like us to pull your list of text-code users and plan the switch with you, reach out. Related: our Microsoft 365 services and Copilot Chat limits: do we need to buy Copilot?

Sources