Microsoft 365 and CopilotPublished Last reviewed November 20269 min read
Short answer
Since September 1, 2026, Microsoft Entra enables passkeys for users set up for SMS or voice and nudges them to register one. On February 1, 2027, Microsoft stops delivering SMS and voice codes, and users with no other method must register a passkey before they can sign in. Inventory SMS users, secure break glass and admin accounts, issue Temporary Access Passes, then move everyone else.
Check where you stand: take the Microsoft 365 security check. About two minutes, no email needed.
Update, November 2026
On September 15, 2026, Microsoft revised the timeline so Global Administrators (while the role is active) and external users keep Microsoft provided SMS and voice until July 1, 2027, while internal guests and all other users stay on February 1, 2027. Bringing your own telephony provider through Microsoft Security Store became generally available on October 30, 2026, and a November 3 notice confirmed that self service password reset also loses Microsoft provided SMS and voice after a 50 day transition once the rollout reaches each tenant.
Microsoft has put a date on the end of text message MFA in Entra ID. Passkeys became the default sign in experience on September 1, 2026, and Microsoft provided SMS and voice authentication retires on February 1, 2027. For a small or midsize tenant, it is the push to finish a move most firms keep postponing, and it goes better on your schedule than on Microsoft’s prompts.
What changed in Microsoft Entra on September 1, 2026?
Passkeys became the default authentication experience, and users enabled for SMS or voice were automatically enabled for passkeys. Microsoft’s retirement page says those users were placed in a passkey profile that allows all passkey types, and the registration campaign was set to Microsoft managed, so they are nudged to register a passkey at their next MFA sign in.
Two details matter for planning. The Microsoft managed passkey nudge can be snoozed without limit, so it will not finish the job for you. And the opt out Microsoft offers through Microsoft Graph only delays the automatic enablement until February 1, 2027. After that, a user whose only method is SMS or voice gets a blocking prompt to register a passkey, with no opt out.
Organizations with a genuine need for SMS or voice can pay for a telephony provider through Microsoft Security Store, with configuration opening on October 30, 2026. For most small firms that is a cost to avoid, not a plan.
What does the SMS and voice retirement mean for small and midsize tenants?
Every account that still signs in with a text or a call needs another method before February 1, and the ones most likely to be missed are those nobody watches, such as a shared login or a rarely used admin account.
Start with the policy, not the users. Methods could no longer be managed in the legacy MFA and self service password reset (SSPR) policies after September 30, 2025, yet the September 1 change still counted users enabled for SMS or voice in the legacy MFA settings. If Manage migration in your authentication methods policy is not at Migration Complete, finish it, so one policy decides which methods are on.
Check SSPR as well. Many tenants still accept a mobile phone for password resets, and users who lose SMS need another reset method your policy accepts.
Licensing changes what you can enforce. Authentication strengths need Conditional Access and Entra ID P1, which Microsoft 365 Business Premium includes. A tenant on security defaults can still enable passkeys, but it cannot require a phishing resistant method by policy.
Should you use passkeys in Microsoft Authenticator or FIDO2 security keys?
Both, for different people. Microsoft recommends device bound passkeys for admins and highly privileged users and synced passkeys for users without admin rights. In practice that means FIDO2 security keys or Authenticator passkeys for admins, and Authenticator or synced passkeys for everyone else.
| Option | Where the key lives | Best fit | Watch for |
|---|---|---|---|
| Passkey in Microsoft Authenticator | Device bound, in the phone’s secure hardware | Staff who carry a work or personal phone | Needs iOS 17 or Android 14 or later; cross device sign in needs Bluetooth |
| FIDO2 security key | Device bound, on the key | Admins, emergency access accounts, staff without a phone | Buying keys, keeping spares and a process for lost keys |
| Synced passkey (iCloud Keychain, Google Password Manager) | Synced through the user’s passkey provider | Most staff, with the lowest help desk load | No attestation, and you cannot see which devices hold a copy |
| Windows Hello for Business | Bound to one PC, protected by its TPM | Users on Entra joined Windows PCs | Works only on that PC, so pair it with a portable method |
Passkey profiles, generally available since March 2026, let you mix these in one tenant: device bound passkeys with attestation enforced for admins, synced passkeys allowed for staff. The September 1 change already put SMS and voice users in a profile that allows every type, so review it rather than assume it matches your intent.
How do you find out who still uses SMS or voice?
Pull two lists: who has SMS or voice registered, and who actually used it to sign in. The gap between them shows which users will notice February 1 and which just have an old number on file.
- Authentication methods activity in the Microsoft Entra admin center. The Registration tab shows users by registered method and the Usage tab shows sign ins by method. Data can lag by up to 36 hours, and usage insights need Entra ID P1 or P2.
- User registration details, in the same report or through the Microsoft Graph userRegistrationDetails report, which lists registered methods for every user.
- Entra sign in logs for the users the reports flag. The Authentication Details tab shows the method behind each MFA prompt.
- The authentication methods policy, to see which groups are enabled for SMS and Voice calls.
- The PowerShell script Microsoft links from its retirement page, which reports users enabled for SMS or voice and runs with Global Reader rights.
Put the results in one table with an owner and a target method for each person. Shared logins that use SMS get their own rows and a named owner. If you would rather have this inventory done for you, it is part of our Microsoft 365 security assessment.
How should you handle onboarding, recovery and break glass accounts?
Use a Temporary Access Pass whenever a user has no working method, and give your emergency access accounts FIDO2 security keys that no other admin uses.
Temporary Access Pass
A Temporary Access Pass (TAP) is a time limited passcode an Authentication Administrator issues so a user can sign in and register a passkey, Windows Hello for Business or a new phone. Lifetimes run from 10 minutes to 30 days, with a one hour default. A TAP satisfies Conditional Access MFA requirements, so a new hire can register without touching SMS. Pair it with a Conditional Access policy on the Register security information user action, and a help desk rule to verify identity before issuing one.
Break glass accounts
Keep at least two cloud only emergency access accounts with Global Administrator, exclude them from Conditional Access policies that could lock them out, and give them passkeys on FIDO2 security keys stored securely, separate from the methods your admins use daily. Microsoft recommends alerting on every sign in to these accounts and testing them at least every 90 days. A break glass account on SMS is the last place you want a blocking passkey prompt during an outage.
Which Conditional Access authentication strength should you require?
Require the built in Phishing resistant MFA strength for admin roles now, and extend it to everyone once your inventory shows each user has a passkey or Windows Hello for Business.
Entra ID has three built in authentication strengths: Multifactor authentication, Passwordless MFA and Phishing resistant MFA. The phishing resistant strength accepts Windows Hello for Business or a platform credential, passkeys (FIDO2) and multifactor certificate based authentication. SMS and voice count only as a second factor in the basic MFA strength. You cannot use Require multifactor authentication and Require authentication strength in the same policy, so replace the old grant rather than stacking them. Run each new policy in report only mode first.
Push approvals and codes can also be relayed by adversary in the middle kits, as we covered in our post on AiTM token theft in Microsoft 365. For firms that report against CMMC, HIPAA or SOC 2, the same policies become evidence, which our Microsoft 365 compliance work maps to those frameworks.
What rollout order works before February 1, 2027?
Protect the accounts that can lock you out, then the accounts attackers want most, then everyone else, and remove SMS last.
- Finish the authentication methods policy migration and build the SMS and voice inventory.
- Set up two emergency access accounts on FIDO2 security keys, excluded from Conditional Access, with sign in alerts.
- Move every admin to a device bound passkey and enforce the Phishing resistant MFA strength for admin roles.
- Enable Temporary Access Pass, write the help desk procedure for issuing it, and protect security info registration with Conditional Access.
- Configure passkey profiles: device bound with attestation for admins, synced allowed for staff unless a client contract requires company controlled keys.
- Switch the registration campaign from Microsoft managed to Enabled, target your SMS and voice users, and limit snoozes so the prompt leads somewhere. Tell users first.
- Decide in writing whether any group truly needs SMS or voice after February 1, and if so, evaluate a telephony provider.
- Remove SMS and Voice calls from the authentication methods policy for each group once its users have a replacement, then extend the phishing resistant strength to all users.
If you want a second look at your inventory or policy design before February, book a 30 minute call and we will talk through where your tenant stands.
Frequently asked questions
Will users be locked out of Microsoft 365 on February 1, 2027?
Not locked out, but stopped. A user whose only MFA method is Microsoft provided SMS or voice will be required to register a passkey at sign in before going further. Users who already have another registered method, such as Authenticator push, an authenticator code or a passkey, sign in as before.
Can we keep Microsoft Authenticator push notifications after SMS retires?
Yes. The retirement covers Microsoft provided SMS and voice delivery, not Authenticator push or codes. Those methods are still phishable, though, so they will not satisfy a Conditional Access policy that requires the phishing resistant strength. Treat them as a fallback while you move people to passkeys.
Do passkeys add licensing or per user costs?
Microsoft states that moving its SMS and voice users to passkeys carries no additional cost. Passkeys in Microsoft Authenticator and synced passkeys use phones people already have. FIDO2 security keys are hardware you buy, and a telephony provider for continued SMS is billed by that provider.
Does this change affect users who already use Windows Hello for Business?
They keep signing in as they do now. Users who still have SMS or voice enabled alongside Windows Hello for Business may see passkey registration prompts, which is one more reason to remove SMS and Voice calls from the policy once people have moved.
Can staff register a passkey on a personal phone?
Yes, if your passkey profile allows it. Authenticator and synced passkeys work on personal phones, and the private key stays in the phone’s secure hardware or the user’s passkey provider. If a contract requires company controlled hardware, use FIDO2 security keys and restrict models by AAGUID with attestation enforced.