- SOC 2 Readiness
- 24/7 incident line
- 24/7 security operations team
Checklist · Cloud Security
Microsoft 365 Security Hardening Checklist

Written for
Microsoft 365 administrators
Time needed
2 hours
Items
26 across 5 areas
Business email compromise almost always runs through a Microsoft 365 or similar tenant. The defaults are not enough, and most of the settings that matter are included in licences organizations already hold.
Work through this list with a global administrator. Test changes on a pilot group first.
0 of 26 in place (0%)
Identity
Stop account takeover.
The main way in.
Sharing and data
Limit accidental exposure.
Devices
Trust only healthy devices.
Monitoring
Know when something changes.
How to get the most from this list
- 01
Tick only what you can prove
If you could not show an auditor or your board the evidence today, leave it unticked. A lower honest score is more useful than a high hopeful one.
- 02
Give every gap an owner
For each unticked item, name one person and one date. Gaps without an owner are the ones still open next year.
- 03
Re-run it every quarter
Your environment changes faster than policy. Repeat the list each quarter and after any major change, and compare the scores.
Gaps we see most often
- Multi-factor authentication with exceptions nobody listed
- Inbox forwarding rules created by an attacker go unnoticed
- Any user can consent to a third-party application
Take it with you
Download the checklist as a PDF
A designed 6-page version with tick boxes, the common gaps and the questions people ask. Useful for a team review or as audit evidence.
Want a second pair of eyes?
Bring your completed list to a risk review. We will check the items that matter most for your environment, confirm the evidence and turn the gaps into a short, prioritized plan.
Common questions
Do we need a premium licence?
Many controls are in standard business licences. Conditional access and some advanced protections need higher tiers, which are usually worth it for administrators and finance staff at minimum.
Will blocking legacy authentication break things?
It can affect old mail clients and devices. Review sign-in logs first to see what still uses it.
Is multi-factor authentication enough?
It stops most attacks, but token theft and consent phishing get around it. Conditional access and monitoring cover that gap.



