Eleven Microsoft 365 data protection checks
Review sign-in, administrator roles, sharing, email controls, mobile access and audit evidence around your Microsoft 365 business data.

A Microsoft 365 licence tells you which features you can use. It can’t tell you how your tenant is set up or who follows up on a warning.
Use these eleven checks to review protection around business data. For each one, record the setting, an example of its behaviour and the person responsible for maintaining it.
1. Confirm the sign-in policy
Check whether security defaults or a planned Conditional Access policy set protects your tenant. It’s one or the other: you don’t turn both on together.
Microsoft’s security defaults guidance explains the baseline and its limits. Confirm users have registered the sign-in methods your policy requires and that recovery doesn’t depend on one unavailable phone.
2. Limit administrator roles
Review who holds privileged roles and why. Use separate accounts for administrative work, and remove access that no longer has an owner.
A role governing tenant administration doesn’t replace the permissions governing an individual document.
3. Identify old authentication dependencies
Microsoft began switching off basic authentication for most Exchange Online protocols in October 2022. SMTP AUTH, which many scan-to-email printers use, was left out of that change, and Microsoft plans to turn off its basic authentication by default for existing tenants at the end of December 2026. Check the sign-in logs for applications, printers or scripts that still use an older method, such as a scan-to-email printer, and move each one to a supported replacement.
An unexplained exception can leave a gap long after the original migration finishes.
4. Test shared-device behaviour
Check screen locking, browser sessions and sign-out on shared equipment. A web session setting doesn’t necessarily lock the device or remove downloaded files.
Test the applications staff use before treating a timeout as effective protection.
5. Review calendar exposure
Inspect external calendar-sharing settings and a sample shared calendar. Decide what information an external contact needs.
Avoid placing confidential client details in an appointment title that other people can see.
6. Check email protection and ownership
Identify the mail protections licensed and configured, then confirm where alerts go. Microsoft now uses Defender for Office 365 for the capabilities formerly described as Office 365 Advanced Threat Protection.
Check which plan you have. Business Premium includes Defender for Office 365 Plan 1; Business Basic and Standard don’t.
7. Examine sensitive-data warnings
If you’re using data loss prevention, test a harmless sample against the policy. Confirm which locations it covers and who reviews exceptions.
A warning that users can override has different consequences from a blocked action.
8. Confirm mobile-data handling
Review managed-device or app-protection policies against the supported mobile apps. Check whether work data can be copied into personal storage.
Record what a selective removal can affect before using it. Don’t assume every phone or application supports the same control.
9. Inspect file-sharing permissions
Review external guests, broad links and access inherited from groups. Give each shared workspace an owner who can approve access and remove it when work ends.
Include departures and supplier changes in that review.
10. Verify usable audit evidence
Run a sample search for an action you expect to investigate. Check whether auditing is enabled, which events are recorded and how long they’re available.
Microsoft Purview’s audit comparison explains licensing differences. Assign someone to investigate relevant findings; collecting events alone doesn’t resolve them.
11. Test protected delivery and staff reporting
Try the method your business uses for sending sensitive information to an external recipient. Check the recipient’s identity and access, including any encryption or restricted-sharing settings.
Encryption doesn’t protect a message from someone who legitimately controls the receiving account. Give staff a clear route for reporting a mistaken send or suspicious request, and practise the response with harmless test data.


