audit-azure-environment

Assess Azure tenants, subscriptions, and resource groups for security, reliability, governance, and cost posture.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/QuyDu/Skills-Orchestrator --skill audit-azure-environment-quydu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-azure-environment
Source: https://github.com/QuyDu/Skills-Orchestrator/tree/main/.github/skills/audit-azure-environment
Command: npx skills add https://github.com/QuyDu/Skills-Orchestrator --skill audit-azure-environment-quydu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Evaluating a deployed Azure environment for security gaps, reliability risks, governance drift, and cost waste requires collecting scattered evidence across identity, networking, policy, and billing signals, then turning it into a defensible report. This Skill performs that assessment in a read-only, evidence-based way. ## Core Features & Use Cases - Multi-pillar assessment: Evaluates security (RBAC, network exposure, secrets, encryption), reliability (HA/DR, backup, monitoring), governance (policy compliance, tagging), and cost (overprovisioning, orphaned resources) posture. - Evidence-based findings: Every finding records a reproducible evidence path, affected scope, impact, and confidence, separating verified facts from assumptions. - Machine-readable output: Emits a structured report at reports/azure-audit-findings.json with explicit limitations for unavailable evidence. - Use Case: Point the Skill at a subscription to detect policy drift and security misconfigurations while preserving evidence suitable for a formal compliance review. ## Quick Start Audit my Azure subscription for security, reliability, governance, and cost issues and produce a findings report with evidence references.

Frequently Asked Questions about audit-azure-environment

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

FAQPage Schema
How do I audit an Azure subscription for security misconfigurations?

Define the audit scope (tenant, subscriptions, resource groups, exclusions) and provide collected evidence such as resource inventories, policy states, and identity assignments. The assessment evaluates RBAC, network exposure, secret handling, encryption, and threat protection, producing findings with evidence references.

What is the difference between auditing an Azure environment and reviewing infrastructure code?

Environment auditing assesses the live, deployed state of a tenant or subscription using collected runtime evidence. Design-time review of infrastructure code in a repository is a separate concern handled by an architecture-review skill, not this one.

Can this audit make changes to my Azure resources?

No. The assessment is strictly read-only and never mutates Azure resources or policy state. Any command that would modify the environment requires separate explicit approval outside this workflow.

What output does an Azure environment audit produce?

It produces a machine-readable report at reports/azure-audit-findings.json. Each finding includes a reproducible evidence path, affected scope, impact, confidence level, and remediation direction, plus explicit limitations for unavailable evidence.

What happens when audit evidence is incomplete or inaccessible?

The assessment fails closed when scope authority or evidence provenance cannot be established. It returns a partial assessment only when covered scope is explicit and separated from unknown scope, and never claims compliance for areas without supporting evidence.