Cloud & Microsoft 365

Microsoft 365 Security Checklist for Small Businesses: 15 Settings to Check

A Microsoft 365 security checklist for small firms: MFA, conditional access, legacy auth, admin accounts, Defender, Intune, sharing, DMARC and CISA baselines.

By Boston IT Services Group · Published November 14, 2026 · Updated November 14, 2026 · 9 min read

In short

This Microsoft 365 security checklist covers the 15 tenant settings we check first at small businesses, with a short reason and how-to for each. It starts with identity (MFA, conditional access, legacy authentication, admin accounts), moves to email and devices (Defender for Office 365, Defender for Business, Intune), and finishes with sharing, auditing, DMARC, backup, Secure Score and CISA's SCuBA baselines.

This Microsoft 365 security checklist is the list we work through when we take over a small business tenant. Most of the items are settings, not purchases, and a competent admin can finish the first half in a day. The order matters: identity first, because most Microsoft 365 breaches start with a stolen password, then email, devices, data and monitoring.

A note on licensing before you start. Several items depend on your plan. Microsoft 365 Business Basic and Business Standard include Microsoft Entra ID Free. Business Premium adds Entra ID P1 (with conditional access), Intune Plan 1, Microsoft Defender for Business and Defender for Office 365 Plan 1, according to Microsoft's security overview. We flag which items need Premium.

The Microsoft 365 security checklist at a glance

# Item Needs Business Premium?
1 Choose security defaults or conditional access Conditional access does
2 Require MFA for every user No
3 Move admins to phishing-resistant MFA No (conditional access helps enforce it)
4 Block legacy authentication No
5 Clean up admin accounts No
6 Set up two emergency access accounts No
7 Apply Defender for Office 365 preset policies Yes (Plan 1)
8 Deploy Defender for Business on every device Yes
9 Enroll devices in Intune and require compliance Yes
10 Tighten SharePoint and OneDrive external sharing No
11 Confirm mailbox auditing and audit log retention No
12 Publish SPF, DKIM and DMARC No
13 Back up Microsoft 365 data Separate product or tool
14 Track Secure Score monthly No
15 Check against CISA SCuBA baselines No

Identity: who can sign in, and how

1. Choose security defaults or conditional access

Why: you need one of them, and you cannot run both. Security defaults are free and on by default for newer tenants. They require all users to register for MFA, require MFA for admins, prompt users for MFA when Microsoft judges it necessary, block legacy authentication, block device code flow and protect Azure management. Conditional access needs at least Entra ID P1, and Microsoft says organizations with P1 or P2 licenses probably should not rely on security defaults.

How: on Basic or Standard, confirm security defaults are enabled in the Entra admin center under Entra ID, Overview, Properties. On Business Premium, build conditional access policies that cover the same ground (MFA for all users, MFA for admins, block legacy authentication) and only then disable security defaults. Microsoft provides managed policies and templates that mirror security defaults.

2. Require MFA for every user

Why: a password alone is not enough, and attackers target ordinary users as well as admins. Microsoft says MFA can block over 99.2% of identity-based attacks.

How: with security defaults, users register through the Microsoft Authenticator app with number matching. With conditional access, target all users and all cloud apps, and keep exclusions to your emergency access accounts. Check the sign-in logs for anyone still signing in with a single factor.

3. Move admins to phishing-resistant MFA

Why: CISA calls phishing-resistant MFA the gold standard and notes that code-based and push MFA can be beaten by phishing pages, push bombing and SIM swaps. Admin accounts are the highest-value target in the tenant.

How: register passkeys (FIDO2 security keys or device-bound passkeys), Windows Hello for Business or certificate-based authentication for anyone with an admin role. With Entra ID P1, use a conditional access authentication strength policy to require phishing-resistant methods for admin roles. Then expand to finance staff and executives.

Microsoft has also made MFA mandatory for its admin portals. Enforcement began in October 2024 for the Azure portal, Entra admin center and Intune admin center, and in February 2025 for the Microsoft 365 admin center, per Microsoft's mandatory MFA documentation. That covers the portals, not your users' email, so items 2 and 3 still matter.

4. Block legacy authentication

Why: legacy protocols such as older POP, IMAP and SMTP clients cannot do MFA. Microsoft's security defaults documentation says most compromising sign-in attempts come from legacy authentication, and that an attacker can use an older protocol to bypass MFA.

How: security defaults block it automatically. With conditional access, apply Microsoft's "block legacy authentication" policy. The usual casualty is a copier or line-of-business app that sends mail with SMTP AUTH. Exchange Online's SMTP AUTH basic authentication has its own timeline, which Microsoft has revised more than once. Microsoft's January 2026 update says behavior stays unchanged through December 2026, basic auth will be disabled by default for existing tenants at the end of December 2026 (admins can re-enable it), and a final removal date will be announced in the second half of 2027. Inventory your scanners and apps that send mail now and move them to OAuth or another supported method.

5. Clean up admin accounts

Why: every account with an admin role is a way to take over the whole tenant.

How: Microsoft's role best practices recommend fewer than five Global Administrators and fewer than ten privileged role assignments. Give admins a separate admin account that has no mailbox and is not used for daily work. Use the least-privileged role that does the job (Exchange Administrator, User Administrator, Helpdesk Administrator) instead of Global Administrator. Use cloud-only accounts for admin roles, not accounts synced from on-premises Active Directory. Remove admin rights from former staff and former IT vendors. We find leftover vendor accounts in a surprising number of tenants.

6. Set up two emergency access accounts

Why: if conditional access or an MFA outage locks everyone out, you need a way back in.

How: Microsoft recommends two cloud-only emergency access accounts permanently assigned Global Administrator, not tied to a specific person. Protect them with passkeys or certificate-based authentication, because Microsoft's mandatory MFA also applies to break-glass accounts. Store the credentials offline, monitor every sign-in to them, and test them on a schedule.

Email and devices

7. Apply Defender for Office 365 preset policies

Why: email is still the main delivery route for phishing and malware. Every Microsoft 365 for business plan includes built-in anti-malware, anti-spam and spoofing protection. Business Premium adds Defender for Office 365 Plan 1, with Safe Links, Safe Attachments and impersonation protection.

How: in the Microsoft Defender portal, assign the Standard or Strict preset security policy to all users. Microsoft says the default settings give a good level of protection and recommends the preset policies for better protection. Turn on impersonation protection for executives and anyone who approves payments.

8. Deploy Defender for Business on every device

Why: endpoint detection and response (EDR) is one of the controls cyber insurers ask about most. Microsoft describes Defender for Business as equivalent to Defender for Endpoint Plan 1 with some Plan 2 features.

How: onboard every Windows and Mac device, and servers if you license them, through Intune or the onboarding package. Then check the device inventory for gaps. Decide who reviews alerts, and how quickly. Our guide to cyber insurance requirements covers what underwriters expect here.

9. Enroll devices in Intune and require compliance

Why: a valid password on an unmanaged, unpatched home PC is still a risk. Intune Plan 1 lets you manage company devices and, for personal phones, manage just the company data.

How: enroll company laptops and phones. Create compliance policies (encryption on, supported OS version, Defender running, screen lock). Then add a conditional access policy that requires a compliant device for access to email and files, starting with a pilot group. For personal phones, use app protection policies instead of full enrollment. If you still have Windows 10 machines, see our notes on Windows 10 end of support.

Data, sharing and monitoring

10. Tighten SharePoint and OneDrive external sharing

Why: "Anyone" links can be forwarded endlessly and accessed without signing in.

How: in the SharePoint admin center under Policies, Sharing, choose the most restrictive level that still lets people work. Microsoft's options run from Anyone, to New and existing guests, to Existing guests, to Only people in your organization. For most professional firms, New and existing guests is the right default. If you keep Anyone links, set them to expire and limit them to view only. Set the default link type to Specific people, set guest access to expire, and use site-level settings to lock down sensitive sites further.

11. Confirm mailbox auditing and audit log retention

Why: after a business email compromise, the first questions are what the attacker read, sent and changed. You can only answer them if the logs exist.

How: mailbox audit logging is on by default in all organizations, but confirm nobody turned it off by running Get-OrganizationConfig | Format-List AuditDisabled in Exchange Online PowerShell. The value should be False. Check that inbox rule changes are being logged, review your audit log retention in Microsoft Purview, and know how to search the log before you need to.

12. Publish SPF, DKIM and DMARC

Why: without them, anyone can send email that appears to come from your domain. Microsoft's guidance is direct: SPF, DKIM and DMARC work together, and anything less than all of them gives substandard protection.

How: publish an SPF record listing every service that sends mail for your domain (Microsoft 365, your marketing platform, your billing system). Enable DKIM signing for your custom domain in the Defender portal. Publish a DMARC record starting with monitoring (p=none) and a reporting address, review the reports, then move to quarantine and eventually reject once legitimate senders all pass.

13. Back up Microsoft 365 data

Why: built-in retention helps with accidental deletes, but it is not a backup you control. Our post on backup vs disaster recovery explains Microsoft's shared responsibility model in more detail.

How: use Microsoft's separate Microsoft 365 Backup product or a third-party tool to back up Exchange, OneDrive and SharePoint. Set retention to match your obligations, protect the backup console with separate admin credentials and MFA, and test a restore.

14. Track Secure Score monthly

Why: Microsoft Secure Score in the Defender portal turns your configuration into a number with a ranked list of recommended actions. It is not a guarantee of anything, and Microsoft says so, but it is a good way to spot drift.

How: review it monthly. For items you deliberately skip, mark them as risk accepted or resolved through a third-party tool, with a note explaining why, so the score reflects reality.

15. Check against CISA SCuBA baselines

Why: CISA's Secure Cloud Business Applications (SCuBA) project publishes secure configuration baselines for Microsoft 365 and a free assessment tool, ScubaGear, that checks a tenant against them. Federal civilian agencies are required to apply the baselines under BOD 25-01, issued December 17, 2024. CISA says all organizations can use SCuBA to strengthen SaaS security.

How: run ScubaGear against your tenant (it is a PowerShell tool and needs an account with enough admin rights to read your settings), read the report, and treat it as a second opinion. Some baseline settings are written for federal agencies and will not suit a 15-person firm. Decide each one on purpose and document why.

Where to go from here

If you get through items 1 through 6 this month, you have closed the gaps behind most of the Microsoft 365 compromises we see. Items 7 through 15 take longer and pay off over time.

Our cloud services team runs this checklist as a tenant review and fixes what it finds, and our cybersecurity services keep watch afterward. If your team just needs help with user-side changes such as MFA enrollment and passkeys, our IT help desk handles that rollout.

Frequently asked questions

Should a small business use security defaults or conditional access?

If you have no Microsoft Entra ID P1 licenses, use security defaults, which are free and turn on MFA and block legacy authentication. If you have Microsoft 365 Business Premium, which includes Entra ID P1, Microsoft says security defaults are probably not right for you, and conditional access gives you finer control. You cannot run both at once, so disable security defaults only after equivalent conditional access policies are in place.

Does Microsoft 365 Business Premium include conditional access?

Yes. Microsoft's documentation lists Microsoft Entra ID Plan 1 as part of Business Premium, and Entra ID P1 includes conditional access. Business Premium also includes Intune Plan 1, Microsoft Defender for Business and Defender for Office 365 Plan 1. Business Basic and Business Standard include Entra ID Free, which supports security defaults but not conditional access. Business Premium is designed for organizations of up to 300 users.

What is phishing-resistant MFA in Microsoft 365?

Phishing-resistant MFA uses methods that cannot be relayed through a fake login page, such as passkeys (FIDO2 security keys or device-bound passkeys), Windows Hello for Business and certificate-based authentication. CISA calls phishing-resistant MFA the gold standard. App push notifications and SMS codes are much better than passwords alone but can be defeated by phishing kits and push fatigue attacks. Start with admin accounts.

What are the CISA SCuBA baselines for Microsoft 365?

SCuBA (Secure Cloud Business Applications) is a CISA project that publishes secure configuration baselines for Microsoft 365 and a free assessment tool called ScubaGear. The baselines cover products including Entra ID, Exchange Online, SharePoint, Teams and Microsoft's security suite. Federal agencies must apply them under Binding Operational Directive 25-01, but CISA says all organizations can use SCuBA to strengthen their cloud security.

How often should we review our Microsoft 365 security settings?

Review Secure Score and admin role assignments monthly, and do a full configuration review against a baseline such as CISA SCuBA at least once a year. Also review after big changes: new hires in admin roles, a merger, a new line-of-business app, or a licensing change. Microsoft changes defaults and retires features regularly, so a tenant that was well configured two years ago may have drifted.

Sources and references

  1. Microsoft Learn: Configure security defaults for Microsoft Entra ID
  2. Microsoft Learn: Microsoft 365 for business security overview
  3. Microsoft Learn: Plan for mandatory Microsoft Entra multifactor authentication
  4. Microsoft Learn: Best practices for Microsoft Entra roles
  5. Microsoft Exchange Team Blog: Updated Exchange Online SMTP AUTH Basic Authentication deprecation timeline
  6. Microsoft Learn: Manage sharing settings for SharePoint and OneDrive
  7. Microsoft Learn: Manage mailbox auditing
  8. Microsoft Learn: How email authentication works in Microsoft 365
  9. Microsoft Learn: Microsoft Secure Score
  10. Microsoft Learn: Overview of Microsoft 365 Backup
  11. CISA: Secure Cloud Business Applications (SCuBA) Project
  12. CISA: BOD 25-01, Implementing Secure Practices for Cloud Services
  13. CISA ScubaGear (GitHub)
  14. CISA: Implementing Phishing-Resistant MFA (fact sheet)

Talk to a Boston IT engineer

Tell us what is slowing your team down. We will review your current setup and send back a plain-English plan with priorities, at no cost.