If you run a small business on Microsoft 365, security defaults give you a solid baseline without requiring a security engineer. Many owners enable them and assume the job is done. It is not.
This guide covers what microsoft 365 security defaults small business owners need to know: what they protect, where they stop short, and which extra settings to turn on. By the end, you will have a clear checklist you can work through this week, written for business owners and office managers who know their way around Microsoft 365 but are not full-time IT staff.
What Microsoft 365 Security Defaults Actually Turn On
Security defaults flip on a set of baseline controls across your entire Microsoft 365 tenant at once. Every user gets pushed toward multi-factor authentication, or MFA, the next time they sign in. Legacy authentication protocols, older connection methods that cannot handle MFA challenges, get blocked tenant-wide. Privileged roles like Global Administrator face stricter sign-in requirements automatically.
Microsoft builds these controls into every business subscription tier. The cloud mailbox protections and additional defenses available through Microsoft Defender for Office 365 can help guard against common email-based attacks (Microsoft). That matters because email is still the most common entry point for breaches targeting small businesses.
What security defaults do not do is give you granular control. Every policy applies to every user the same way. There are no exceptions, no per-user overrides, and no conditional rules based on location or device.
That is a reasonable trade-off for organizations with no dedicated IT staff. You get meaningful protection without touching a single advanced setting. But knowing exactly what turned on helps. It also helps to know what did not turn on. That tells you what to add next.
What Security Defaults Deliberately Leave Unconfigured
Security defaults do not touch everything in your tenant. Microsoft leaves certain controls for admins to set up. Each environment is different, so admins choose settings based on their own risk level.
Anti-spam policy settings are a clear example. The default anti-spam policy ships with many settings left at their out-of-box values, and the Standard and Strict preset security policies do not configure them either (Microsoft). Microsoft documents what those settings are so you can review them yourself.
The same logic applies more broadly. The baseline recommendations built into security defaults do not cover every attack surface across every Microsoft 365 product (Microsoft). They cover the most common and highest-impact exposures, then stop.
Data retention is another area security defaults leave untouched. Microsoft starts the retention clock when an item is created by default (Microsoft). An admin can configure different retention settings using labels that users apply to Outlook folders as a default retention label (Microsoft). Most small organizations are better served by a single org-wide retention policy than by per-folder labels, but neither option is set up for you automatically.
After turning on security defaults, look at your anti-spam policies, your Safe Attachments configuration if you have Defender for Office 365, and any third-party integrations that handle mail flow. Those areas sit outside the defaults and need a separate review. A short audit of your current policy settings is a reasonable next step this week.
Conditional Access Versus Microsoft 365 Security Defaults
Security defaults and Conditional Access are two different tools. Security defaults are on or off for the whole tenant. Conditional Access lets you write specific rules. You can control who, what device, and what app. You can also set conditions that trigger MFA.
Conditional Access brings together signals from users, devices, and locations to enforce your policies (Microsoft). That matters when a blanket policy causes problems. For example, you can require MFA only for admins, or only when someone logs in from outside the office.
You can also apply rules based on the device platform or whether a device meets your compliance requirements (Microsoft). That is useful once you manage devices through Intune or a similar tool.
Conditional Access requires Microsoft Entra ID P1 licensing, which comes with Microsoft 365 Business Premium. If your subscription is Business Basic or Business Standard, that license is not included, and you would need to upgrade to Business Premium or add it separately before Conditional Access policies are available to you.
The practical rule: start with security defaults. Sometimes a blanket policy breaks your workflow. That is your sign to move to Conditional Access. It gives you finer control. Do not disable security defaults until your Conditional Access policies fully cover the same ground.
Tenant Settings Attackers Exploit in Small Business Accounts
Several Microsoft 365 settings stay off by default and create real exposure if you leave them untouched.
Legacy authentication protocols are the most common gap we find when auditing a new tenant. Tenants set up years ago and never re-audited frequently still have legacy auth active, because the original configuration predated current hardening guidance. Attackers use those same protocols to bypass MFA entirely with credential-stuffing tools. Blocking legacy auth at the tenant level is one of the fastest fixes available and rarely breaks modern workflows.
Anti-spoofing and anti-phishing controls inside Microsoft Defender for Office 365 are not enabled automatically. Without them, attackers can send email that appears to come from your own domain. Turning these on is a separate configuration step from security defaults.
Privileged accounts deserve special attention. Global admins and billing admins hold the keys to your entire tenant. CISA specifically calls out MFA for all system administrator accounts as a priority hardening step, because those accounts are high-value targets (CISA). Audit logging is off in some configurations. Without it, you cannot see what happened after a breach.
Check these four areas first. Look at anti-phishing rules, legacy auth blocks, and MFA on every admin account. Also check the audit log status. Each one is a quick win with low risk of breaking normal user workflows.
Audit Log Retention and Alert Rules to Enable Now
The unified audit log captures sign-ins, file access, admin changes, and mail-forwarding rule creation. Without it, you have no record to review after an incident. Go to the Microsoft Purview compliance portal, find Audit, and confirm the log is set to active. If it shows as off, turning it on takes about two minutes.
License tier matters for how long your audit log keeps records. Higher-tier plans extend that retention window significantly, which matters if you discover a breach weeks after it happened. Check your license documentation and extend retention if your plan allows it. That window closes fast in a real investigation, so look at this today rather than waiting.
Once logging is on, set at least three alert rules. Watch for new inbox forwarding rules and admin role changes. Also alert on bulk file downloads. These three catch the most common early-stage attack patterns. Review alerts weekly until your team builds a rhythm for spotting unusual activity.
Post-Setup Checklist to Verify Your Tenant Baseline
Run through this list in the Microsoft 365 admin center after you enable security defaults. It takes under thirty minutes for most tenants.
- Open the sign-in logs and verify MFA prompts appear for at least one test account.
- Check that legacy authentication is blocked. Try signing in with a mail client that uses basic auth. It should fail.
- Open Exchange admin center and confirm no existing inbox rules forward mail to external addresses.
- Review the global admin list. Remove any account that does not need that role today.
- Check that self-service password reset requires identity verification before it completes.
- Confirm no third-party app has been granted broad mailbox or file permissions without review.
A second pattern we see often is a global admin list that grew over time and was never trimmed. It is common to find three or four accounts holding global admin rights when only one person needs that level of access. Trimming that list is a fast, high-impact change that costs nothing and reduces the blast radius of a compromised credential significantly.
Document what you find, even when everything looks correct. A written baseline lets you spot drift when you run this check again. Assign one person to own the review, and schedule a repeat check every quarter so your protections do not quietly drift backward.
For a related guide, see Email Migration to Microsoft 365 for Small Business. If you want help with this work, see our cloud and infrastructure services and managed IT services pages.
If you would like help reviewing your Microsoft 365 tenant settings, book a free 30-minute call with Joshua to talk it through. It costs nothing and you will leave with a clear sense of where your tenant stands today.




