How to Switch On MFA for Every Microsoft 365 User in a Small Business
For most businesses with 5 to 50 staff, the quickest route to MFA for every Microsoft 365 user is Security Defaults in the Microsoft Entra admin centre. This guide gives the admin path, the checks to run before enabling it, when Conditional Access is the better fit, and the accounts that deserve extra attention.
Check what is already enforcing MFA in your tenant
Before changing anything, sign in to the Microsoft Entra admin centre as a Global Administrator and look at what already exists. If your tenant has Conditional Access policies that require MFA, or per-user MFA settings from an earlier setup, enabling Security Defaults on top creates overlapping controls that are hard to troubleshoot. Review the Conditional Access policy list first and note any policy that already targets all users.
Make a short inventory of who signs in. Confirm every one of your 5 to 50 staff has an individual account, and list any shared mailboxes, meeting room accounts or service accounts that are used by software rather than a person. Shared and service accounts cannot complete an MFA prompt, so they need to be identified now rather than discovered when a scanner or line-of-business app stops working.
Enable Security Defaults in the Entra admin centre
For many small tenants without Conditional Access, Security Defaults is the simplest route. In the Microsoft Entra admin centre, go to Identity, then Overview, then Properties, then Manage security defaults. Set Security defaults to Enabled and select Save. Microsoft has moved these menus before, so check the current path against its security defaults documentation if your portal looks different.
Security Defaults applies baseline protections to the whole tenant, including requiring users to register for MFA, so you cannot pick which users it covers. Once enabled, each user is prompted to register an authentication method, usually the Microsoft Authenticator app, at their next sign-in. Choose a quiet time to switch it on and tell staff in advance what the prompt will look like.
Test sign-in, legacy apps and recovery before and after
Security Defaults blocks legacy authentication, which affects older mail clients, some scanners that send email through Microsoft 365, and old devices that cannot use modern sign-in. Ask your IT provider or check each device and application that connects to mailboxes, and test with one pilot user and one administrator before the wider rollout. Anything that stops working needs to be moved to modern authentication or replaced.
Decide the recovery route for a lost or replaced phone before staff need it. A user who loses their phone cannot pass the MFA prompt, so an administrator will need to reset their registered methods and have them register again. Write down who can do this, how they will verify the person asking, and keep the process short enough that a locked-out member of staff is back in the same day.
When to use Conditional Access instead
Conditional Access gives finer control, such as requiring MFA for all users but with different rules for administrators, or blocking sign-in from certain locations. It requires a Microsoft Entra ID P1 licence, and Microsoft 365 plans differ in what they include, so confirm the licence assigned to your users in Microsoft's current licensing documentation rather than assuming it is covered.
Security Defaults and Conditional Access cannot run side by side. If you move to Conditional Access, you disable Security Defaults first and then build a policy that requires MFA for all users and all cloud apps, so there is no gap between the two. Test the policy in report-only mode where available, and keep one administrator account excluded and monitored so a policy mistake cannot lock the whole business out.
Accounts that need stronger controls
Administrator accounts carry the most risk. Keep at least two protected admin accounts, use them only for administration rather than daily email, and test your emergency access arrangement so you know it works. A single admin whose phone is lost or whose account is compromised can leave you unable to manage the tenant.
Shared mailboxes should have sign-in blocked so nobody uses them as an interactive login, and access should be granted through individual accounts instead. Service accounts used by software need to be documented, given long unique passwords, and moved to a method that does not depend on a human MFA prompt. Directors and finance staff are the most common targets for invoice fraud, so check their registered methods first and prefer the authenticator app over text messages where you can.
Common questions
- Does Security Defaults cover every user in my Microsoft 365 tenant?
- Yes. Security Defaults applies to the whole Microsoft Entra tenant and requires all users to register for MFA. You cannot exclude individual users or target groups with it. If you need exceptions or different rules for administrators, you need Conditional Access, which requires a Microsoft Entra ID P1 licence.
- Can I use Security Defaults and Conditional Access together?
- No. Microsoft does not support running both at once. If you want to use Conditional Access, disable Security Defaults first and then create a policy that requires MFA for all users, so the tenant is not left unprotected between the two. Test the policy before relying on it.
- What happens to older email clients and scanners when I turn it on?
- Security Defaults blocks legacy authentication, so older mail clients, some multifunction printers or scanners that send email, and old devices without modern sign-in may stop connecting. Identify these before you switch it on, test with a pilot user, and move affected devices to modern authentication or replace them.
- What should I do if a member of staff loses their phone?
- An administrator needs to reset that user's registered authentication methods in Microsoft Entra so they can register a new device at their next sign-in. Agree in advance who can do this and how they confirm the identity of the person asking, because a request to reset MFA is a common route for attackers to take over an account.
- Do the UK data protection regulators expect small businesses to use MFA?
- The ICO advises organisations to use multi-factor authentication wherever possible and describes it as requiring at least two separate forms of identification. This is security guidance rather than a Microsoft configuration instruction, but enabling MFA on Microsoft 365 is a direct way to follow it for the systems holding your email and files.
Official UK sources checked
- Practical ways to keep your IT systems safe and secure
- Information Commissioner's Office shares cyber security ...
- Selecting right methods to authenticate customers
- Protecting business accounts and information from cyber ...
- Actions to take when the cyber threat is heightened
- ico.org.uk · passwords-in-online-servicesPasswords in online services | ICO
Related UK cybersecurity guides
How to Enforce 2-Step Verification in Google Workspace
Enforcing 2-Step Verification in Google Workspace is done from the Admin console under Security, Authentication. This guide covers the admin path, choosing an organisational unit or group, staging the rollout so staff can enrol, protecting administrator accounts first, and handling recovery codes and lost devices before enforcement begins.
How to Remove Local Admin Rights in a Small Business Without Stopping Work
Staff in a small business rarely need administrator rights for daily work, but removing them overnight causes blocked installs and angry messages. This guide sets out a staged route for Windows and macOS: find out who has admin rights and why, pilot with a few people, move administration to a separate support account, and set up a quick exception process so work continues while risk falls.
What to do when an old Windows computer cannot be replaced yet
Some businesses run a line-of-business application that only works on an old Windows computer. Once Microsoft stops issuing security updates, that machine is an unsupported device. This guide covers how to isolate it, restrict who and what can reach it, record a replacement date and understand why compensating controls reduce risk without making the device compliant for Cyber Essentials.
