well-architected-review
Skill70 starsChanged 4 months agoMITView on GitHub
Run a Well-Architected Framework (WAF) review against Azure resources in scope. Use when asked about best practices, architecture review, WAF assessment, or pillar compliance (Reliability, Security, Cost, Operational Excellence, Performance Efficiency).
1 other project uses a version of this.
Adopted by
Most recently taken up by
- harshgoyal1/cloud-architect-skillstheir own version, first seen Aug 28, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- harshgoyal1/cloud-architect-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
The file
Show its rules and text
We split this skill into the rules it gives an agent
27 rules. About 0 are common, 25 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈25
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
Run the following checks and report findings:
- Distinctive: line 25
Availability design: Check if critical workloads use availability zones or availability sets
- Distinctive: line 30
Backup coverage: Verify Recovery Services vaults and backup policies exist for VMs, databases, and file shares
- Distinctive: line 38
Disaster recovery: Check for paired regions, ASR replication, or geo-redundant storage
- Distinctive: line 39
Health probes: Verify App Service health checks, load balancer probes, and Container Apps health endpoints
- Distinctive: line 40
Auto-healing: Check if App Service auto-heal rules or AKS pod disruption budgets are configured
- Distinctive: line 43
Identity: Check for managed identities vs.
- Distinctive: line 48
Network isolation: Check for private endpoints, NSGs, and service endpoints
- Distinctive: line 53
Encryption: Verify encryption at rest (storage, databases) and in transit (TLS)
- Distinctive: line 54
Key management: Check Key Vault usage and key/secret expiration dates
- Distinctive: line 59
Defender for Cloud: Check Secure Score and outstanding recommendations
- Distinctive: line 68
Reservations: Check if high-usage resources could benefit from reserved instances
- Distinctive: line 69
Dev/Test pricing: Verify non-production workloads use Dev/Test subscriptions or B-series VMs
- Distinctive: line 70
Storage tiers: Check if cool/archive tiers are used for infrequently accessed data
- Very specific: line 73
IaC coverage: Check for ARM/Bicep/Terraform templates in connected repos
- Distinctive: line 74
Tagging: Verify mandatory tags (environment, owner, cost-center) exist
- Distinctive: line 78
Monitoring: Check for alert rules, action groups, and diagnostic settings
- Distinctive: line 83
Deployment practices: Check for deployment slots, blue-green, or canary configurations
- Distinctive: line 84
Automation: Check for runbooks, Logic Apps, or scheduled tasks for routine operations
- Distinctive: line 87
Autoscaling: Verify autoscale rules exist for App Service plans, VMSS, and Container Apps
- Distinctive: line 95
Caching: Check for Redis Cache or CDN usage on high-traffic workloads
- Distinctive: line 96
Database performance: Check DTU/vCore utilization, index recommendations
- Distinctive: line 97
Content delivery: Verify static assets use CDN or Front Door
- Distinctive: line 98
Connection pooling: Check for connection string patterns suggesting missing pooling
- Distinctive: line 109
If the user provides a list of accepted exceptions, do not flag those items.
- Distinctive: line 119
When exceptions are provided:
- Very specific: line 162
Use GetAzCliHelp to validate the command syntax before suggesting
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Well-Architected Review
Purpose
Perform a structured assessment of Azure resources against the five pillars of the Microsoft Azure Well-Architected Framework. Produce a scored report with prioritized recommendations.
When to use this skill
- User asks "are we following best practices?"
- User asks for a WAF or Well-Architected review
- User wants to assess architecture quality before a launch or audit
- Periodic (quarterly) architecture health check
Pillars and checks
1. Reliability
Run the following checks and report findings:
- Availability design: Check if critical workloads use availability zones or availability sets
az vm list --query "[].{name:name, zones:zones, availabilitySet:availabilitySet.id}" -o table az appservice plan list --query "[].{name:name, zoneRedundant:zoneRedundant, sku:sku.name}" -o table - Backup coverage: Verify Recovery Services vaults and backup policies exist for VMs, databases, and file shares
Then for each vault:az backup vault list -o tableaz backup item list --vault-name <vault> --resource-group <rg> --backup-management-type AzureIaasVM -o table - Disaster recovery: Check for paired regions, ASR replication, or geo-redundant storage
- Health probes: Verify App Service health checks, load balancer probes, and Container Apps health endpoints
- Auto-healing: Check if App Service auto-heal rules or AKS pod disruption budgets are configured
2. Security
- Identity: Check for managed identities vs. stored credentials
az webapp identity show --name <app> --resource-group <rg> az ad app list --query "[].{name:displayName, passwordCredentials:passwordCredentials}" -o table - Network isolation: Check for private endpoints, NSGs, and service endpoints
az network private-endpoint list -o table az network nsg list -o table - Encryption: Verify encryption at rest (storage, databases) and in transit (TLS)
- Key management: Check Key Vault usage and key/secret expiration dates
az keyvault list -o table az keyvault secret list --vault-name <vault> --query "[].{name:name, expires:attributes.expires}" -o table - Defender for Cloud: Check Secure Score and outstanding recommendations
3. Cost Optimization
- Rightsizing: Identify underutilized VMs (CPU < 5% average over 14 days)
- Orphaned resources: Find unattached disks, unused public IPs, empty resource groups
az disk list --query "[?managedBy==null].{name:name, size:diskSizeGb, rg:resourceGroup}" -o table az network public-ip list --query "[?ipConfiguration==null].{name:name, rg:resourceGroup}" -o table - Reservations: Check if high-usage resources could benefit from reserved instances
- Dev/Test pricing: Verify non-production workloads use Dev/Test subscriptions or B-series VMs
- Storage tiers: Check if cool/archive tiers are used for infrequently accessed data
4. Operational Excellence
- IaC coverage: Check for ARM/Bicep/Terraform templates in connected repos
- Tagging: Verify mandatory tags (environment, owner, cost-center) exist
az resource list --query "[?tags.environment==null].{name:name, type:type, rg:resourceGroup}" -o table - Monitoring: Check for alert rules, action groups, and diagnostic settings
az monitor metrics alert list -o table az monitor diagnostic-settings list --resource <id> -o table - Deployment practices: Check for deployment slots, blue-green, or canary configurations
- Automation: Check for runbooks, Logic Apps, or scheduled tasks for routine operations
5. Performance Efficiency
- Autoscaling: Verify autoscale rules exist for App Service plans, VMSS, and Container Apps
Note:az monitor autoscale list --resource-group <rg> -o tableaz monitor autoscale listrequires--resource-group. Iterate over relevant resource groups, or use Azure Resource Graph:az graph query -q "resources | where type == 'microsoft.insights/autoscalesettings'" -o table - Caching: Check for Redis Cache or CDN usage on high-traffic workloads
- Database performance: Check DTU/vCore utilization, index recommendations
- Content delivery: Verify static assets use CDN or Front Door
- Connection pooling: Check for connection string patterns suggesting missing pooling
Scoring model
For each check, assign one of:
- ✅ Pass — follows best practice
- ⚠️ Needs attention — partially implemented or at risk
- ❌ Fail — not implemented, risk exposure
Accepted exceptions (optional)
If the user provides a list of accepted exceptions, do not flag those items. Instead, note them in the report as Accepted Exception with the reason provided.
Example format the user may provide:
| Check | Reason |
| 1.1 Availability zones | Single-AZ by design to reduce cost |
| 3.3 Reserved instances | Short-term workload, reservations not applicable |
| 5.5 Connection pooling | Legacy app uses persistent connections by design |
When exceptions are provided:
- Skip the flagged checks in scoring
- List them in a separate "Accepted Exceptions" section at the end of the report
- Recalculate the overall score excluding excepted checks
Expected output
Report header (mandatory — use this exact format)
Well-Architected Review Report
| Field | Value |
| Subscription | (name + ID) |
| Assessment Date | YYYY-MM-DD |
| Overall Score | XX% |
Summary
A table with pillar scores:
| Pillar | Pass | Needs Attention | Fail | Score |
| Reliability | X | Y | Z | X/(X+Y+Z) % |
| Security | ... | ... | ... | ... |
| Cost Optimization | ... | ... | ... | ... |
| Operational Excellence | ... | ... | ... | ... |
| Performance Efficiency | ... | ... | ... | ... |
| Overall | avg % |
Detailed findings
For each pillar, list every check with:
- Status (pass/attention/fail)
- Evidence (command output or observation)
- Recommendation (specific action to take)
- Priority (Critical / High / Medium / Low)
- Reference link to WAF documentation
Top 5 recommendations
Ordered by impact, with estimated effort (hours/days) for each.
Remediation guidance
For each ❌ or ⚠️ finding, include in the output:
- The specific
azCLI command to remediate (suggest only — do not execute) - Use
GetAzCliHelpto validate the command syntax before suggesting - The official Microsoft Learn documentation link for the remediation
References
- WAF Overview: https://learn.microsoft.com/en-us/azure/well-architected/
- Reliability: https://learn.microsoft.com/en-us/azure/well-architected/reliability/
- Security: https://learn.microsoft.com/en-us/azure/well-architected/security/
- Cost Optimization: https://learn.microsoft.com/en-us/azure/well-architected/cost-optimization/
- Operational Excellence: https://learn.microsoft.com/en-us/azure/well-architected/operational-excellence/
- Performance Efficiency: https://learn.microsoft.com/en-us/azure/well-architected/performance-efficiency/
Sample output
The following is a redacted example of what the report looks like when run against a subscription.
Well-Architected Review Report
| Field | Value |
| Subscription | contoso-prod-001 (a1b2c3d4-e5f6-7890-abcd-ef1234567890) |
| Assessment Date | 2026-07-15 |
| Overall Score | 68% |
Summary
| Pillar | Pass | Needs Attention | Fail | Score |
| Reliability | 3 | 1 | 1 | 60% |
| Security | 2 | 2 | 1 | 40% |
| Cost Optimization | 4 | 1 | 0 | 80% |
| Operational Excellence | 3 | 1 | 1 | 60% |
| Performance Efficiency | 4 | 0 | 1 | 80% |
| Overall | 16 | 5 | 4 | 68% |
Detailed findings (sample)
Reliability
| Check | Status | Evidence | Priority |
| 1.1 Availability zones | ❌ Fail | VMs vm-web-01, vm-web-02 in rg-app-prod have no zones configured | Critical |
| 1.2 Backup coverage | ✅ Pass | Recovery Services vault rsv-prod-eastus protects 4/4 VMs | — |
| 1.3 Disaster recovery | ⚠️ Needs attention | No ASR replication configured for rg-app-prod | High |
Security
| Check | Status | Evidence | Priority |
| 2.1 Managed identity | ✅ Pass | App Service app-api-prod uses System-Assigned MI | — |
| 2.2 Network isolation | ❌ Fail | SQL Server sql-contoso-prod has public endpoint enabled | Critical |
| 2.3 Key management | ⚠️ Needs attention | 2 secrets in kv-contoso-prod expire within 30 days | High |
Top 5 recommendations
| # | Recommendation | Impact | Effort |
| 1 | Enable availability zones on production VMs | Critical | 2 hours |
| 2 | Disable public endpoint on SQL Server | Critical | 30 min |
| 3 | Configure ASR replication for rg-app-prod | High | 4 hours |
| 4 | Rotate expiring Key Vault secrets | High | 1 hour |
| 5 | Add autoscale rules to App Service plan asp-prod | Medium | 30 min |
Remediation guidance (sample)
# Enable availability zones on VM (redeploy required)
az vm create --name vm-web-01 --resource-group rg-app-prod --zone 1 ...
# Disable public access on SQL Server
az sql server update --name sql-contoso-prod --resource-group rg-data-prod --set publicNetworkAccess="Disabled"
# Add autoscale rule to App Service plan
az monitor autoscale create --resource-group rg-app-prod --resource asp-prod --resource-type Microsoft.Web/serverfarms --min-count 2 --max-count 10 --count 2Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

