Hardening Microsoft 365 for a 50-seat firm
How to take a small firm's Microsoft 365 tenant from password-only sign-in to a Zero Trust baseline without halting day-to-day work.
A scenario: a typical small-business tenant and the order in which I would harden it. Not a report on a specific client.
Most Microsoft 365 compromises don't start with something exotic. They start with a legacy authentication protocol nobody remembered to turn off and a shared mailbox with a weak password. A lot of that risk can be removed with configuration alone.
The starting point
Picture a 50-seat professional services firm that grew into Microsoft 365 organically: no Conditional Access, MFA "encouraged" but not enforced, legacy authentication wide open, and global admin rights handed out to anyone who once needed them.
What to change, in order
- Enforce phishing-resistant MFA through Conditional Access, scoped by risk so low-risk sign-ins stay frictionless.
- Turn off legacy authentication (POP, IMAP, basic auth), after a couple of weeks in report-only mode to catch anything that would break.
- Tier admin access. Separate, MFA-protected admin identities; as few standing global admins as possible, with the rest moved to just-in-time roles through Privileged Identity Management.
- Require baseline device compliance through Intune before granting access to corporate data.
How to know it worked
Track risky sign-in detections, the number of standing admin accounts and the share of sign-ins still using legacy protocols, before and after. Report-only mode first means the cutover itself can be short and scheduled out of hours.
The highest-leverage security work is rarely a new tool. It's turning off the defaults that should never have been on.