
Multi-Factor Authentication: Why Every GTA Business Needs It
Which MFA method to use, how to switch it on in Microsoft 365 and Google Workspace, and the awkward cases (shared mailboxes, emergency admin accounts, staff without company phones) that trip most small offices up.
Reviewed by the ITRS security team · Last updated
What MFA stops, and what it does not
Microsoft states that MFA combined with blocking legacy sign-in stops more than 99.9% of common identity-related attacks. That is Microsoft's figure for password spraying and credential stuffing, the attacks that hit small businesses most.
It does not stop everything. Attackers now use fake login pages that relay your code in real time, then steal the session token. They also send repeated push prompts until someone taps Approve. The method you choose decides how well you resist those two tricks.
Methods compared
| Method | Resists password theft | Resists push fatigue | Resists fake login pages | Notes |
|---|---|---|---|---|
SMS or voice code | Yes | n/a | No | SIM-swap risk. Use only as a fallback. |
Authenticator app code (TOTP) | Yes | n/a | No | Works offline. Codes can be phished. |
Push with number matching | Yes | Yes | No | Default in Microsoft Authenticator; users type the number shown on screen. |
Passkey (device-bound or synced) | Yes | Yes | Yes | Bound to the real site's domain, so a look-alike page gets nothing. |
FIDO2 security key | Yes | Yes | Yes | Best for admins and staff without a company phone. |
Microsoft 365: the two ways to turn it on
Security defaults is free and is a single switch in the Microsoft Entra admin centre (Entra ID > Overview > Properties > Manage security defaults). It requires every user to register MFA, prompts when needed and blocks legacy authentication. Users get 14 days to register. Microsoft's security defaults page describes exactly what it enforces.
Conditional Access needs Microsoft Entra ID P1, which is included in Microsoft 365 Business Premium. It lets you require stronger methods for admins, block sign-ins from countries you never work in, and exempt nothing by accident. You must turn security defaults off to use it. Our guide to security defaults vs Conditional Access covers the choice in detail.
Either way, check that number matching is in effect for push notifications (users cannot opt out of it), and consider passkeys for anyone with admin rights.
Google Workspace
In the Admin console go to Security > Authentication > 2-step verification, allow users to turn it on, give them a set enrolment period, then switch enforcement on. Google's 2-Step Verification guide explains the enrolment window and the option to allow only security keys for high-risk users. Our step-by-step is at Google Workspace 2-step verification.
This matters in the GTA. In our 5 August 2026 scan of 479 mail-enabled GTA business domains, Google Workspace domains enforced DMARC at 10.8% against 27.2% for Microsoft 365, which suggests Workspace tenants are more often left at their defaults.
The awkward cases
MFA rollout and enforcement is part of our managed security services; see also how our managed IT plans are structured.
Shared mailboxes
In Microsoft 365, a shared mailbox should have sign-in blocked; people reach it through their own MFA-protected accounts. If staff log in to a general 'info' address with a shared password, convert it to a shared mailbox first.
Emergency (break-glass) accounts
Keep two cloud-only admin accounts for the day MFA or Conditional Access locks everyone out. Microsoft now recommends passkeys (FIDO2) for emergency access accounts. Store the keys in two separate secure places and alert on any sign-in.
Staff without a company phone
Some employees will not put a work app on a personal phone. Give them a FIDO2 security key. It costs less than the argument and is stronger than SMS.
Scanners, copiers and old apps
Devices that send mail with a username and password often rely on legacy authentication, which MFA cannot protect. Move them to a connector or app password alternative before you block legacy authentication.
Executives and finance staff
These are the accounts used to redirect payments. Require phishing-resistant methods for them first, even if everyone else stays on push with number matching for now.
A rollout plan for a 10 to 50 person office
- Week 0: list every account, including shared and service accounts, and decide method per group.
- Week 1: create two emergency access accounts and test them.
- Week 1 to 2: announce, register users in small groups, sit with anyone who struggles.
- Week 3: enforce, then block legacy authentication.
- Week 4: review sign-in logs for failures and anything still using old protocols.
- Ongoing: check Microsoft Secure Score monthly and reset MFA only after verifying the person by a callback to a known number.
If an account is already compromised
MFA added after a compromise does not remove an attacker who already has a session or an inbox rule. Follow what to do if a Microsoft 365 account is hacked, and call our 24/7 incident line at (289) 582-9930 if money or client data may be involved.
Related reading.
- GuidePhishing-resistant MFA and passkeys in Microsoft 365Text codes and app approvals stop password guessing, but they don't stop a convincing fake sign-in page that relays everything in real time.
- GuideSecurity defaults vs Conditional Access in Microsoft 365Both switch on multifactor authentication and block old sign-in protocols.
- GuideEnforcing 2-Step Verification and security keys in Google WorkspaceTurning on 2-Step Verification in Google Workspace takes a few clicks.
- ArticleMicrosoft 365 Security Best Practices for 2026Eight settings that close the gaps we find most often in small-business Microsoft 365 tenants, each with where to find it and which licence it needs.
Want this handled for your business?
Tell us your users, devices and sites. We are staffed 24/7 and reply with next steps. Quotes are built from your environment, not a price list. Active incident? Call (289) 582-9930, 24/7.
