Entra ID (Azure AD) without enforced multi-factor authentication
Microsoft Entra ID (formerly Azure AD) controls sign-in to the portal, Microsoft 365 and federated apps. Without a Conditional Access policy (or security defaults) requiring MFA, accounts are protected by a password alone.
Why it matters
Password spraying and phishing against Entra ID are constant; Microsoft's own data shows MFA blocks the overwhelming majority of account-takeover attempts.
An admin account without MFA is the whole tenant: one compromised sign-in can create users, grant roles and read everything.
How to check for it
- Entra admin centre → Protection → Conditional Access: check for a policy requiring MFA, at minimum for directory roles.
- Review 'Security defaults' (Properties) — if off, there must be an equivalent Conditional Access policy.
How to fix it
- Enable security defaults for small tenants, or create a Conditional Access policy that requires MFA for all users (and a stricter one for admins).
- Prefer phishing-resistant methods (FIDO2 keys, passkeys, Authenticator number matching) over SMS.
SkyShield checks this automatically
Connect your AWS, Cloudflare, GitHub, GitLab, Hetzner or DigitalOcean account read-only and SkyShield flags this across every account and region, with the fix in plain words — alongside the agent that watches your servers. Start free.
FAQ
- Security defaults or Conditional Access?
- Security defaults is a free on/off baseline that requires MFA for everyone. Conditional Access (Entra ID P1+) is granular — use it when you need per-app or per-role rules.