The SMS Code Countdown: How Enterprises Can Prepare for a Passkey-First Authentication Era

In this article
Enterprise passkeys: planning a secure transition
For years, a six-digit text message has been the familiar second step in signing in to work systems. That familiarity is now becoming a liability. Passkeys are moving from an optional passwordless alternative toward a mainstream enterprise authentication method, and major identity providers are changing their defaults.
Microsoft announced that passkeys would become the default sign-in experience in Microsoft Entra ID from September 1, 2026. Its published plan says retirement of Microsoft-provided SMS and voice delivery starts rolling out on February 1, 2027 for most users, with Global Administrators and external users following from July 1, 2027. These are rollout start dates for the relevant Entra public-cloud and Government Community Cloud services, not universal deadlines for every SMS-based login on the internet [1].
Why SMS codes are reaching their limits
SMS-based multifactor authentication improved security when the alternative was a password alone. It is still better than having no second factor in many situations, but it is vulnerable to phishing, SIM-swap fraud, number porting, message interception and social engineering.
A convincing fake sign-in page can persuade an employee to enter both a password and a one-time code, allowing an attacker to relay the code in real time. The issue is not that every text message is automatically unsafe; it is that the code is not cryptographically bound to the genuine website or application requesting it. A phishable factor can be captured and reused during the short period in which it remains valid.
What makes passkeys different
A passkey is a FIDO-based credential built around public-key cryptography. During registration, the authenticator creates a key pair: the private key stays with the user’s device or credential provider, while the public key is registered with the service. During sign-in, the service sends a challenge and the authenticator signs it.
The private key is not typed into a website, and the credential is associated with the legitimate relying party, which helps resist credential phishing. Users typically unlock the credential with a device PIN, fingerprint or face recognition. The biometric normally unlocks the local authenticator; it is not sent to the employer as an authentication secret [2].
Synced and device-bound credentials need different policies
Not all passkeys are stored in the same way. A synced passkey can be securely synchronized through a credential manager so that a user can access it on more than one approved device. A device-bound passkey remains tied to a particular device or security key.
The choice affects portability, administration and recovery. Synced credentials may suit employees who move between managed devices, while device-bound credentials may be preferred for privileged roles or tightly controlled environments. Organizations should assess attestation needs, supported platforms, device ownership, browser compatibility and their identity provider’s controls before selecting a policy. Avoid assuming that one setting will work equally well for every workforce segment [2].
Start with an authentication inventory, not a blanket switch
The first migration task is to identify who actually depends on SMS or voice. Review identity-provider policy assignments, sign-in logs, registration data, help-desk tickets, legacy applications and exception lists. Separate employees, contractors, administrators, external collaborators, frontline staff and users who do not have a compatible company-managed device.
Also distinguish human user accounts from service accounts, integration identities and automated workloads; passkeys are designed for people signing in, not as a universal replacement for machine-to-machine authentication. Map each group to its applications, device types, access risk and fallback method. This inventory turns a broad security announcement into a manageable programme with owners, milestones and measurable exceptions.
Design enrollment around real working conditions
A passkey rollout succeeds when registration is simple and happens at the right moment. Begin with a small pilot that includes different operating systems, browsers, device-management states and job roles. Test registration, everyday sign-in, cross-device use and what happens when someone replaces a phone or loses a security key.
Provide short instructions with screenshots and a support route that does not depend on the factor being replaced. For shift workers, shared workstations and employees who rarely use a personal smartphone, offer suitable hardware security keys or managed-device options. Communicate the change before enrollment prompts appear, explain why the process is changing and make the first sign-in experience predictable.
Recovery is the part attackers will test
Strong primary authentication can be undermined by weak account recovery. If an employee loses a phone, the recovery process should not simply send an SMS to the same number that the organization is trying to phase out. Define identity-proofing steps, help-desk verification, backup authenticators, device replacement procedures and temporary access arrangements.
Apply stronger checks to administrators and accounts with access to sensitive systems. Maintain carefully controlled emergency-access accounts, monitor their use and test them periodically. FIDO Alliance deployment guidance recommends piloting recovery as part of the passkey programme and designing backup mechanisms that do not reduce assurance below the credential being recovered [4]. Recovery should be documented before enforcement begins.
Measure adoption and remove fallback safely
Track more than the number of passkeys registered. Useful measures include the percentage of active users with a tested phishing-resistant method, failed enrollment rate, help-desk contacts, recovery completion time, sign-in failure by device type, privileged-account coverage and the age of outstanding exceptions. Keep SMS available only where an approved business requirement remains and the identity provider supports a suitable route.
Do not disable the fallback before users have successfully registered and tested the replacement. Conversely, do not leave old methods enabled indefinitely after migration: unused methods create confusion and can preserve an attack path. A staged policy change, followed by log review and exception closure, is safer than a single organization-wide switch.
Illustrative scenario: a distributed engineering company
Consider a hypothetical engineering company with 2,400 employees across offices, construction sites and remote locations. Its identity team discovers that 31% of active users still rely on SMS for at least one important application. Rather than forcing a change on everyone at once, it groups users by role and device access.
Office staff enroll synced or device-bound passkeys on managed laptops and phones; site supervisors receive tested security keys; administrators get a stricter device-bound option and separate recovery procedures. A six-week pilot reveals that contractors need a different onboarding guide and that a legacy timekeeping application does not yet support the desired sign-in flow. The company addresses those gaps before changing the conditional-access policy. The scenario is illustrative, but it shows why inventory, recovery and application compatibility matter as much as the credential itself.
A practical 90-day migration sequence
In the first 30 days, inventory authentication methods, confirm provider timelines, select credential types and define recovery. In days 31–60, pilot with a representative group, measure failures, train service-desk staff and remediate unsupported applications. In days 61–90, expand by user segment, communicate enforcement dates, review exception owners and report adoption to security leadership.
The precise schedule will vary by organization size and provider dependencies, but the sequence is portable: discover, design, pilot, expand and verify. Treat passkeys as an identity lifecycle change rather than a one-time technology toggle. The aim is not simply to remove an SMS prompt; it is to make phishing-resistant access dependable for the people and systems that keep the business running.
Frequently Asked Questions
Are SMS authentication codes being discontinued everywhere?
No. The February 2027 and July 2027 dates described here concern Microsoft-provided SMS and voice delivery in Microsoft Entra ID, with different user groups following different dates. Other identity providers and services set their own policies.
Are passkeys the same as passwords stored in a password manager?
No. A passkey uses a public/private key pair and signs a challenge for the legitimate service. It does not send a reusable password to the website. Some password managers can store and sync passkeys, but the underlying authentication model is different.
Can an enterprise use both synced and device-bound passkeys?
Yes, if its identity provider and security policy support both. The choice should reflect user roles, device ownership, assurance requirements, portability and recovery needs.
What happens if an employee loses the device that holds a passkey?
The organization should use a pre-designed recovery process, such as a backup authenticator, controlled identity proofing and secure re-enrollment. Recovery should not depend on a weaker factor than the one being replaced.
Do passkeys eliminate every account-takeover risk?
No. They substantially reduce phishing of the credential, but organizations must still secure devices, identity recovery, session tokens, administrator workflows, help desks and third-party integrations.
How should organizations handle applications that still require SMS or passwords?
Inventory them, assess their business importance, isolate or modernize them where possible, and document time-limited exceptions with owners and compensating controls. Do not assume the entire application estate will modernize at once.
References and further reading
3. Microsoft Learn – How to enable passkeys (FIDO2) in Microsoft Entra ID
4. FIDO Alliance – Displace Password + OTP Authentication with Passkeys
