The 12 Most Common Entra ID Misconfigurations We Find in Every Audit (With the Exact Settings and Fixes)
We run a lot of Microsoft 365 and Entra ID security assessments. The tenants differ — different sizes, industries, and maturity levels — but the same handful of misconfigurations show up again and again. This post lists the twelve most common ones, roughly in the order we'd prioritise them, with the exact settings to look at and the fix for each.
A caveat before we start: none of these are exotic. That's the point. Identity is the number one attack path into Microsoft 365, and most of the damage we see comes from a small set of configuration gaps that are well documented and easy to close once you know to look.
1. Legacy authentication is still allowed
Where to check: Entra admin center → Protection → Conditional Access, or Get-MgIdentityConditionalAccessPolicy. Also check that Security Defaults or CA is enabled at all (Entra → Overview → Properties → Manage security defaults).
The problem: SMTP AUTH, POP, IMAP, and older Office clients use basic authentication, which can't enforce MFA. Password spray attacks against basic auth remain one of the most common initial access techniques.
The fix: Block legacy authentication with a Conditional Access policy targeting Other clients (along with the standard client apps) and apply to all users. If you're worried about breaking scanners or printers, scope exceptions to specific service accounts rather than leaving legacy auth open tenant-wide.
2. Security defaults disabled and no Conditional Access policies
Where to check: Entra admin center → Overview → Properties (security defaults toggle), and Protection → Conditional Access → Policies.
The problem: Security defaults are off — usually because someone enabled them briefly, found it broke something, and disabled them. But no replacement CA policies were ever built. Result: no baseline MFA enforcement.
The fix: Either turn security defaults back on (fine for smaller tenants without licensing for CA) or build a minimum CA baseline: require MFA for all users, block legacy auth, require compliant or hybrid-joined devices for admins. Microsoft's Conditional Access templates are a decent starting point.
3. No Conditional Access policy is in report-only mode with a plan to enforce it
Related to the above: we frequently find policies that look comprehensive but sit in report-only mode indefinitely because nobody triaged the results. "We have a policy" is not the same as "the policy is enforced."
The fix: Review report-only policy results on a schedule (even weekly), address break-glass exceptions, then enable enforcement. Keep the report-only policy copy for a test group if you need a safety net.
4. Break-glass accounts missing or misconfigured
Where to check: The set of accounts excluded from all CA policies.
The problem: We see two failure modes. Some tenants have no emergency access accounts, so a bad CA policy or MFA outage locks everyone out. Others have break-glass accounts but they're regular interactive accounts with the same weak password-and-MFA posture as everyone else, or they're excluded from policies but never monitored.
The fix: Two cloud-only emergency access accounts with long, randomly generated passwords stored in a physical safe or password manager. Exclude them from all CA policies (including MFA), monitor sign-in activity on them, and rotate credentials on a schedule.
5. Excessively broad admin roles (Global Administrator everywhere)
Where to check: Entra admin center → Identity → Roles & admins → Global Administrator (list active assignments). Also check for stand