Who it is for
This is for a small office or shop (roughly 3 to 50 people) that runs email and files on Microsoft 365 or Google Workspace and still signs in with just a password. A stolen or reused password is one of the most common ways small businesses get their email taken over: the attacker reads your threads, then sends “please pay this new account” messages to your customers as you. Two-step sign-in (also called multifactor authentication, or MFA) adds a second check, usually a prompt on your phone, so a password alone is not enough.
The technology is the easy part. The part that goes wrong is the rollout: the owner’s phone dies, a new hire cannot get past the setup screen, or an admin locks themselves out on a Friday afternoon. This guide is about turning it on and having a plan for those moments. Plan on about two hours of setup and a short team huddle, spread over a week.
What you need
- Admin access to Microsoft 365 or Google Workspace, or the person who manages it. Ideally two people have admin access, so one can rescue the other.
- A current list of everyone who signs in, including part-timers, seasonal staff, and shared mailboxes.
- Each person’s phone, or a plan for people who do not want work apps on a personal phone (see the cautions).
- A safe place to store recovery info, such as a password manager shared with the owner, or a sealed envelope in a locked drawer.
The idea in one sentence
Turn on two-step sign-in in stages (admins first, then everyone), give each person a second way in, and keep one admin account with a tested recovery path.
Steps
1. Make a list and clean it up first
Before you require anything, list every account and who uses it. Remove accounts for people who left. Find shared logins (for example “info@” or “front desk”) that several people sign in to with one password. Those need a plan, because a code sent to one person’s phone does not work for five people. The usual fix is to turn a shared login into a shared mailbox that people open with their own accounts, which keeps the audit trail and lets everyone use their own second step.
2. Make sure two people can rescue the admin account
Pick two admins (the owner plus one trusted person, or your IT help). Each should have their own named admin sign-in, not one shared admin login. If one admin loses a phone, the other can reset their sign-in methods. Write down who they are.
3. Turn it on for admins first
Admin accounts can see and change everything, so they go first.
- Microsoft 365: Microsoft’s security defaults turn on a baseline set of protections, including requiring all users to register for MFA and requiring MFA for administrators (security defaults). Many new Microsoft 365 tenants already have this on. If yours does not and you do not use Conditional Access policies, security defaults are a reasonable small-business choice. If you already use Conditional Access, do not switch security defaults on top of it; use a policy instead and check the Microsoft 365 MFA setup guide.
- Google Workspace: In the Admin console, 2-Step Verification is under the Security area (Protect your business with 2-Step Verification). Google’s guide walks through turning it on for an organizational unit, which lets you start with a small group such as admins (deploy 2-Step Verification).
Menu names in both admin consoles change often. If a label moved, search the admin console for “multifactor,” “security defaults,” or “2-Step Verification” instead of following an old screenshot.
Have each admin finish setup, then sign out and back in to confirm it works before moving on.
4. Give everyone a second way in
Ask each person to set up two methods, not one:
- Main method: an authenticator app on their phone (Microsoft Authenticator or Google Authenticator or similar), or a prompt in the Google app. App-based prompts are much safer than text messages, which can be intercepted or redirected, though a text is still far better than nothing.
- Backup method: a second device, a hardware security key kept in the office, or backup codes.
For Google accounts, backup codes are one-time codes you print or save for when the phone is not available (sign in with backup codes). Store them somewhere that is not the same phone.
5. Roll out in waves
Do not flip it on for everyone at 4:45 on a Friday.
- Day 1: admins (done in step 3).
- Day 2 or 3: a pilot group of two or three willing people. Note what confused them.
- Following days: everyone else, ideally at the start of a workday, with someone available to help.
In Google Workspace you can use organizational units to stage this. In Microsoft 365, the registration page and any Conditional Access policy groups play that role. In both, you can give people a short window to register before it becomes required, if the admin tools offer it. Check the current docs for how your plan handles that.
6. Hold a 15-minute setup huddle
Walk people through it on their own phones, in the room if you can. Show them:
- What the sign-in prompt looks like, including the “type this number into the app” step some prompts use to stop accidental approvals.
- The rule: only approve a prompt you started yourself. If a prompt shows up and you did not just try to sign in, tap deny and tell the owner. That is how attackers try to wear people down.
- Where to find their backup method, and who to call if they are locked out.
7. Plan for the lost phone and the new hire
This is where most rollouts quietly fail, so write the plan down.
- Lost or replaced phone: an admin resets that person’s sign-in methods, then the person sets up the app again on the new phone. Google describes the recovery options in recover an account protected by 2-Step Verification. Do not do the reset based on an email or text alone. Call the person, or confirm in person.
- New hire: set up the second step on day one, at their desk, with an admin or manager nearby. In Microsoft Entra, a Temporary Access Pass is a time-limited code an admin can give a new person so they can sign in and register their methods (Temporary Access Pass). Whether you can use it depends on your plan and settings.
- Someone leaves: disable their account and remove their devices the same day.
8. Check that it actually worked
A week after you finish:
- In the admin console, open the sign-in or security report and look for accounts that still have no second method registered. Both Microsoft and Google offer a report or user list for this.
- Follow up with anyone left. One unprotected account is enough for an attacker.
- Test the recovery plan once, with a willing person and a spare device, so you are not figuring it out during a real lockout.
Rollout checklist
- Account list cleaned up; former employees removed.
- Shared logins replaced with shared mailboxes or individual accounts.
- Two named admins, each with their own sign-in.
- Admins finished setup and tested a fresh sign-in.
- Everyone has a main method and a backup method.
- Backup codes or recovery info stored somewhere safe, not on the same phone.
- Team knows to deny any prompt they did not start.
- Lost-phone and new-hire steps written down and tested once.
- Admin report shows no one without a second method.
Cautions
- Do not lock out your only admin. Always keep a second admin and one working recovery path before you require anything for everyone.
- Text messages are a fallback, not a goal. Use an authenticator app or security key where you can, and move people off texts over time.
- Personal phones. Some staff will not want a work app on their own phone. Offer a security key or an office-owned device instead of skipping that person.
- Old apps and shared devices. Older email apps, scanners that send email, and shared front-desk computers may not support the second step. Test them before you require it, and ask your admin or IT help before working around any of them with a weaker setting.
- Do not approve a prompt you did not start. If prompts keep arriving, change that account’s password right away and tell the owner.
- Two-step sign-in is not the whole job. It makes stolen passwords far less useful, but you should still use unique passwords and watch for phishing links. CISA’s MFA page is a good plain-English overview to share with staff.
- This is general guidance for small businesses. If you handle health, financial, or government-contract data, check your industry rules and your insurer’s requirements.