azure-reliability
Assess and improve the reliability posture of PaaS Applications (Azure Functions and Azure App Service). Scans deployed resources for zone redundancy, ZRS storage, health probes, and multi-region failover. Presents a feature-pivoted checklist, then drives staged remediation (CLI or IaC patches) end-to-end with user confirmation. WHEN: \"assess reliability\", \"check reliability\", \"zone redundant\", \"multi-region failover\", \"high availability\", \"disaster recovery\", \"single points of failure\", \"reliability posture\", \"resiliency\".
Profile →npx skills add microsoft/azure-skills --skill azure-reliability --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Assesses the reliability posture of Azure Functions and App Service resources, identifies zone redundancy, storage redundancy, health probes, and multi-region failover gaps, presents a feature-pivoted checklist, and guides staged remediation end-to-end with user confirmation. It supports generating CLI or IaC patches and requires user confirmation before making changes.
How it works
- Phase 1: Discover Resources by querying the specified resource group/subscription or app name using Azure Resource Graph and filters for the given scope.
- Phase 2: Assess Reliability with a two-step deep dive: (1) platform discovery to detect gaps (zone redundancy, storage redundancy, multi-region/load balancers, health probes) and (2) per-service deep dive loading service references for Functions or App Service to obtain plan rules, queries, CLI commands, and IaC patches.
- Phase 3: Generate Reliability Checklist as a feature-pivoted table with four rows: Zone redundancy — compute; Zone-redundant storage; Health probes; Multi-region failover. Each row lists relevant resources and status per feature, with specific resource details and inline reasons where applicable. Ends with a yes/no remediation prompt.
- Configuration Workflow: If user asks to fix, presents a plan with quick wins first, then asks to choose between Fix Now (CLI) or Patch IaC. Includes steps for enabling zone redundancy and health probes, followed by a separate storage upgrade and multi-region follow-up. All changes require explicit user consent before execution.
When to use it
Use when the user wants to assess reliability, check reliability, verify zone redundancy, set up multi-region failover, assess disaster recovery readiness, or improve resiliency for Azure Functions and App Service resources. Note: Azure Container Apps support is planned for a future version; if encountered, surface it as planned and skip per-service remediation for that resource.
What it can touch
- Interfaces with Azure via MCP tools and Azure CLI commands, including
az graph query,az extension add --name resource-graph, and per-service references for functions/app-service repairs. The exact per-service CLI commands and IaC patches are loaded from the service references corresponding to discovered resources.
Caveats
- Requires user to be logged in to Azure (
az login) and hold Reader access for assessment and Contributor access for configuration. - Some fixes may require storage migrations (e.g., LRS to ZRS) and could incur costs or downtime; user confirmation is required before any destructive or costly action.
- If non-supported services are discovered (e.g., Container Apps), they are surfaced as not assessed (planned) and skipped for remediation.
# Azure Reliability Assessment & Configuration ## Quick Reference | Property | Details | |---|---| | Best for | Reliability posture assessment, zone redundancy enablement, multi-region failover setup | | Primary capabilities | Reliability assessment table, Zone Redundancy Configuration, Multi-Region IaC Generation | | Supported services | Azure Functions, App Service (Container Apps planned for a future version) | | MCP tools | Azure Resource Graph queries, Azure CLI commands | ## When to Use This Skill Activate this skill when user wants to: - "Assess my Function app's reliability" - "Assess my Web app's reliability" - "Check the reliability of my resource group" (App Service and Functions resources only) - "Is my app zone redundant?" (App Service and Functions resources only) - "Is my app service plan zone redundant?" - "Make my app zone redundant" (App Service and Functions resources only) - "Make my app service plan zone redundant" - "Set up multi-region failover for my app" (App Service and Functions resources only) - "Check my reliability posture" - "Find single points of failure" (App Service and Functions resources only) - "Enable high availability for my app" (App Service
- Quick Reference
- When to Use This Skill
- Prerequisites
- MCP Tools
- Assessment Workflow
- Phase 1: Discover Resources
- Phase 2: Assess Reliability
- Phase 3: Generate Reliability Checklist
- Configuration Workflow
- Step 1: Present Fix Plan + Choose Path
- Path A: Fix Now (CLI)
- Path B: Patch IaC
- Step 2 (both paths): Re-Assess
- Step 3 (both paths): Multi-region follow-up — ASK and WAIT
What does the azure-reliability skill do?
Assess and improve the reliability posture of PaaS Applications (Azure Functions and Azure App Service). Scans deployed resources for zone redundancy, ZRS storage, health probes, and multi-region failover. Presents a feature-pivoted checklist, then drives staged remediation (CLI or IaC patches) end-to-end with user confirmation. WHEN: \"assess reliability\", \"check reliability\", \"zone redundant\", \"multi-region failover\", \"high availability\", \"disaster recovery\", \"single points of failure\", \"reliability posture\", \"resiliency\".
How do I install it?
Run `npx skills add microsoft/azure-skills --skill azure-reliability --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From microsoft/azure-skills, a repository with 1,353 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.