--- title: "Azure Policy analyzer: review, role & definition · Undominated.ai" canonical: https://undominated.ai/agents/github-azure-policy-analyzer/ description: "Requires evidence in the report and has a guardrails heading against invented policy data." --- # Azure Policy analyzer: review, role & definition · Undominated.ai > Requires evidence in the report and has a guardrails heading against invented policy data. [← Explore all agents](/agents/) SECURITY AND GOVERNANCE / GitHub # Azure Policy analyzer Requires evidence in the report and has a guardrails heading against invented policy data. [Use this definition ↓](#setup)[Original source ↗](https://github.com/github/awesome-copilot/tree/3a685010a7afdc0dbd4c83b7fbda6c316aa516e5/agents) SOURCE REVIEW Reviewed 2026-10-14 Evidence 2 linked sources Publisher GitHub Licence [MIT ↗](https://github.com/github/awesome-copilot/blob/3a685010a7afdc0dbd4c83b7fbda6c316aa516e5/LICENSE) Revision 3a685010a7af [Read what was—and wasn’t—checked ↓](#review) “Analyze Azure Policy compliance posture (NIST SP 800-53, MCSB, CIS, ISO 27001, PCI DSS, SOC 2), auto-discover scope, and return a structured single-pass risk report with evidence and remediation commands.” [GitHub · upstream description ↗](https://github.com/github/awesome-copilot/blob/3a685010a7afdc0dbd4c83b7fbda6c316aa516e5/agents/azure-policy-analyzer.agent.md) Our analysis follows below. 01 / THE REASONING ## Why this made the selection. - Guardrails forbid fabricated policy data and forbid Azure writes unless the user asks. - The report must contain ten named sections, including evidence and assumptions. ### A good fit for - Writing a single-pass Azure Policy report from resource-graph evidence. - Refusing a certification claim the guardrails prohibit. - Supply the exact authorized management-group, subscription or resource-group scope. - Receive observed policy gaps with identifiers and proposed remediation commands. ### Weigh up before choosing - Tools include edit, execute, and a wildcard azure-mcp/*, which is broader than the no-write guardrail. - The file is a Copilot agent definition and does not install itself into a host. - This review did not run the agent. - Read-only Azure operations are a prompt rule despite edit/execute and Azure MCP wildcards; automatic discovery must remain inside the user’s authorized scope. 02 / THE REVIEW RECORD ## What we actually inspected. Source review has boundaries. A clear record is more useful than a “safe” badge. ### Material inspected - agents/azure-policy-analyzer.agent.md - LICENSE - Round 2: pinned definition, output contract and permission/dependency boundaries reread on 2026-10-14 ### Our findings - Frontmatter tools include read, edit, search, execute, web, azure-mcp/*, and azure_query_azure_resource_graph. - Operating mode says not to ask clarifying questions when defaults can be applied, and not to publish to GitHub by default. - Required sections run from Objective through Next Action and include Evidence and Assumptions and Gaps. - Guardrails say never to fabricate IDs or compliance data, never to claim formal certification, and never to execute Azure writes unless the user asks. - Scope discovery prefers management group before subscription and resource group, which can materially widen what data is inspected. - If Azure MCP is unavailable it switches to Azure CLI and must disclose that fallback. ### Not established by this review - The agent was not executed against a live repository or host. The review applies to the material and revision named here. A newer upstream release can change its behavior. 03 / PUT IT TO WORK ## Use the role in your project. [Upstream setup instructions ↗](https://code.visualstudio.com/docs/copilot/customization/custom-agents) - Download the original azure-policy-analyzer.agent.md with its licence and attribution; inspect it before use. - Put a reviewed working copy at .github/agents/azure-policy-analyzer.agent.md and select it in the agent picker. - Configure the Azure MCP server or a signed-in Azure CLI with read-only access to the intended scope. VS Code ignores a declared tool that is not available rather than granting it. - Name the scope if you do not want it auto-discovered, and read the Assumptions and Gaps section before running any remediation command. ### Before you start - VS Code with GitHub Copilot custom-agent support - Azure MCP server or Azure CLI with read access to the policy scope - Optionally the Azure extension that provides azure_query_azure_resource_graph ### Compatibility GitHub Copilot custom agents in VS Code ### Implementation Markdown ### Local role instructions - read, edit, search, execute, web, todo, azure-mcp/*, and azure_query_azure_resource_graph. - The body forbids Azure write operations unless the user explicitly asks. ### Cost model MIT. The file does not state a hosted-model price. THE COMPLETE REVIEWED DEFINITION ## Read it before you reuse it. Original source bytes, with attribution. Review the host-specific setup notes above. Copy definition ↗ [Download definition + licence ↗](/resources/agents/github-azure-policy-analyzer/bundle.zip)[Raw Markdown ↗](/resources/agents/github-azure-policy-analyzer/definition.md) --- name: Azure Policy Analyzer description: Analyze Azure Policy compliance posture (NIST SP 800-53, MCSB, CIS, ISO 27001, PCI DSS, SOC 2), auto-discover scope, and return a structured single-pass risk report with evidence and remediation commands. tools: [read, edit, search, execute, web, todo, azure-mcp/*, ms-azuretools.vscode-azure-github-copilot/azure_query_azure_resource_graph] argument-hint: Describe the Azure Policy analysis task. Scope is auto-detected unless explicitly provided. --- You are an Azure Policy compliance analysis agent. ## Operating Mode - Run in a single pass. - Auto-discover scope in this order: management group, subscription, resource group. - Prefer Azure MCP for policy/compliance data retrieval. - If MCP is unavailable, use Azure CLI fallback and state it explicitly. - Do not ask clarifying questions when defaults can be applied. - Do not publish to GitHub issues or PR comments by default. ## Standards Always analyze and map findings to: - NIST SP 800-53 Rev. 5 - Microsoft Cloud Security Benchmark (MCSB) - CIS Azure Foundations - ISO 27001 - PCI DSS - SOC 2 ## Required Output Sections 1. Objective 2. Findings 3. Evidence 4. Statistics 5. Visuals 6. Best-Practice Scoring 7. Tuned Summary 8. Exemptions and Remediation 9. Assumptions and Gaps 10. Next Action ## Guardrails - Never fabricate IDs, scopes, policy effects, compliance data, or control mappings. - Never claim formal certification; report control alignment and observed gaps only. - Never execute Azure write operations unless the user explicitly asks. - Always include exact remediation commands for key findings. The download contains azure-policy-analyzer.agent.md . Keep its filename when placing it in the agent directory described above. By **GitHub**. [Exact upstream source ↗](https://raw.githubusercontent.com/github/awesome-copilot/3a685010a7afdc0dbd4c83b7fbda6c316aa516e5/agents/azure-policy-analyzer.agent.md) · [Licence](/resources/agents/github-azure-policy-analyzer/LICENSE.txt) · [Attribution](/resources/agents/github-azure-policy-analyzer/ATTRIBUTION.txt) SHA-256 c0da2f36e335d5967a27a65f4d5356d0c5e2df8d77b0bb7060a1ca90e078d1a6 Read the applicable licence MIT License Copyright GitHub, Inc. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. 04 / FOLLOW THE EVIDENCE ## The source trail. Our notes are separate from the original resource. Check upstream before adopting a new version. - [Agent profile ↗](https://github.com/github/awesome-copilot/blob/3a685010a7afdc0dbd4c83b7fbda6c316aa516e5/agents/azure-policy-analyzer.agent.md) Checked 2026-10-14 https://github.com/github/awesome-copilot/blob/3a685010a7afdc0dbd4c83b7fbda6c316aa516e5/agents/azure-policy-analyzer.agent.md Supports: Role and stated limits - [Repository licence ↗](https://github.com/github/awesome-copilot/blob/3a685010a7afdc0dbd4c83b7fbda6c316aa516e5/LICENSE) Checked 2026-10-14 https://github.com/github/awesome-copilot/blob/3a685010a7afdc0dbd4c83b7fbda6c316aa516e5/LICENSE Supports: Redistribution terms KEEP COMPARING ## Other approaches to consider. Related by category or shared topics. These are alternatives to inspect, not a measured quality order. [### Compliance mapper ↗ Maps a finding to a control only as far as the finding supports, and names the frameworks it will not pretend to certify.](/agents/pentest-compliance-mapper/)[### STIG analyst ↗ Writes a STIG-shaped finding and a keep-open justification, and does not certify the system.](/agents/pentest-stig-analyst/)[### AI-DLC Compliance Agent ↗ Organizes data classification, requirement-to-control mapping and compliance evidence into an advisory role within an AI-DLC project.](/agents/awslabs-aidlc-compliance/) [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/) ## Continue your investigation - [Find reusable instructions](/skills/) - [Inspect connections](/mcp-servers/) - [Build a toolkit](/tools/) - [Choose the model](/compare/)