Published:
Updated:

Passkeys in Microsoft 365: the SME rollout guide
Small businesses do not need to turn passkeys into a grand transformation project.
What they need is a sensible order of operations.
The right question is not whether passkeys are the future. The right question is where stronger, phishing-resistant sign-in makes the biggest difference first.
For most SMEs, that starts with administrators and anyone with sensitive access.
MFA vs phishing-resistant MFA in plain English
Standard MFA adds a second step to sign-in. That is useful, and in many environments it is still a meaningful improvement over passwords alone.
Phishing-resistant MFA raises the bar further. It is designed to make it much harder for attackers to trick a user into approving the wrong sign-in or handing over something reusable.
That distinction matters. Not all MFA methods offer the same level of resistance to modern phishing.
What passkeys are, and what they are not
A passkey is a modern sign-in method that uses the device and a local gesture such as biometrics or a PIN, rather than relying on a traditional password-and-code pattern.
That does not mean every other MFA method becomes instantly obsolete. It means SMEs now have a practical route to stronger sign-in for the users who matter most.
For broader context on how this fits into your wider Cyber Security posture, the Cyber Security hub covers how identity controls sit alongside device management, backup and monitoring as part of a defined security baseline.
A practical rollout order for SMEs
A staged rollout is usually the right move. The goal is to protect the highest-value accounts first, then expand as your support processes catch up.
Stage 1: Protect admins first
If you only improve one user group first, make it privileged accounts.
Administrators have access to every setting, every mailbox, and every service in your Microsoft 365 tenant. Compromised admin credentials are the single most damaging account type an attacker can seize. Getting passkeys onto admin accounts before anything else eliminates the weakest link in your identity chain.
Stage 2: Cover sensitive roles
Think finance, leadership, HR, or anyone with access that would create significant operational impact if compromised.
These users are prime targets for spear-phishing and business email compromise attacks. A passkey on a finance director's account, for example, means an attacker cannot trick them into approving a fraudulent sign-in from a known email address.
Stage 3: Expand to standard users where it fits
Once recovery, support and device readiness are clear, broader rollout becomes easier and less disruptive.
By this stage your staff will have seen passkeys working in their organisation, IT support will have documented the onboarding flow, and you will know which devices or scenarios need special handling. The final push tends to be the smoothest.
For a more detailed implementation checklist — covering app inventories, password manager transitions, cross-OS considerations and legacy application scenarios — see our passkeys implementation guide for small businesses.
Where Microsoft 365 makes this easier
For Microsoft 365-based SMEs, the useful part is not just that passkeys are available. It is that administrators can shape policy around them.
That means looking at things like:
which authentication methods are allowed
which user groups move first
whether stronger authentication is required for sensitive resources
how recovery and fallback are handled
In other words, better sign-in is not just a user setting. It is an operating policy.
What to consider before rolling out passkeys
A small business should make a few decisions up front:
Which users go first?
Are admin accounts already separated and identifiable?
Are business devices managed well enough to support a smoother rollout?
What is the fallback plan if a user changes device or loses access?
Will any shared-device scenarios make adoption harder?
Those questions matter more than hype.
SMS MFA retirement — what has changed
Microsoft has now fully retired SMS and voice-based MFA across Microsoft 365. Organisations that still had SMS as a fallback authentication method saw it removed on the timeline Microsoft published — most notably with the SMS/voice retirement date passing in early 2026, with full enforcement completing in February 2027.
The practical impact is straightforward. Any staff member whose only remaining identity method was a text message or phone call can now be blocked from signing in with no workaround. Microsoft prompts users to set up a passkey as the default sign-in method, and there is no opt-out from the automatic activation that follows.
Understanding how many of your users were on SMS MFA is not optional anymore — it is a tenant-level policy review that needs to happen sooner rather than later.
Cyber Essentials readiness
Passkeys represent a significantly stronger identity control than SMS-based MFA, and they align closely with the phishing-resistance expectations that auditors reference under Cyber Essentials and Cyber Essentials Plus.
Insurance providers and business suppliers are increasingly demanding documented, phishing-resistant identity governance as a baseline condition. Positioning your organisation for these expectations regardless of when the next audit lands is what forward-looking MSP support delivers.
Day-to-day staff impact
When the transition happens, anyone without a passkey set up may be locked out without warning. Blocked sign-ins mean missed deadlines, confused clients, and work that simply does not get done because someone cannot reach their inbox.
Staff already using modern phones or computers with biometric authentication (Face ID, Touch ID, Windows Hello) may actually find their sign-in experience improves. No more waiting for text messages to arrive or calling in codes from memory.
The key to a smooth transition is clear internal communication. Let staff know what is happening, why, and what they need to do during their next login. A brief internal note goes further than you might expect.
Mistakes to avoid
The most common mistakes are predictable:
changing everyone at once
not protecting admins first
treating rollout as a purely technical switch
failing to define recovery and support ownership
A better approach is phased, deliberate and role-based.
Final thought
For SMEs, passkeys are best understood as part of a stronger sign-in policy, not a one-click replacement project.
If your environment still has weak admin protection, inconsistent MFA, or unclear sign-in standards, the right next step is not "enable everything overnight". It is to strengthen identity in the right order and make that standard repeatable.
If you want to understand how many of your users are on SMS MFA right now, what that means for your team's ability to sign in, and how passkeys fit into your broader IT security baseline, start with a quick review.
FAQs
What is the difference between passkeys and MFA?
Multi-factor authentication (MFA) typically uses a password plus a verification code sent to your phone. Passkeys replace the password entirely with a cryptographic key stored on your device — they are phishing-resistant because they cannot be stolen by fake login pages.
Should SMEs implement passkeys in Microsoft 365?
Yes — passkeys are the most phishing-resistant authentication method available and are supported natively in Microsoft 365. They eliminate the single biggest attack vector (password theft) while improving the user experience compared to traditional MFA.
How do you enable passkeys for staff in Microsoft 365?
Enable passkeys through your Microsoft 365 admin centre by configuring the authentication methods policy to allow Windows Hello for Business or FIDO2 security keys. Train staff to set up their passkey during their next login, and require MFA for any users who have not yet enrolled.

Cyber Security
Endpoint protection vs antivirus: do small businesses need XDR?

Backup & Disaster Recovery
Business continuity and backup for UK SMEs: a practical checklist
Cyber Security
Three Automatic-Fail Areas in Cyber Essentials

Modern Workplace
Microsoft 365 Support for Sussex SMEs: Who Owns Your Tenant

Cyber Security