Back to Blog
Microsoft 365 10 min read 10 February 2026
Microsoft 365 Security Hardening: The 15-Point Checklist
Most M365 tenants are configured with insecure defaults. This checklist covers the 15 most impactful hardening steps.
Why M365 defaults are insecure
Microsoft ships M365 with permissive defaults to reduce onboarding friction. Legacy authentication protocols remain enabled, MFA is not enforced, and many security features in Business Premium are present but unconfigured. Most SME tenants are significantly below their licensed security capability.
The 15-point hardening checklist
- Enable MFA for all users — Use Conditional Access policies, not the per-user MFA legacy portal
- Block legacy authentication — Create a Conditional Access policy blocking Basic Auth. This eliminates a major attack vector for password spraying.
- Enable Security Defaults (if not using Conditional Access) — Microsoft's minimum baseline for tenants not yet ready for full Conditional Access
- Protect Global Admin accounts — Dedicated break-glass accounts, no email, FIDO2 key authentication only
- Enable Unified Audit Log — Required for forensics and compliance. Enable in Security & Compliance Centre.
- Configure DKIM and DMARC — Prevent email spoofing from your domain. DMARC policy should be p=reject once DKIM and SPF are validated.
- Enable Microsoft Defender for Office 365 — Safe Links and Safe Attachments reduce phishing and malware delivery via email
- Configure Intune device compliance policies — Require managed, compliant devices before granting M365 access
- Deploy Windows Hello for Business — Phishing-resistant authentication for Windows endpoints
- Enable Microsoft Secure Score — Baseline and track your security posture improvement
- Restrict mail forwarding — Block automatic external forwarding rules. Business Email Compromise attackers routinely set these up.
- Configure DLP policies — Prevent sensitive data (PII, financial data) leaving via email or Teams
- Set retention policies — Ensure email and Teams data is retained for the required period and deleted after
- Review and remove guest accounts — Audit Teams and SharePoint guest access quarterly
- Enable Privileged Identity Management (PIM) — Just-in-time admin access rather than standing admin privileges (requires Entra ID P2)
Need help with this?
Our team can help you assess where you stand and build a practical remediation plan. Free 30-minute consultation — no obligation.
Book a Free Consultation