Security checks / Check reference / Conditional Access
Conditional Access Break Glass Account Covered By Policy
Critical Severity Microsoft 365 security check in the Conditional Access domain.
Break-glass (emergency access) account is not explicitly excluded from one or more enabled Conditional Access policies. The account may be blocked or challenged during an emergency sign-in If MFA or block controls apply to the break-glass account during a tenant lockout, emergency recovery fails. Siemserva runs this check automatically across your tenant and maps every finding to the compliance frameworks below.
Check summary
What this check verifies
Break-glass (emergency access) account is not explicitly excluded from one or more enabled Conditional Access policies. The account may be blocked or challenged during an emergency sign-in
Why it matters
If MFA or block controls apply to the break-glass account during a tenant lockout, emergency recovery fails. The entire purpose of a break-glass account is to bypass normal access controls and remain accessible when the primary auth infrastructure is unavailable
How to fix it
Open each listed CA policy in the Entra admin center and add the break-glass account object ID to Exclude Users. Verify with What-If. Group-based exclusion is also acceptable if the account belongs to an excluded group
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 Conditional Access checks
Common questions
What does the Conditional Access Break Glass Account Covered By Policy check verify?
Break-glass (emergency access) account is not explicitly excluded from one or more enabled Conditional Access policies. The account may be blocked or challenged during an emergency sign-in It is a Critical Severity check in the Conditional Access domain, one of the 650+ checks Siemserva runs across Microsoft 365, Intune, Defender, and Entra ID.
How do I fix a Conditional Access Break Glass Account Covered By Policy finding?
Open each listed CA policy in the Entra admin center and add the break-glass account object ID to Exclude Users. Verify with What-If. Group-based exclusion is also acceptable if the account belongs to an excluded group 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.1.1v1, MS.AAD.2.1v1, MS.AAD.2.2v1, MS.AAD.2.3v1, MS.AAD.3.1v1, MS.AAD.3.2v1, and MCSB controls PA-4, IM-1. 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.