AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

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".

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read microsoft--azure-reliability at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 13

references/configure-health-probes.md

Configure Health Probes — Platform Notes

What "health probe" means per service

| Service | Mechanism | Where | |---|---|---| | App Service (Basic / Standard / Premium / Dedicated) | siteConfig.healthCheckPath (platform health check) | services/app-service/reliability.md | | Functions Premium / Dedicated | siteConfig.healthCheckPath (platform health check) | services/functions/reliability.md | | Functions Flex Consumption (FC1) / Consumption (Y1) | HTTP-triggered /api/health function in app code — healthCheckPath is unsupported | services/functions/reliability.md | | Azure Front Door | healthProbeSettings on origin group | health-probe-checks.md | | Traffic Manager | monitorConfig on profile | health-probe-checks.md |

Container Apps (liveness / readiness probes) deep-dive references are planned for a future version of this skill but are not yet shipped.

⛔ STOP — Code-only fixes require user consent

For any case where enabling health probing requires modifying app source code rather than IaC — most notably Functions on FC1 / Y1, and Container Apps where the image doesn't already serve a /health route — always ask the user for explicit consent before touching source files. The exact prompt and decision tree are documented in the relevant per-service reference.

Do not generate or modify code without an explicit yes.

Best Practices for Health Endpoints

These apply to any service:

  1. Keep health endpoints lightweight — return 200 quickly; don't run heavy DB or downstream-dependency queries on every probe.
  2. Use anonymous auth — platform health probes can't pass auth tokens.
  3. Two endpoints, not one — a fast /health for the load balancer, and an optional /health/deep for on-call diagnostics.
  4. For Container Apps, both liveness AND readiness — liveness alone restarts the container without taking it out of rotation first.
  5. Test the endpoint before relying on it: curl https://<app-url>/api/health.