agentleFS
ricmmartinsricmmartins/azure-sre-agent-skills/skills/01-well-architected-review/SKILL.md

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

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
  1. Distinctive:

    Run the following checks and report findings:

    line 23
  2. Distinctive:

    Availability design: Check if critical workloads use availability zones or availability sets

    line 25
  3. Distinctive:

    Backup coverage: Verify Recovery Services vaults and backup policies exist for VMs, databases, and file shares

    line 30
  4. Distinctive:

    Disaster recovery: Check for paired regions, ASR replication, or geo-redundant storage

    line 38
  5. Distinctive:

    Health probes: Verify App Service health checks, load balancer probes, and Container Apps health endpoints

    line 39
  6. Distinctive:

    Auto-healing: Check if App Service auto-heal rules or AKS pod disruption budgets are configured

    line 40
  7. Distinctive:

    Identity: Check for managed identities vs.

    line 43
  8. Distinctive:

    Network isolation: Check for private endpoints, NSGs, and service endpoints

    line 48
  9. Distinctive:

    Encryption: Verify encryption at rest (storage, databases) and in transit (TLS)

    line 53
  10. Distinctive:

    Key management: Check Key Vault usage and key/secret expiration dates

    line 54
  11. Distinctive:

    Defender for Cloud: Check Secure Score and outstanding recommendations

    line 59
  12. Distinctive:

    Reservations: Check if high-usage resources could benefit from reserved instances

    line 68
  13. Distinctive:

    Dev/Test pricing: Verify non-production workloads use Dev/Test subscriptions or B-series VMs

    line 69
  14. Distinctive:

    Storage tiers: Check if cool/archive tiers are used for infrequently accessed data

    line 70
  15. Very specific:

    IaC coverage: Check for ARM/Bicep/Terraform templates in connected repos

    line 73
  16. Distinctive:

    Tagging: Verify mandatory tags (environment, owner, cost-center) exist

    line 74
  17. Distinctive:

    Monitoring: Check for alert rules, action groups, and diagnostic settings

    line 78
  18. Distinctive:

    Deployment practices: Check for deployment slots, blue-green, or canary configurations

    line 83
  19. Distinctive:

    Automation: Check for runbooks, Logic Apps, or scheduled tasks for routine operations

    line 84
  20. Distinctive:

    Autoscaling: Verify autoscale rules exist for App Service plans, VMSS, and Container Apps

    line 87
  21. Distinctive:

    Caching: Check for Redis Cache or CDN usage on high-traffic workloads

    line 95
  22. Distinctive:

    Database performance: Check DTU/vCore utilization, index recommendations

    line 96
  23. Distinctive:

    Content delivery: Verify static assets use CDN or Front Door

    line 97
  24. Distinctive:

    Connection pooling: Check for connection string patterns suggesting missing pooling

    line 98
  25. Distinctive:

    If the user provides a list of accepted exceptions, do not flag those items.

    line 109
  26. Distinctive:

    When exceptions are provided:

    line 119
  27. Very specific:

    Use GetAzCliHelp to validate the command syntax before suggesting

    line 162

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

  1. 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
  2. Backup coverage: Verify Recovery Services vaults and backup policies exist for VMs, databases, and file shares
    az backup vault list -o table
    Then for each vault:
    az backup item list --vault-name <vault> --resource-group <rg> --backup-management-type AzureIaasVM -o table
  3. Disaster recovery: Check for paired regions, ASR replication, or geo-redundant storage
  4. Health probes: Verify App Service health checks, load balancer probes, and Container Apps health endpoints
  5. Auto-healing: Check if App Service auto-heal rules or AKS pod disruption budgets are configured

2. Security

  1. 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
  2. Network isolation: Check for private endpoints, NSGs, and service endpoints
    az network private-endpoint list -o table
    az network nsg list -o table
  3. Encryption: Verify encryption at rest (storage, databases) and in transit (TLS)
  4. 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
  5. Defender for Cloud: Check Secure Score and outstanding recommendations

3. Cost Optimization

  1. Rightsizing: Identify underutilized VMs (CPU < 5% average over 14 days)
  2. 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
  3. Reservations: Check if high-usage resources could benefit from reserved instances
  4. Dev/Test pricing: Verify non-production workloads use Dev/Test subscriptions or B-series VMs
  5. Storage tiers: Check if cool/archive tiers are used for infrequently accessed data

4. Operational Excellence

  1. IaC coverage: Check for ARM/Bicep/Terraform templates in connected repos
  2. Tagging: Verify mandatory tags (environment, owner, cost-center) exist
    az resource list --query "[?tags.environment==null].{name:name, type:type, rg:resourceGroup}" -o table
  3. 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
  4. Deployment practices: Check for deployment slots, blue-green, or canary configurations
  5. Automation: Check for runbooks, Logic Apps, or scheduled tasks for routine operations

5. Performance Efficiency

  1. Autoscaling: Verify autoscale rules exist for App Service plans, VMSS, and Container Apps
    az monitor autoscale list --resource-group <rg> -o table
    Note: az monitor autoscale list requires --resource-group. Iterate over relevant resource groups, or use Azure Resource Graph:
    az graph query -q "resources | where type == 'microsoft.insights/autoscalesettings'" -o table
  2. Caching: Check for Redis Cache or CDN usage on high-traffic workloads
  3. Database performance: Check DTU/vCore utilization, index recommendations
  4. Content delivery: Verify static assets use CDN or Front Door
  5. 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:

CheckReason
1.1 Availability zonesSingle-AZ by design to reduce cost
3.3 Reserved instancesShort-term workload, reservations not applicable
5.5 Connection poolingLegacy 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

FieldValue
Subscription(name + ID)
Assessment DateYYYY-MM-DD
Overall ScoreXX%

Summary

A table with pillar scores:

PillarPassNeeds AttentionFailScore
ReliabilityXYZX/(X+Y+Z) %
Security............
Cost Optimization............
Operational Excellence............
Performance Efficiency............
Overallavg %

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:

  1. The specific az CLI command to remediate (suggest only — do not execute)
  2. Use GetAzCliHelp to validate the command syntax before suggesting
  3. The official Microsoft Learn documentation link for the remediation

References

Sample output

The following is a redacted example of what the report looks like when run against a subscription.

Well-Architected Review Report

FieldValue
Subscriptioncontoso-prod-001 (a1b2c3d4-e5f6-7890-abcd-ef1234567890)
Assessment Date2026-07-15
Overall Score68%

Summary

PillarPassNeeds AttentionFailScore
Reliability31160%
Security22140%
Cost Optimization41080%
Operational Excellence31160%
Performance Efficiency40180%
Overall165468%

Detailed findings (sample)

Reliability

CheckStatusEvidencePriority
1.1 Availability zones❌ FailVMs vm-web-01, vm-web-02 in rg-app-prod have no zones configuredCritical
1.2 Backup coverage✅ PassRecovery Services vault rsv-prod-eastus protects 4/4 VMs—
1.3 Disaster recovery⚠️ Needs attentionNo ASR replication configured for rg-app-prodHigh

Security

CheckStatusEvidencePriority
2.1 Managed identity✅ PassApp Service app-api-prod uses System-Assigned MI—
2.2 Network isolation❌ FailSQL Server sql-contoso-prod has public endpoint enabledCritical
2.3 Key management⚠️ Needs attention2 secrets in kv-contoso-prod expire within 30 daysHigh

Top 5 recommendations

#RecommendationImpactEffort
1Enable availability zones on production VMsCritical2 hours
2Disable public endpoint on SQL ServerCritical30 min
3Configure ASR replication for rg-app-prodHigh4 hours
4Rotate expiring Key Vault secretsHigh1 hour
5Add autoscale rules to App Service plan asp-prodMedium30 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 2

Download now (ZIP)

Does 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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.