Cyber Security & Compliance
Microsoft Is Ending SMS Authentication: What This Means for Your Business
Microsoft Entra ID is moving SMS and voice users to passkeys. Microsoft-provided telephony retires on 1 February 2027 for most users, and 1 July 2027 for Global Administrators and external users. Here is how to prepare.
Key dates at a glance
Checked against Microsoft Entra documentation on 15 October 2026. This timeline applies to the public cloud; other clouds and External ID tenants have separate schedules.
- ›Users enabled for SMS or voice are auto-enabled for passkeys and nudged to register after eligible MFA sign-ins.
- ›A temporary campaign opt-out does not postpone retirement.
- ›Organisations that need SMS or voice can begin configuring a supported provider through Microsoft Security Store.
- ›Applies to all users except Global Administrators and external users. Internal guest users are included.
- ›Microsoft-provided SMS and voice delivery retires for these groups.
For years, the standard approach to securing a Microsoft 365 login was a password plus a six-digit SMS code sent to a mobile number. It was better than a password alone — but not by as much as most people assumed. Microsoft is retiring its own SMS and voice delivery in Entra ID and encouraging passkeys: phishing-resistant credentials that avoid one-time codes.
The September rollout has already begun. Identify which retirement group each user belongs to and test replacement sign-in methods before their applicable deadline.
Why SMS authentication is being retired
SMS was never designed as a security mechanism. Text messages can be intercepted through SIM-swapping — where an attacker convinces a mobile operator to transfer your number to their SIM card — or through SS7 protocol vulnerabilities, which allow sophisticated attackers to reroute messages in transit. Both attack types have been used against business accounts in South Africa.
Beyond interception, SMS codes are still vulnerable to phishing. A convincing fake login page can capture both your password and the SMS code in real time, because the attacker can relay them to the real site before the code expires. Passkeys break this attack entirely.
SIM swapping
An attacker tricks your mobile operator into transferring your number, then receives all your SMS codes.
SS7 interception
Weaknesses in the global mobile signalling protocol allow SMS messages to be rerouted and read.
Real-time phishing
A fake login page captures your password and SMS code simultaneously, relaying both to the real site before the code expires.
Social engineering
Support staff at mobile operators can be manipulated. No technical attack required — just a convincing story.
What is a passkey?
A passkey uses cryptographic keys to prove your identity without typing a one-time code. Device-bound passkeys stay on their device; synced passkeys are held in a supported credential manager and can sync across your devices. Sign-in is tied to the legitimate service, which resists phishing.
Common phishing-resistant sign-in options include:
Windows Hello for Business
Uses a PIN or biometric (fingerprint, face) on your Windows device to authenticate — no password or code needed.
Microsoft Authenticator
The Authenticator app on iOS or Android can store and use a passkey, approving logins with a face scan or fingerprint.
FIDO2 hardware keys
Physical security keys (such as a YubiKey) that you plug in or tap. The strongest option, typically used for high-privilege admin accounts.
What changes — and when
The dates below concern Microsoft-provided SMS and voice delivery in Microsoft Entra ID, the identity platform behind Microsoft 365 sign-ins.
September rollout: who receives prompts?
Users enabled for SMS or voice in Authentication Methods Policy or legacy MFA settings are brought into the passkey registration campaign. Prompts follow eligible sign-in and MFA; snoozing is unlimited by default. Existing phishing-resistant methods remain usable.
February and July retirement: what happens at sign-in?
Without a configured telephony provider, affected users whose only available MFA is SMS or voice must register a passkey during sign-in. This registration prompt blocks progress until completed. The temporary campaign opt-out does not remove enforcement on the applicable retirement date.
Continuing SMS or voice through a supported provider
From 30 October 2026, organisations with a business, regulatory or technical need for telephony can configure a supported provider through Microsoft Security Store. Select a provider, test delivery and migrate affected users before their retirement date. Passkeys remain Microsoft's recommended path.
What your business needs to do
The transition is manageable with the right preparation. The key actions are:
- 1
Deploy Microsoft Authenticator to all staff
The Authenticator app is the simplest path to passkeys for most users. It is free, available on iOS and Android, and can store a passkey that works with Face ID or fingerprint. Register and test passkeys now, before each user's applicable retirement date. Installing the app alone does not register a passkey.
- 2
Enable Windows Hello for Business
For staff on Windows devices, Windows Hello for Business uses a PIN or biometric to authenticate without any phone at all. Use it where each person signs in with their own Windows account; assess portable passkeys or security keys for shared devices.
- 3
Review your Conditional Access policies
Passkey registration is subject to Conditional Access in Entra ID. Your policies may need adjusting to ensure registration flows work correctly — particularly for remote or off-site staff who cannot access your network during the transition.
- 4
Identify SMS-dependent users and their retirement group
Review authentication methods and sign-in activity in Entra ID. Separate the February and July groups, then confirm each user has a tested replacement method or has migrated to a supported telephony provider.
How StormDotCom is managing this for our clients
We proactively manage and monitor Microsoft 365 tenants for our clients, which means this transition is already in our scope. We use Augmentt — a dedicated Microsoft 365 management platform — to monitor authentication method usage across all our client tenants, identify users still relying on SMS, and track Secure Score changes as passkey adoption improves security posture.
For clients on our managed service, we coordinate registration, device checks and user readiness against the applicable retirement dates. If you are not on a managed plan and want to confirm your environment is ready, the best first step is a Microsoft 365 health review.
The bottom line
Passkeys are a genuine security improvement — not a cosmetic change. The weaknesses that SMS authentication carries are real, well-documented, and actively exploited. Microsoft's decision to retire it is overdue. The good news is that with the right preparation, the transition is straightforward and most users will find passkeys simpler to use than typing a six-digit code.
Key Takeaways
- 📅September rollout: users enabled for SMS or voice are nudged to register passkeys
- 🚫1 February 2027: most users, including internal guests; 1 July 2027: Global Administrators and external users
- ✓Passkeys cannot be intercepted, SIM-swapped, or stolen via phishing
- ✓Microsoft Authenticator and Windows Hello for Business are the main passkey paths
- ⚠Register and test replacement methods before the deadline for each user group
Official Microsoft Sources
Related Services
Other Categories
Is Your Microsoft 365 Ready for the Passkey Transition?
Book a Microsoft 365 health review to identify affected users, confirm their retirement dates and plan a tested passkey transition.
Book a Microsoft 365 Health Review