Multi-Factor Authentication for Business: Which Type Should You Use?
A stolen password used to be a nuisance. Today it is often the first step in a mailbox takeover, a fraudulent wire request, or a ransomware incident. Multi-factor authentication (MFA) is the single most practical control for blunting that risk, yet many businesses turn it on in a way that leaves easy gaps. The question is no longer whether to use MFA. It is which kind to use, and where.
What MFA is and why passwords alone fall short
MFA asks a person to prove who they are using at least two different kinds of evidence: something they know (a password), something they have (a phone or a security key), or something they are (a fingerprint or face scan). A stolen password by itself is no longer enough, because the attacker does not have the second item.
Passwords fail for ordinary reasons. People reuse them across sites, so a breach at an unrelated service can expose a work login. Phishing emails trick people into typing a password into a fake sign-in page. Attackers also test lists of leaked passwords against business email systems automatically. MFA does not stop every one of these attacks, but it removes the easiest path.
If your team has had a suspicious email scare, our guide on how to spot a phishing scam covers the human side of the same problem.
The common types of MFA, compared
Text message (SMS) codes
A code is sent to a phone number and typed into the sign-in page. This is easy to set up and familiar to everyone. The weakness is that text messages can be redirected if an attacker convinces a mobile carrier to move a phone number to a new SIM card, a technique called SIM swapping. Codes can also be captured by a fake sign-in page and used immediately. SMS is acceptable as a fallback, but it should not be the primary method for important accounts.
Authenticator app codes
An app on the phone generates a six-digit code that changes every 30 seconds or so. Because the code is created on the device and not sent over the phone network, it is not exposed to SIM swapping. A fake sign-in page can still trick a person into typing the code, so this method is good but not phishing-resistant.
Authenticator app push approvals with number matching
Instead of typing a code, the person approves a sign-in request on their phone. Older push approvals had a flaw: an attacker with a stolen password could send repeated requests until a tired user tapped Approve. Number matching closes much of that gap by requiring the person to enter a number shown on the sign-in screen into the app, which proves they are looking at the real sign-in attempt. Microsoft states that number matching is enabled by default for all Microsoft Authenticator users, and any other push-based tool your team uses should have an equivalent setting turned on.
Hardware security keys
A small physical key, usually USB or NFC, is plugged in or tapped to sign in. These use a standard called FIDO2 and are resistant to phishing because the key will only respond to the genuine website. They are the strongest common option. The tradeoffs are cost, the need to keep a spare key, and some user training.
Passkeys
Passkeys use the same underlying technology as security keys, but the credential is stored on a phone, computer or password manager and unlocked with a fingerprint, face scan or device PIN. They are phishing-resistant and easy to use, and support is growing across business platforms. Support varies by application, so confirm that each platform your team uses accepts them.
Quick comparison
| Method | Protection level | Ease of use | Best used for |
|---|---|---|---|
| SMS code | Basic | Very easy | Backup method only, or where nothing else is offered |
| Authenticator app code | Good | Easy | General staff accounts |
| Authenticator push with number matching | Good | Very easy | General staff accounts |
| Hardware security key | Strongest | Moderate | Administrators, executives, finance roles |
| Passkey | Strongest | Easy | Any account where the platform supports it |
Which accounts to protect first
If a full rollout feels like too much at once, start with the accounts that cause the most damage when they are taken over:
- Email and Microsoft 365 or Google Workspace sign-ins. A hijacked mailbox is the starting point for most fraud against small businesses.
- Administrator accounts. Anyone who can change settings, create users or reach servers should use the strongest method available.
- Remote access. VPN and remote desktop sign-ins are a common way in for attackers.
- Banking, payroll and accounting platforms. These involve money movement directly.
- Line-of-business applications that hold client records, case files, patient information or financial data.
- Password managers, because they hold the keys to everything else.
How attackers get around weak MFA
MFA is not a guarantee, and it helps to know the common ways it is defeated so you can choose methods that resist them.
- Prompt fatigue. The attacker has the password and triggers repeated approval requests, hoping the user taps Approve to make them stop. Number matching and clear guidance to never approve a request you did not start reduce this risk.
- Real-time phishing. A convincing fake sign-in page collects the password and the one-time code at the same moment and passes them to the real site. Phishing-resistant methods such as security keys and passkeys defeat this approach.
- SIM swapping. The attacker takes over a phone number and receives the text codes. Avoiding SMS as the main method removes this exposure.
- Stolen sign-in sessions. If malware on a device steals an already-approved session, MFA is not asked again. Protecting the device itself with endpoint security matters as much as protecting the account.
MFA in Microsoft 365
Many Ventura County and Los Angeles businesses run on Microsoft 365, so it is worth knowing the options there. Microsoft provides a free baseline setting called security defaults. According to Microsoft, it requires all users to register for MFA, requires administrators to complete MFA, prompts other users when necessary, and blocks legacy authentication protocols. Plans that include Conditional Access allow finer control, such as requiring MFA only when someone signs in from an unfamiliar location or device, blocking sign-ins from countries where you do not operate, and requiring a compliant company device for sensitive applications. Which of these you can use depends on your license level, which we cover in our comparison of Microsoft 365 Business Standard and Business Premium.
Two details are easy to overlook. First, registering an MFA method does not by itself require MFA at sign-in; something, such as security defaults or a Conditional Access policy, has to require it. Second, older email protocols that do not support MFA, often called legacy authentication, can let an attacker skip the prompt entirely if they are left enabled. Security defaults block them, and if you use Conditional Access instead, confirm that legacy authentication is blocked as part of your MFA rollout.
How to roll MFA out without frustrating your team
- Make a list of accounts and applications. Include shared mailboxes, scanners that send email, and any systems that sign in automatically.
- Start with administrators and finance staff. They are the highest-risk users and usually the easiest group to train.
- Choose one primary method for staff and one backup. An authenticator app as the primary method and a second registered method as the backup keeps support questions manageable.
- Plan for lost and replaced phones. Decide in advance how someone proves their identity when their phone is gone, and who is allowed to reset their MFA. This is a common target for social engineering, so the reset process should require verification, not just a request by email.
- Handle the exceptions on purpose. Shared accounts, service accounts and older software may not work with MFA. Each exception should have an owner and a plan, not a quiet permanent bypass.
- Tell people what is coming and why. A short message explaining the change, the date, and who to call for help prevents most of the friction.
- Review after launch. Check who has not enrolled and watch for repeated failed prompts, which can signal an attack in progress.
Common mistakes
- Turning MFA on for staff but not for administrator accounts or for the owner.
- Leaving legacy authentication enabled, which allows sign-ins that skip MFA.
- Relying on text messages for every account indefinitely.
- Allowing unlimited, unreviewed exceptions.
- Letting MFA resets happen through a simple email request with no identity check.
- Treating MFA as a replacement for other protections. It works best alongside endpoint security, email protection and monitoring, and with authenticated email, as described in our guide to DMARC.
Frequently asked questions about MFA
The bottom line
Turning on MFA is a clear improvement, and choosing the right type is what makes it hold up. Use authenticator apps with number matching as the everyday standard, move administrators and high-risk roles to security keys or passkeys, and treat text messages as a backup. Pair MFA with a plan for resets and exceptions so that it keeps working as people join, leave and replace devices.
If you are not sure how your own accounts are set up today, talk to Urban IT about a review of your sign-in security. We support businesses across Ventura County and greater Los Angeles from our office in Westlake Village.
Sources & Further Reading
- Security defaults in Microsoft Entra ID, Microsoft Learn
- Protecting authentication methods in Microsoft Entra ID, Microsoft Learn
- Cybersecurity and Infrastructure Security Agency (CISA), U.S. Department of Homeland Security
- National Institute of Standards and Technology (NIST), U.S. Department of Commerce