Security checks / Check reference / Users & accounts
User Per User MFA
Medium Severity Microsoft 365 security check in the Users & accounts domain.
User has per-user MFA enabled (legacy). Should migrate to Conditional Access MFA Per-user MFA creates fragmented enforcement and method sprawl; use Conditional Access with the unified Authentication Methods policy to standardize strong factors and reduce phishable sign-ins at scale Siemserva runs this check automatically across your tenant and maps every finding to the compliance frameworks below.
Check summary
What this check verifies
User has per-user MFA enabled (legacy). Should migrate to Conditional Access MFA
Why it matters
Per-user MFA creates fragmented enforcement and method sprawl; use Conditional Access with the unified Authentication Methods policy to standardize strong factors and reduce phishable sign-ins at scale
How to fix it
Migrate from per-user MFA to Conditional Access-based MFA enforcement
Siemserva flags every tenant where this check fails and, with Senserva Trustworthy AI remediation, can propose a validated fix you approve before it applies.
Ask your own AI about this check
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Compliance framework mappings
Findings from this check serve as evidence for:
References
Related Users & accounts checks
Common questions
What does the User Per User MFA check verify?
User has per-user MFA enabled (legacy). Should migrate to Conditional Access MFA It is a Medium Severity check in the Users & accounts domain, one of the 650+ checks Siemserva runs across Microsoft 365, Intune, Defender, and Entra ID.
How do I fix a User Per User MFA finding?
Migrate from per-user MFA to Conditional Access-based MFA enforcement Siemserva ranks the finding by Severity and, with Senserva Trustworthy AI, can propose a validated, approve-before-apply configuration fix.
Which compliance frameworks does this check evidence?
Findings from this check map to SCuBA, MCSB, NIST, SOC2, CIS, HIPAA, including SCuBA policy MS.AAD.6.1v1, and MCSB controls IM-6, IM-7. That mapping is what turns a scan finding into audit evidence.
Can I ask my own AI about this check?
Yes. This page includes a free copy-paste AI prompt carrying the check's facts: what it verifies, the risk, the remediation, and the framework mappings. Paste it into Claude, ChatGPT, or Copilot; cite-worthy detail without giving an AI access to your tenant.
All 672 checks with severities and mappings: the Microsoft 365 security checks catalog.