- name
Perform an Azure Well-Architected Framework review of the current workload IaC and architecture, generating findings and GitHub issues for improvements.
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add github/awesome-copilot --skill azure-well-architected-review -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add github/awesome-copilot --skill azure-well-architected-review -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add github/awesome-copilot --skill azure-well-architected-review -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add github/awesome-copilot --skill azure-well-architected-review -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/github/awesome-copilot/tree/HEAD/skills/azure-well-architected-reviewFrom the publisher
This workflow performs a structured Azure Well-Architected Framework (WAF) review against your workload's IaC files and deployed infrastructure. It identifies risks across all 5 WAF pillars and creates GitHub issues to track remediation.
az) configured and authenticatedFetch current Azure WAF best practices:
https://learn.microsoft.com/en-us/azure/well-architected/https://learn.microsoft.com/en-us/azure/well-architected/service-guides/)If the microsoft.docs.mcp MCP server is available, use it to query the latest pillar checklists and service-specific recommendations.
Establish the review scope, then inventory both the code and the live environment:
**/*.bicep, bicepconfig.json**/*.tf (azurerm/azapi providers)**/azuredeploy*.json, **/*.template.json, files with $schema containing deploymentTemplateaz resource list --resource-group <rg> --output json (or subscription-wide), plus targeted az <service> show calls for configuration details the pillar checks need.Identify key Azure services in use (compute, data, networking, security, observability) and generate a Mermaid architecture diagram.
* β * allow rules)minimumTlsVersion, httpsOnly)az security pricing list)az consumption budget list)For each finding, classify:
ποΈ Azure Well-Architected Review Summary
π Review Results:
β’ IaC Files Analyzed: X
β’ Azure Services Identified: Y
β’ Total Findings: Z
β’ High Risk: A (immediate action required)
β’ Medium Risk: B (should address soon)
β’ Low Risk: C (nice to have)
π΄ Top High Risk Findings:
1. [Pillar]: [Finding] β [Why it matters]
2. [Pillar]: [Finding] β [Why it matters]
π‘ This will create Z individual GitHub issues + 1 EPIC issue.
β Proceed with creating GitHub issues? (y/n)
Gate: Only proceed to Steps 6β7 if the user gives an explicit affirmative response (e.g. "y", "yes"). On a negative, ambiguous, or missing response, do not create any GitHub issues β output the full findings as formatted markdown to the console and stop.
Label with "well-architected" and the pillar name (e.g., "security", "reliability").
Title: [WAF-<PILLAR>] [Brief Finding] β [Risk Level]
Body:
## ποΈ Well-Architected Finding: [Brief Title]
**Pillar**: [Name] | **Risk Level**: [High/Medium/Low] | **Effort**: [Low/Medium/High]
### π Description
[Clear explanation of the finding and why it matters]
### π§ Remediation
**IaC Fix** (preferred):
```bicep
// Bicep example
resource storageAccount 'Microsoft.Storage/storageAccounts@2023-05-01' = {
name: storageAccountName
location: location
sku: { name: 'Standard_ZRS' }
kind: 'StorageV2'
properties: {
minimumTlsVersion: 'TLS1_2'
allowBlobPublicAccess: false
supportsHttpsTrafficOnly: true
}
}
```
**Azure CLI fallback**:
```bash
az storage account update --name <name> --resource-group <rg> \
--min-tls-version TLS1_2 --allow-blob-public-access false --https-only true
```
### π Azure Reference
- [WAF Best Practice Link]
- [Microsoft Learn Documentation Link]
### β
Validation
- [ ] Change implemented in IaC and deployed
- [ ] Azure Policy compliance passes (if applicable)
- [ ] Microsoft Defender for Cloud recommendation resolved (if applicable)
**Well-Architected Recommendation**: [WAF checklist item this maps to]
Label with "well-architected" and "epic".
Title: [EPIC] Azure Well-Architected Review β X findings across 5 pillars
Body: Executive summary with pillar breakdown table (finding counts by pillar and risk level), Mermaid architecture diagram, prioritized checklist linking all individual issues (High β Medium β Low), and success criteria:
az resource list) and note the gapΒ© 2026 Skills Rack.
---name: azure-well-architected-reviewdescription: Perform an Azure Well-Architected Framework review of the current workload IaC and architecture, generatingβ¦---# skills/azure-well-architected-review/SKILL.mdFAQ
Download skills/azure-well-architected-review/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/github/awesome-copilot.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.