conditional-access-audit

Audit Azure AD Conditional Access policies for legacy authentication and MFA gaps.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/afoxnyc3/chelsea-piers-itops --skill conditional-access-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: conditional-access-audit
Source: https://github.com/afoxnyc3/chelsea-piers-itops/tree/main/plugins/azure-security/skills/conditional-access-audit
Command: npx skills add https://github.com/afoxnyc3/chelsea-piers-itops --skill conditional-access-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies security gaps in Azure AD Conditional Access that can enable legacy authentication, leave applications unprotected, or allow access without MFA requirements.

Core Features & Use Cases

  • Audit CA policies for critical misconfigurations: Detect missing legacy authentication blocking, disabled or report-only weaknesses, and MFA coverage gaps.
  • Map policy coverage to applications: Surface applications with no Conditional Access targeting, with severity tuned for business-critical workloads.
  • Review exclusions and alert signals: Highlight problematic exclusions (including overbroad group exclusions) and correlate with recent Conditional Access alerts.
  • Read-only security assurance: Provide findings and prioritized recommendations without proposing unauthorized changes.

Quick Start

Ask to run a conditional access audit for your tenant and scope it to the specific policy or application if you know its name.

Frequently Asked Questions about conditional-access-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit Azure AD Conditional Access policies for MFA enforcement gaps?

To audit Conditional Access policies for MFA gaps, evaluate grant controls within enabled and disabled states to verify MFA enforcement. This review detects incomplete coverage across applications and identifies configurations allowing access without multifactor authentication requirements.

What is the best way to find legacy authentication exposure in Azure AD?

Finding legacy authentication exposure requires auditing Azure AD Conditional Access policies to detect missing block configurations. A structured review surfaces unprotected protocols and identifies critical security gaps where legacy authentication methods bypass modern MFA enforcement.

Why does Conditional Access allow MFA bypass for excluded users?

MFA bypass occurs when Conditional Access policies contain overbroad group exclusions or lack targeting for specific applications. Auditing these exclusions and correlating with recent alerts identifies the problematic configurations allowing unauthorized authentication bypass.

Can I check which applications have no Conditional Access policy coverage?

Checking application coverage involves mapping Conditional Access policies to targeted workloads. This audit surfaces applications with no policy targeting and prioritizes findings based on business criticality to highlight unprotected resources.

Does a Conditional Access audit require write permissions to modify policies?

A Conditional Access audit does not require write permissions because it operates as a read-only security assurance review. It uses enumeration tools to analyze configurations and provide findings with prioritized recommendations without proposing unauthorized changes.

When should I run a Conditional Access policy audit for compliance preparation?

You should run a Conditional Access policy audit during security reviews, compliance preparation, and post-incident investigation. Auditing evaluates policy states and MFA enforcement to uncover legacy authentication exposure and resolve gaps before compliance validation.