A step-by-step MFA implementation guide for businesses with 10 or more staff: which accounts to protect first, which methods to choose, how to roll it out in Microsoft 365, and what to do about lost phones and shared accounts.
TL;DR MFA is the single most effective control for stopping stolen passwords, but a rushed rollout creates lockouts and workarounds. Do it in order: inventory, admins first, pick methods, pilot, communicate, roll out, then close the gaps (legacy sign-ins, shared accounts, systems outside Microsoft 365). Plan for lost phones before the first one goes missing.
MFA implementation is the process of requiring a second proof of identity, beyond a password, for every account in your business, and making that stick without blocking people from their work. It’s one of the first controls in any managed cybersecurity program, and a common question on cyber insurance applications.
I’m Jeffrey Bowles, Partner and Director of IT Services at ACT360. This is the order we’d follow for an Ontario business with 10 to 100 staff, most of them on Microsoft 365. It’s a how-to, not a sales pitch: you can run most of it yourself if you have someone with admin access and a free afternoon.
What Is MFA and Why Does It Matter So Much?
Multi-factor authentication (MFA) requires two or more kinds of proof to sign in: something you know, like a password, plus something you have, like a phone or security key, or something you are, like a fingerprint.
The Canadian Centre for Cyber Security describes those three factor types and notes that the password alone “can be easily compromised.” That’s the whole point. Passwords get reused, guessed and phished. A second factor means a stolen password on its own isn’t enough.
Microsoft puts it bluntly: based on its own data, more than 99.9% of common identity-related attacks are stopped by using MFA and blocking legacy authentication. Few other single controls come close.
It also isn’t optional anymore for the people who run your systems. Microsoft has required MFA to sign in to the Microsoft 365 admin center since February 2025, and to the Azure portal, Microsoft Entra admin center and Intune admin center since late 2024.
How Do You Implement MFA in a Small Business, Step by Step?
Roll out MFA in a fixed order: inventory accounts, secure admins and emergency accounts, choose methods, pilot with a small group, communicate, enforce for everyone, then block legacy sign-ins and extend MFA to systems outside Microsoft 365.
- List every account and system staff sign in to, including banking, payroll and remote access.
- Turn on MFA for every admin account first, and create two emergency access accounts.
- Choose your methods: authenticator app for staff, passkeys or security keys for admins.
- Pilot with four or five people from different departments for one week.
- Tell staff the date, what they’ll see, and who to call if they get stuck.
- Enforce MFA for all users, ideally department by department over two weeks.
- Block legacy authentication and old protocols that can skip the MFA prompt.
- Extend MFA to VPN, firewall, payroll, banking and line-of-business apps.
The sections below go through the steps that need the most care.
Which Accounts Should Get MFA First?
Start with the accounts that would do the most damage in the wrong hands: Microsoft 365 Global Administrators, then anyone who can move money, then remote access, then everyone else. Admin accounts come first because one stolen admin login opens the whole tenant.
| Priority | Accounts | Why |
|---|---|---|
| 1 | Global Administrators and other admin roles | Full control of email, files and users |
| 2 | Finance, payroll and executive mailboxes | Used for payment redirection and impersonation |
| 3 | VPN, remote desktop and firewall logins | A direct path onto your network |
| 4 | Banking, payroll and accounting portals | Money moves here, often outside Microsoft 365 |
| 5 | All remaining staff accounts | Any mailbox can be used to phish the rest of the company |
| 6 | Service and shared accounts | Easy to forget, tempting to exempt |
Before you enforce anything, set up emergency access accounts. Microsoft recommends at least two cloud-only emergency access accounts, protected with a passkey or certificate-based authentication that’s different from your everyday admin method, and tested at least every 90 days. They’re your way back in if a policy locks everyone out.
If you’re sharing admin duties with an outside provider, our co-managed IT checklist covers how to keep admin accounts in the company’s name.
Which MFA Methods Should You Choose?
Use an authenticator app with number matching as the minimum for staff, and phishing-resistant methods such as passkeys, FIDO2 security keys or Windows Hello for Business for admins and finance. Avoid relying on text messages where you have a choice.
| Method | Phishing-resistant? | Best for | Trade-off |
|---|---|---|---|
| Text message (SMS) or voice call | No | Fallback only | Codes can be phished or intercepted |
| Authenticator app push with number matching | No, but much better than SMS | Most staff | Needs a smartphone |
| Passkey in Microsoft Authenticator | Yes | Staff with company or personal phones | Newer, needs some setup help |
| FIDO2 security key | Yes | Admins, finance, staff without phones | Costs money per key, can be lost |
| Windows Hello for Business | Yes | Staff on company-managed Windows PCs | Tied to one device |
Microsoft lists Windows Hello for Business, passkeys (FIDO2), FIDO2 security keys, passkeys in Microsoft Authenticator and certificate-based authentication as phishing-resistant methods. Number matching is now on for all Authenticator push notifications, so users type a number shown on screen instead of tapping Approve.
Why it matters: in October 2025 the Cyber Centre published guidance on adversary-in-the-middle attacks, where a fake sign-in page relays your password and MFA code to the real site and steals the signed-in session. It calls phishing-resistant MFA “the new industry standard” and recommends removing weaker backup methods on accounts that use it. You don’t have to get every user there on day one. Admins and finance first is a practical start.
Should You Use Security Defaults or Conditional Access?
Security defaults are free, on by default in new Microsoft 365 tenants, and turn on MFA plus legacy-authentication blocking in one switch. Conditional Access gives finer control but needs Microsoft Entra ID P1 or P2 licensing.
| Feature | Security defaults | Conditional Access |
|---|---|---|
| Licence needed | None | At least Microsoft Entra ID P1 |
| Setup | One switch | Policies you design and test |
| Blocks legacy authentication | Yes | Yes, if you build the policy |
| Exceptions for specific users or locations | No | Yes |
| Best for | Businesses with no Entra ID P1 licences | Businesses that need exceptions, device rules or location rules |
You can’t run both. Microsoft says organizations that move to Conditional Access must disable security defaults. Check your licences before deciding, and if you switch, build and test the Conditional Access policies first so there’s no gap. And don’t skip blocking legacy authentication. Older email protocols can sign in with a password alone, which makes MFA everywhere else pointless.
How Do You Get Staff to Accept MFA?
Explain the why in one sentence, give a firm date, show exactly what the prompt will look like, and make help easy to reach on rollout day. Notice and a clear guide prevent most of the friction.

- Send a short note a week ahead. What’s changing, the date, and a one-page guide with screenshots.
- Run a 10-minute setup huddle per department rather than one big all-hands.
- Have someone available the morning enforcement starts, when the questions come in.
- Answer the personal-phone question honestly (more on that below).
- Tell people what an unexpected prompt means: someone has their password. Deny it, then call IT.
That last habit ties MFA to phishing awareness training. The Cyber Centre also recommends limiting the number of MFA requests per user, which blunts attackers who spam prompts hoping someone taps Approve to make them stop.
What About Lost Phones, Shared Accounts and Staff Without Smartphones?
Decide these before rollout. Lost phones need a verified reset process, shared accounts should become named accounts, and staff without a smartphone, or who won’t use a personal one, can use a FIDO2 security key instead.
Lost or replaced phones. Write down who can reset someone’s MFA, how they confirm it’s really that person (a call to a known number or in person, never just an email), and how fast. A reset process that anyone can trigger by emailing the help desk is a gap attackers know about.
Personal phones. Some staff don’t want work apps on their own phone, and that’s a fair concern. A security key costs far less than a company phone and works without any app.
Shared logins. A shared front-desk or shop-floor account with MFA tied to one person’s phone breaks the moment that person is away. Convert shared logins to named accounts where possible. Where a shared device is truly needed, talk to your IT provider about the right setup rather than exempting it.
Offboarding. When someone leaves, remove their MFA methods along with their account access. Old registered devices are easy to forget.
What Doesn’t MFA Protect Against?
MFA protects your own accounts from stolen passwords. It doesn’t stop someone from emailing your staff or partners from a lookalike domain, and it doesn’t replace backups, patching or payment verification.
A real case from our work shows the limit. A business partner of one of our Ontario clients received an email asking to change banking details on a pending payment worth over six figures. We reviewed the client’s Microsoft 365 sign-ins and found no breach: the email came from a newly registered domain one letter off from the client’s. MFA on the client’s accounts was never going to stop that, because the attacker never touched them. What stopped it was the partner pausing to confirm.
So treat MFA as one layer. Our post on why Microsoft 365 security alone isn’t enough covers the others, and the Cyber Centre’s baseline controls for small and medium organizations list strong authentication alongside patching, backups, training and incident response.
MFA also comes up on cyber insurance forms. Our guide to cyber insurance requirements in Ontario explains what underwriters ask about it.
Where ACT360 Fits
MFA coverage is one of the first things we check in an assessment, because it decides how exposed every other system is. As part of managed IT or our cybersecurity services, we can plan and run the rollout in the order above. Our identity protection for Microsoft 365 then watches for what MFA alone won’t flag, such as sign-ins from unusual locations and odd access patterns.
Final Thought
Check one thing today: can every Global Administrator in your Microsoft 365 tenant sign in with a password alone? If yes, fix that before anything else in this guide.
If you’d rather have someone map the gaps for you, book a free IT Readiness Assessment. We’ll show you where MFA is missing, which accounts matter most, and a rollout order your staff can live with. You can also call 705-739-2281 or email [email protected].