azure-well-architected-review

Reviews Azure infrastructure against the five Well-Architected Framework pillars and files findings as GitHub Issues.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/serpro-workshop-fortaleza/sifap-modernization-paula --skill azure-well-architected-review-serpro-workshop-fortaleza
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: azure-well-architected-review
Source: https://github.com/serpro-workshop-fortaleza/sifap-modernization-paula/tree/main/.github/skills/azure-well-architected-review
Command: npx skills add https://github.com/serpro-workshop-fortaleza/sifap-modernization-paula --skill azure-well-architected-review-serpro-workshop-fortaleza

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Auditing an Azure workload against the Well-Architected Framework is a manual, error-prone process that requires cross-referencing IaC files, live resources, and dozens of best-practice checklists. This Skill automates that review and turns findings into trackable GitHub Issues. ## Core Features & Use Cases - Five-Pillar Review: Systematically checks Reliability, Security, Cost Optimization, Operational Excellence, and Performance Efficiency against Terraform, Bicep, or ARM files and live Azure resources discovered via the az CLI. - Drift Detection: Compares IaC definitions with deployed resources to flag portal-created resources and configuration drift. - Risk-Rated GitHub Issues: After explicit user approval, creates one labeled issue per finding with Terraform remediation snippets, plus an EPIC issue summarizing all findings with a Mermaid architecture diagram. - Use Case: Before a production release, ask for a WAF review of your Terraform-managed workload; receive a risk-classified findings table and, upon approval, a full set of tracked remediation issues. ## Quick Start Run a Well-Architected review of the Terraform infrastructure in this repository and open GitHub Issues for the findings.

Frequently Asked Questions about azure-well-architected-review

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

FAQPage Schema
How do I run an Azure Well-Architected Framework review on my infrastructure?

Invoke the review with a request like "run a Well-Architected review on our Azure workload." The workflow reads your IaC files, inventories live resources with the az CLI, checks all five WAF pillars, and presents a risk-classified findings summary before creating any GitHub Issues.

What tools are required for an Azure architecture audit with this workflow?

You need an authenticated Azure CLI (az) for resource discovery, IaC files in the repository (Terraform preferred, Bicep or ARM also readable), and a GitHub MCP server or the gh CLI for issue creation. The microsoft.docs.mcp server is optional for fetching current WAF checklists.

Does the Well-Architected review support Bicep and ARM templates?

Yes, the review reads Bicep files and ARM deployment templates in addition to Terraform. However, remediation examples are written in Terraform with azurerm ~> 3.x, and Bicep/ARM snippets are illustrative only.

Are GitHub Issues created automatically after the review?

No. The workflow presents a summary of findings and requires an explicit affirmative response before creating any issues. Without approval, all findings are displayed as formatted Markdown in the console and nothing is filed.

What happens if no IaC files are found in the repository?

The review falls back to discovering live resources with az resource list and records the missing IaC as a finding, typically under Operational Excellence. Insufficient Azure permissions prompt a list of required read-only roles such as Reader and Security Reader.