# Assess and Improve Azure Application Reliability

Azure application reliability gaps can remain hidden until a zone or region fails. This skill assesses key controls and guides confirmed Azure CLI or IaC remediation.

## Install

```bash
npx skillstore add microsoft/azure-reliability
```

## Metadata

- Status: approved
- Slug: microsoft-azure-reliability
- Version: 1.0.2
- Author version: 1.0.2
- Skillstore revision: r2
- Version status: valid
- Tree hash: e2ff6bc044ebdd24405d1823028410917515d8b933d344e8270f575917e8010c
- Author: microsoft
- GitHub username: microsoft
- License: MIT
- Repository: https://github.com/microsoft/azure-skills/tree/main/.github/plugins/azure-skills/skills/azure-reliability/
- Ref: ebdfe608f5de2b66ff37ab4af12af8ac4f5e8006
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, filesystem, scripts
- Quality score: 79
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/microsoft-azure-reliability
- Manifest: https://skillstore.pages.dev/api/skills/microsoft-azure-reliability/manifest

## Capabilities

- Discovers Azure Functions and App Service resources within a selected resource group or subscription.
- Checks compute zone redundancy, storage replication, health probes, and multi-region failover.
- Presents a feature-based reliability table with affected resources and status.
- Applies confirmed Azure CLI changes and verifies the resulting resource state.
- Patches existing Bicep or Terraform files and guides staged deployments.
- Generates confirmed secondary-region and Azure Front Door infrastructure for supported applications.

## Use Cases

- Audit production reliability: Assess zone, storage, probe, and regional resilience before an operational review.
- Plan resilient architecture: Identify single-region dependencies and prepare an Azure Front Door failover design.
- Persist reliability fixes: Patch Bicep or Terraform settings so reliability changes remain after deployment.

## Prompt Templates

### Run a basic assessment

```
Assess reliability for Azure resources in [scope]. Show the feature table and explain each gap. Do not make changes.
```

### Review one application

```
Assess my [Function App or App Service] in [resource group]. Recommend quick wins, costs, and consent gates. Ask before running any command.
```

### Patch existing infrastructure

```
Patch reliability gaps in my [Bicep or Terraform] project. Show proposed file changes and the deployment plan. Wait for confirmation before deployment.
```

### Design regional failover

```
Design multi-region failover for [application] using Azure Front Door and [secondary region]. Include health probes, storage replication, costs, validation, and staged deployment.
```

## Limitations

- Supports Azure Functions and App Service only; Azure Container Apps are not assessed.
- Requires Azure authentication and Reader access for assessment.
- Configuration changes require Contributor access and explicit user approval.
- Provides reliability checks, not complete security, compliance, or deployment validation.

## Best Practices

- Start with read-only assessment and define the exact subscription or resource group scope.
- Review cost, downtime, and replacement risks before approving any configuration change.
- Reassess after each deployment and test regional failover on a planned schedule.

## Anti Patterns

- Do not run broad Azure queries without a user-defined scope.
- Do not combine slow storage migration with quick compute changes in one deployment.
- Do not start multi-region deployment before explicit approval and core reliability checks.

## Security Audit

- Audited at: 2026-07-23T19:19:15.274\+00:00
- Summary: All 100 static findings are false positives caused by Markdown formatting, relative links, IaC identifiers, Azure endpoint examples, and a C\# attribute. The skill intentionally runs Azure CLI and IaC deployments, with scoped operations and explicit confirmation before changes. No prompt injection, credential exfiltration, or malicious intent was found.

## Stats

- Views: 0
- Downloads: 6
- Favorites: 0
- Popularity score: 0