Microsoft 365 tenants grow without a plan. Someone needed email, then Teams, then SharePoint, then Copilot, then a handful of connected apps. Security settings end up as whatever people configured along the way, and each team assumes another team owns them. A Microsoft 365 security baseline fixes that by setting a minimum standard you can check and defend.
What is a Microsoft 365 security baseline?
A Microsoft 365 security baseline is a defined minimum set of configurations for identities, devices, email, data sharing and monitoring. Microsoft publishes recommendations across Microsoft Entra ID, Defender, Intune and Microsoft 365. Your exact list depends on your size, risk, regulations and licensing, but the principle is the same: a written standard, not settings that accumulated.
1. Protect every identity
Credential theft is a common way in. Check that:
- MFA is required for all users, not just administrators
- Legacy authentication is blocked
- Risky sign-ins are monitored
- Inactive accounts are reviewed and disabled
- Guest accounts are reviewed regularly
Microsoft is also making MFA mandatory for administrative portals and, in phases, for Azure management tools. Check the current schedule in Microsoft’s documentation so these changes do not surprise your admins.
2. Use Conditional Access well
Conditional Access evaluates user, device, location, application and risk before granting access. A baseline normally includes:
- MFA for administrators and for higher-risk sign-ins
- Blocking legacy authentication
- Compliant devices for sensitive applications
- Rules for guests and external users
Test each policy in report-only mode first. A badly designed policy locks out the people you meant to protect.
3. Secure administrator accounts
An attacker who controls a global administrator can change settings, create accounts and disable protections.
- Keep the number of global administrators small
- Use separate admin accounts from daily accounts
- Use Privileged Identity Management for just-in-time elevation, where licensed
- Review privileged roles on a schedule
- Remove access that is no longer needed
Ask of each administrator: do they still need this role today?
4. Protect email
Email remains a primary attack path. If you have Microsoft Defender for Office 365, review:
- Anti-phishing and anti-malware policies
- Safe Links and Safe Attachments
- Spoofing protection and external sender tags
- Mailbox forwarding and inbox rules, since unexpected forwarding rules often signal a compromised account
5. Control sharing in Teams, SharePoint and OneDrive
Review external sharing, guest access, anonymous links, site permissions and Teams external access. The aim is to let people collaborate without exposing sensitive files. Start with the tightest setting that still lets people do their jobs, then relax where there is a business reason.
6. Manage devices with Intune
Enroll devices, require encryption and screen locks, set operating system update requirements and restrict access for non-compliant devices. This matters most for remote and hybrid staff.
7. Turn on what you are already paying for
A common gap is a licensed feature that was never configured. Depending on your plan, you may hold capabilities in Entra ID, Defender, Intune, Purview and others. Microsoft has also announced Security Copilot access for Microsoft 365 E5 customers, subject to terms and capacity, so check what your plan includes. Before you buy another security tool, list what you own and what you use.
8. Log, monitor and assign an owner
Check that audit logging is on and that sign-in logs, risky-user alerts, administrator activity and Defender incidents are reviewed. Alerts nobody reads protect nothing. Name the person or service responsible for each one and what they do when it fires.
9. Protect data and retention
Know where sensitive information lives and who can reach it. Review sensitivity labels, data loss prevention, retention policies and eDiscovery readiness. This matters more once Copilot is in use, because Copilot can make anything a user can reach easier to find.
10. Make reviews routine
Microsoft 365 security baseline changes constantly, people come and go and apps get connected. Set a recurring review with an owner and a checklist covering identity, admin roles, Conditional Access, email protection, device compliance, external sharing, alerts, data protection, app permissions and licensing.
Where to start
Begin with the basics. Who has access? To what? From which devices? Under what conditions? Where is data shared? Would you know if something went wrong? Once those answers are solid, add more advanced controls to you Microsoft 365 security baseline.
| Priority | Item | Typical effort |
| First | MFA, legacy authentication block, admin account hygiene | Days to weeks |
| Next | Conditional Access, email protection, sharing controls | Weeks |
| Then | Device compliance, data protection, logging reviews | Weeks to months |
Next step
If you are not sure your tenant meets even the first rows of that table, a Security Assessment from 360 Visibility reviews your Microsoft 365 security baseline, finds misconfigurations and unused licensed features and ranks the fixes by impact.