Skip to content
TECH Consult

Two-Factor Authentication for Business: Methods and Setup

What two-factor authentication is, which methods are safe, which company accounts to protect first and how to roll it out to your team without lockouts.

Published 9 min read

A stolen password is the easiest way into a company. It reaches the attacker through a fake login page, through a hacked website where the employee used the same password, or from a sticky note on a monitor. Two-factor authentication means the password alone is no longer enough. This article covers the methods available, which accounts to protect first, how to switch it on in Microsoft 365 and what to do when someone loses their phone.

What two-factor authentication means

With an ordinary sign-in, you prove who you are with one thing: the password. With two-factor authentication (2FA) you add a second proof of a different kind. Usually it’s something you carry, such as your phone or a security key.

You’ll see several names for the same idea:

  • two-step verification, the term Microsoft and many banks use;
  • two-factor authentication, or 2FA;
  • multi-factor authentication (MFA), the general term for two or more proofs.

For a small business, the differences don’t matter. What matters is that the second step is switched on for the important accounts, and that people know what to do when an approval request appears that they didn’t ask for.

2FA methods, from weakest to strongest

Not all methods protect you equally. Any of them is far better than a password alone, but it’s worth knowing the differences.

  1. SMS code. The most common and the easiest to use. It’s also the most exposed: an attacker can ask for the code over the phone (“I’m calling from the bank, read me the code you just got”), and in rare cases a phone number can be moved to another SIM card.
  2. Email code. Only helps if the email account is well protected itself. If the attacker is already in the mailbox, they get the code too.
  3. Authenticator app with codes (for example Microsoft Authenticator or other apps that generate 6-digit codes). The code changes every few tens of seconds and never travels over the phone network.
  4. App notification with number matching. A number appears on the computer screen and you type the same number on your phone. That way you can’t approve someone else’s request by mistake.
  5. Passkeys and physical security keys. The key is tied to the real website, so it doesn’t work on a fake page. They’re the best protection against phishing pages, but not every service accepts them yet.

A realistic starting point for a small business: an authenticator app for email and Microsoft 365, SMS only where the service offers nothing else, and security keys for administrator accounts if the service allows them.

Which accounts to protect first

You don’t have to do everything in one day. Start with the accounts that open other doors:

  1. Email. Almost every other account’s password can be reset from email. Whoever has the mailbox effectively has everything.
  2. Administrator accounts in Microsoft 365, the antivirus console, the router and the server.
  3. Online banking. Most banks already require a second step, but check secondary users too.
  4. The domain registrar and hosting account. Whoever takes it over can move the company’s website and email elsewhere.
  5. Cloud accounting or invoicing software.
  6. The password manager. It’s the safe holding every other key, so it needs the strongest protection. We cover choosing one in our article on password managers for teams.
  7. Company social media and advertising accounts, which often have a card attached.

Microsoft 365: security defaults

If your company uses Microsoft 365, you already have a basic set of rules called security defaults. Microsoft offers them at no extra cost to every organisation. When they’re on:

  • every user has to register for multi-factor authentication;
  • administrators have to use it at every sign-in;
  • ordinary users are prompted when Microsoft judges it necessary, based on location, device and action;
  • legacy sign-in methods that don’t support a second step are blocked.

Users register with the Microsoft Authenticator app. At sign-in they see a number on screen that they type into the app, which stops anyone approving a stranger’s request on reflex.

You switch them on in the Microsoft Entra admin centre: Entra ID → Overview → Properties → Manage security defaults, then choose Enabled. You’ll need an administrator account with the right permissions.

One practical warning. Blocking legacy sign-in can stop devices or programs that send email with a plain username and password. Most often that’s a multifunction printer that scans straight to email, or old invoicing software. List them beforehand and check how they connect, so you don’t discover the problem on Monday morning.

Email on your own domain, hosted separately

Not every business uses Microsoft 365. Many have addresses like name@yourcompany.ro on the website’s hosting, read in Outlook or on a phone over IMAP or POP3. Those older protocols only work with a username and password, so a second step doesn’t apply there.

In that case, the protection sits elsewhere:

  • a long, unique password for each mailbox, kept in the password manager;
  • a second step on the hosting control panel and on the domain registrar account, if the provider offers it;
  • encrypted connections (SSL/TLS) in the email program’s settings, not plain ones;
  • a check of forwarding rules in the mailbox, because attackers often add a rule that sends a copy of every message elsewhere.

If we host your email, through our web hosting with unlimited email, we can help you check the settings on each device.

How to roll out 2FA to your team without lockouts

Technically, switching it on takes a few minutes. The hard part is getting everyone ready.

  1. Announce it a few days ahead: what’s changing, why, and what each person needs, which is their phone with the app installed.
  2. Book half an hour where everyone registers together, with someone beside them who knows the steps.
  3. Register two methods for each person, for example the app and a phone number. If one fails, the other still works.
  4. Keep the recovery codes where the service offers them, somewhere safe, not on the same phone.
  5. Start with administrators, then move on to everyone else. If something goes wrong, you fix it on accounts you control.
  6. Say clearly what to do with an approval request they didn’t trigger: deny it and report it straight away.

For people without a work phone, or who don’t want the app on their personal phone, there are physical security keys or dedicated code generators. Sort that out in advance, not on the day you switch over.

Lost phone, new phone or someone leaving

The second step is tied to a device. When the device disappears, the account shouldn’t end up locked, or worse, left open.

  • Lost or stolen phone. The employee reports it straight away. An administrator removes the authentication methods registered on that phone, and the person registers again on the new device.
  • New phone. Before giving up the old phone, move the accounts to the app on the new one. Many apps have a transfer or backup feature.
  • An employee leaving. Besides disabling their account, remove their authentication methods from shared accounts, for example a bank account where they approved payments. The full list is in our article on employee onboarding and offboarding accounts.

There’s one more case many companies forget: the single administrator. If the only person with admin rights loses their phone on holiday, nobody can change anything. Microsoft recommends that organisations keep emergency access accounts, separate from individuals, for exactly this situation. For a small business, at least two people with administrator rights is a reasonable minimum.

Attacks that get around the second step

Two-factor authentication cuts the risk a lot, but attackers have adapted. Three situations your staff should know about:

  • Repeated approval requests. The attacker has the password and tries to sign in dozens of times, hoping a tired person taps “Approve”. The rule: never approve a request you didn’t start.
  • The code requested over the phone. Someone calls “from the bank” or “from IT” and asks for the SMS code. No legitimate service will ask you for that code over the phone.
  • Fake pages that pass the code on. Some phishing pages copy everything you type in real time, code included. Passkeys help here, and so does checking the address in the browser bar. The signs of a fake page are described in our guide on how to spot phishing emails.

If someone approved a request by mistake or gave out a code, change the account’s password straight away and ask the administrator to sign out all active sessions.

Frequently asked questions

Is two-factor authentication mandatory for businesses?

For a small business there usually isn’t a general rule requiring it on every account. Some services require it themselves, as banks do for payments. Even without an obligation, it’s one of the measures with the biggest effect for the effort involved.

Can staff use their personal phone for the authenticator app?

Yes, and many small businesses do. The authenticator app doesn’t give the company access to the rest of the phone. If an employee refuses, offer an alternative such as a physical security key, so you don’t end up with accounts that have no second step.

What about an account several people share?

Ideally, each person has their own account. Where that’s not possible, for example a social media account or a supplier portal, keep the codes in a password manager that can generate them for the whole team. That way the second step doesn’t depend on one colleague’s phone.

Will it slow our work down?

A little, at first. Most services remember a trusted device and stop asking for the second step at every sign-in. After the first week, prompts appear mainly when you sign in from a new device or a different place.

What if the authenticator app stops working?

Use the backup method you registered, such as SMS or a recovery code. If you have neither, the account administrator can reset your authentication methods after confirming your identity. That’s exactly why two methods from the start are worth it.

When to call a technician

You can switch it on yourself for a handful of accounts by following each service’s steps. Help is worth it when you have Microsoft 365 with several users, older devices that send email, few or unreliable administrator accounts, or when nobody knows exactly which accounts the company has.

Setting up accounts and sign-in methods is a typical example of an IT service that an outside provider can take on. If you’d like someone else to handle the switch-over, staff registration and follow-up, see what our IT maintenance for businesses includes. For an overview of the other measures, read our guide to small business IT security.

Tell us what is not working

Describe the problem in a few lines. We reply with what we think needs doing and what it would cost.

Request a quote