Robertjam954/multimodal_rag_application / .claude/skills/azure-reliability
azure-reliability
UnverifiedAssess 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".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 24.5 KB |
| references/configure-health-probes.md | markdown | 2.1 KB |
| references/configure-multi-region.md | markdown | 18.5 KB |
| references/configure-storage.md | markdown | 5.4 KB |
| references/configure-zone-redundancy.md | markdown | 1.9 KB |
| references/health-probe-checks.md | markdown | 3.5 KB |
| references/iac-patching-bicep.md | markdown | 6.9 KB |
| references/iac-patching-terraform.md | markdown | 4.7 KB |
| references/multi-region-checks.md | markdown | 6.0 KB |
| references/services/app-service/reliability.md | markdown | 10.2 KB |
| references/services/functions/reliability.md | markdown | 6.2 KB |
| references/storage-redundancy-checks.md | markdown | 5.1 KB |
| references/zone-redundancy-checks.md | markdown | 2.9 KB |
references/configure-storage.md
View on GitHub# Configure Storage Redundancy
## Overview
Storage accounts must match or exceed the redundancy level of the compute they support. Zone-redundant compute requires at minimum ZRS storage.
## Upgrade Paths
| Current | Target | Method | Downtime |
|---|---|---|---|
| Standard_LRS → Standard_ZRS | ZRS | Live migration or manual | None (live) or planned (manual) |
| Standard_LRS → Standard_GRS | GRS | In-place update | None |
| Standard_LRS → Standard_GZRS | GZRS | In-place update | None |
| Premium_LRS → Premium_ZRS | ZRS | Manual migration only | Planned |
## In-Place Upgrade (LRS → GRS/GZRS)
GRS and GZRS upgrades can be done in-place immediately:
```bash
# Upgrade to GZRS (zone + region redundant — recommended)
az storage account update \
--name <account-name> \
--resource-group <rg> \
--sku Standard_GZRS
# Upgrade to GRS (region redundant only — NOT zone redundant)
az storage account update \
--name <account-name> \
--resource-group <rg> \
--sku Standard_GRS
```
## Live Migration (LRS → ZRS)
ZRS conversion uses the storage account migration API (not `--sku` update):
```bash
# Check if account supports live migration
# Requirements: Standard general-purpose v2, in a supported region
az storage account show \
--name <account-name> \
--resource-group <rg> \
--query "{name:name, sku:sku.name, kind:kind}"
# Start live migration to ZRS
az storage account migration start \
--account-name <account-name> \
-g <rg> \
--sku Standard_ZRS \
--name default \
--no-wait
# Monitor migration status (can take hours to days)
az storage account migration show \
--account-name <account-name> \
-g <rg> \
--migration-name default \
--query "migrationStatus"
```
> **⛔ HARD GATE: Do NOT proceed to enable zone-redundant compute until migration status is `Succeeded` and `az storage account show --query sku.name` returns `Standard_ZRS`.**
⚠️ **Live migration limitations:**
- Only supported for **Standard general-purpose v2** accounts
- Premium storage accounts require manual migration
- BlobStorage and Storage (classic) kinds require manual migration
- Migration can take hours to days depending on data volume
- Account remains accessible during migration
## Manual Migration (When Live Migration Not Available)
For Premium_LRS or unsupported account types:
```bash
# 1. Create new ZRS storage account
az storage account create \
--name <new-account-name> \
--resource-group <rg> \
--location <location> \
--sku Standard_ZRS \
--kind StorageV2
```
### For Function Apps (special handling required)
Function App host storage uses blobs, queues, tables, and potentially files. A simple blob-only copy is NOT sufficient.
**⛔ Full Function App storage migration workflow:**
```bash
# 1. Stop the function app to quiesce triggers and drain orchestrations
az functionapp stop --name <app-name> --resource-group <rg>
# 2. If using Durable Functions, wait for all orchestrations to complete
# or terminate them before proceeding
# 3. Copy ALL storage services (blobs, queues, tables) using AzCopy
# Authenticate first:
azcopy login
# Copy blobs:
azcopy copy \
"https://<old-account>.blob.core.windows.net/*" \
"https://<new-account>.blob.core.windows.net/" \
--recursive
# Note: AzCopy does not support table/queue copy directly.
# Use Azure Data Factory or Storage Explorer for tables/queues if needed.
# 4. Get new storage connection string
az storage account show-connection-string \
--name <new-account-name> \
--resource-group <rg> \
--query connectionString -o tsv
# 5. Update app settings to point to new storage
az functionapp config appsettings set \
--name <app-name> \
--resource-group <rg> \
--settings "AzureWebJobsStorage=<new-connection-string>"
# 6. Start the function app
az functionapp start --name <app-name> --resource-group <rg>
# 7. Verify app works — check logs, test triggers
az functionapp show --name <app-name> --resource-group <rg> --query "state"
# 8. Only delete old storage after confirming everything works
```
⚠️ **Warn user:** This involves app downtime. For zero-downtime migration, use live migration (Standard_ZRS) instead.
### For non-Function App workloads (simpler)
```bash
# Copy blobs
azcopy login
azcopy copy \
"https://<old-account>.blob.core.windows.net/*" \
"https://<new-account>.blob.core.windows.net/" \
--recursive
# Update app connection strings as needed
# Delete old account after verification
```
## Function App Storage Considerations
Function Apps have a host storage account used for:
- Function code storage
- Timer trigger leases
- Event Hub checkpoints
- Durable Functions state
**Critical:** When upgrading Function App storage:
- The `AzureWebJobsStorage` connection string must point to the upgraded/new account
- If using a separate deployment storage account, upgrade that too
- Durable Functions state is stored in the host storage — ensure no active orchestrations during manual migration
```bash
# Check current storage connection
az functionapp config appsettings list \
--name <app-name> \
--resource-group <rg> \
--query "[?name=='AzureWebJobsStorage'].value" -o tsv
```
## Verification
```bash
az graph query -q "
Resources
| where resourceGroup =~ '<rg>'
| where type =~ 'microsoft.storage/storageaccounts'
| project name, replication=sku.name, kind
" -o table
```
Expected: All accounts show `Standard_ZRS`, `Standard_GZRS`, or `Premium_ZRS`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |