Localized reading guide
azure-reliabilityPurpose, usage and source
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".
Source retrieved:
- Source repository
- microsoft/skills
- SKILL.md
.github/plugins/azure-skills/skills/azure-reliability/SKILL.md- Repository stars
- 3,157
- Repository updated
- 2026-10-31
- Categories
- Cloud
- Last collected
License: License file needs review
Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.
The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.
What this Skill does
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 the upstream workflow works
Configuration Workflow
When user wants to fix findings from the assessment: > ⛔ ALWAYS confirm with user before executing changes. Show what will change, any cost implications, and any destructive actions (e.g., environment recreation).
Upstream passage · L137 ↗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)
Upstream passage · L21 ↗Step 1: Present Fix Plan + Choose Path
After assessment, if user says "fix it" / "improve my reliability" / "enable zone redundancy": List each fixable finding with the specific action Flag any cost implications or breaking changes Ask user which path they want:
Upstream passage · L143 ↗I'll start with the quick wins (no downtime, fast):
1. ✏️ Enable zone redundancy on plan-ii5trxva2ark4 (Flex Consumption — no cost change)
2. ✏️ Set health check path to /api/health on func-api-ii5trxva2ark4
Then, separately, I'll ask if you want to upgrade storage:
3. 🕒 Upgrade stii5trxva2ark4 from LRS → ZRS (small cost increase, migration takes hours)
— Required for full zone redundancy, but I'll confirm with you before starting.
How would you like to apply these changes?
A) Fix now — Run az CLI commands against your live resources (immediate, one-time)
B) Patch my IaC — Update your Bicep/Terraform files so changes persist across deploys
(If you use azd or Terraform, option B is recommended so `azd up` won't overwrite changes.)Requirements and setup
Prerequisites
Authentication: user is logged in to Azure via az login Permissions: Reader access on target subscription/resource group (for assessment)
Limits and quality checks
No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.
Start with a safe trial
- Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
- Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
- Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
- Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.
Read further in the source
- When to Use This Skill
- Prerequisites
- MCP Tools
- 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
- Best Practices
Related Skills
Translation and scope
This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.
This introduction refers to the pinned version below; current repository activity and collection time are shown separately.
- Pinned source
- Read the original ↗
- Source retrieved
- Source commit
00d66a64919edca5bca2c673373444e36a4b5461- Source SHA-256
a70f0a799c8f3cf805ada741e82af31a149b57cb1e2388d7805036492cdceb71