azure-governance-discovery

To discover Azure Policy blockers before deployment, you need to list effective policy assignments and definitions at your subscription scope. This process distinguishes blocking policies from auto-remediation and informational effects, producing a structured governance constraints envelope for planning.

Checking Azure Policy exemptions and assignments involves querying inherited management group policies and subscription-level assignments. This excludes Defender-for-Cloud auto-assignments by default and classifies effects to generate a deterministic snapshot of your governance constraints.

Yes, Azure CLI authentication and subscription read access are required to run subscription governance discovery. The discovery workflow also requires Python 3.10 or later to process policy definitions and output the structured governance constraints envelope.

Yes, you can generate an optional markdown preview of Azure governance constraints alongside the primary schema-compliant JSON output. This preview helps visualize policy classifications, blockers, and exemptions for downstream infrastructure planning scenarios.

Yes, Azure governance discovery works with management group inherited policies by listing effective policy assignments at the subscription scope. It pulls definitions and applies operational filtering to separate blockers from auto-remediation findings, ensuring comprehensive infrastructure planning.