• "Assess my Functions app's reliability"
• "Check the reliability of my resource group" (Functions resources only)
• "Is my function app zone redundant?"
• "Make my function app zone redundant"
• "Set up multi-region failover for my Functions app"
• "Check my reliability posture"
• "Find single points of failure" (in Functions workloads)
• "Enable high availability for my Functions app"
• "Check disaster recovery readiness"
• "Improve my Functions app's resilience"

Scope note: This skill currently covers Azure Functions only. If the user asks about Azure App Service or Azure Container Apps reliability, acknowledge that support is planned but not yet available, and only proceed with the parts that apply to Functions resources in scope.

• Authentication: user is logged in to Azure via

  az login

• Permissions: Reader access on target subscription/resource group (for assessment)
• Permissions: Contributor access (for configuration changes)
• Azure Resource Graph extension:

  az extension add --name resource-graph

1. Identify scope — Ask user for resource group, subscription, or app name
2. Query Azure Resource Graph to discover all resources in scope
3. Classify resources by service type (Functions, Storage, etc.). If non-Functions compute (App Service sites that aren't Function Apps, Container Apps) is found, note it but do not deep-dive — those services are planned for a future version of this skill.

• Resource group:

  | where resourceGroup =~ '<rg-name>'

• Subscription: Use

  --subscriptions <sub-id>

  flag on

  az graph query

• App name:

  | where name =~ '<app-name>'

microsoft.web/serverfarms

kind contains 'functionapp'

microsoft.web/sites

kind contains 'functionapp'

microsoft.web/serverfarms

kind contains 'functionapp'

microsoft.app/containerapps

microsoft.app/managedenvironments

Handling unsupported services: If a resource matches an unsupported row above, surface it in the discovery summary, mark it as

⚪ not assessed (planned)

in the Phase 3 table, and skip the per-service remediation steps for it. Do not attempt to fabricate CLI commands or IaC patches for those services.

n/a

🔍 Reliability Assessment — {scope}
─────────────────────────────────────────────────────────────────────────────────────────────
Reliability Feature              Status      Resources
─────────────────────────────────────────────────────────────────────────────────────────────
Zone redundancy — compute        🔴 OFF      • plan-ii5trxva2ark4 (FC1)

Zone-redundant storage           🔴 GRS      • stii5trxva2ark4 (defaulted; no SKU set in IaC)

Health probes                    🔴 OFF      • func-api-ii5trxva2ark4 — needs code change (FC1)

Multi-region failover            🔴 OFF      • Single region (eastus) only — Front Door not configured
─────────────────────────────────────────────────────────────────────────────────────────────

Want me to fix the 🔴 items? I'll do the quick wins first (Function App
plan zone redundancy + health checks on supported plans), then ask before
storage migration and multi-region setup. (yes/no)

• Four feature rows, in this order: Zone redundancy — compute · Zone-redundant storage · Health probes · Multi-region failover. Omit a row entirely only if no resource in scope could ever apply to it.
• Status column is one symbol + one short word, no other characters:

  • 🟢 ON

    — feature is fully enabled across all relevant resources in scope

  • 🟡 PARTIAL

    — some resources have it, some don't (or partial config like liveness-only)

  • 🔴 OFF

    — feature is missing on all relevant resources
  • For storage, replace

    OFF

    with the current SKU when relevant (

    🔴 LRS

    ,

    🔴 GRS

    ,

    🟢 ZRS

    ,

    🟢 GZRS

    ). When no SKU is set in IaC, label as

    🔴 GRS

    (ARM/AVM default) and note that in the resource line.
• Resources column lists only what's relevant to that feature, one bullet per resource:
  • For "needs fixing" resources, include a short inline reason (

    (FC1)

    ,

    (defaulted; no SKU set)

    ,

    liveness only

    ,

    needs code change (FC1)

    ).
  • For resources that are already ON for that feature, mention them on the same row with

    — already ON

    so the user sees credit for what's right.
• Do not include

  n/a

  ,

  —

  , or empty cells. If a feature doesn't apply to any resource in scope, drop the row.
• Do not include numeric scores, grades, or point totals.
• End the assessment with a single yes/no question that kicks off the staged remediation flow. Do not enumerate the per-resource fix list here — the user will see it after they say yes (Configuration Workflow Step 1).

UX Note: If the assessment finds the app already has all core reliability features (zone redundancy, ZRS/GZRS storage, health probes), skip the fix-it question and jump straight to Configuration Workflow Step 3 (Multi-region follow-up). Do NOT start any multi-region work without explicit consent.

⛔ ALWAYS confirm with user before executing changes. Show what will change, any cost implications, and any destructive actions (e.g., environment recreation).

1. List each fixable finding with the specific action
2. Flag any cost implications or breaking changes
3. Ask user which path they want:

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

az

1. Zone redundancy on compute (fast, in-place property update on the Function App's plan).
2. Health probes (Premium / Dedicated only — in-place; for FC1 / Consumption, follow the consent gate in configure-health-probes.md).
3. Verify the compute changes succeeded before doing anything else.
4. ⛔ STOP — Ask about storage upgrade. Compute is now zone-redundant, but storage may still be LRS or GRS. Ask the user explicitly:

   ✅ Compute is now zone-redundant.
   
   To be **fully zone-redundant**, your storage account also needs to be upgraded:
     • stii5trxva2ark4: currently `Standard_LRS` → needs `Standard_ZRS`
   
   ⚠️  This is a live storage redundancy conversion:
      • Takes hours to days depending on data volume
      • Small ongoing cost increase (~$0.01/GB/month more)
      • Only supported for Standard general-purpose v2 accounts
   
   Do you want me to start the storage migration now? (yes / no / later)

   • yes → run

     az storage account update --sku Standard_ZRS

     (or

     migration start

     if needed); poll

     az storage account show --query sku.name

     until it reports

     Standard_ZRS

     .
   • no / later → leave storage as-is; note in the re-assessment that ZR storage remains a gap.
5. Multi-region — do NOT auto-run. Handled in Step 3 below as an explicit follow-up after re-assessment.

⚠️ Warning: If the user uses

azd up

or

terraform apply

later, CLI-only changes may be overwritten by the IaC definitions. Recommend also patching IaC after CLI fixes.

1. Look for

   infra/

   folder in project root
2. If not found, check project root for

   *.bicep

   or

   *.tf

   files
3. If still not found, ask user: "Where are your IaC files located?"
4. Check for

   *.bicep

   files → use Bicep patching
5. Check for

   *.tf

   files → use Terraform patching
6. If both exist, ask user which to patch
7. If no IaC exists, fall back to Path A (CLI) and inform user

healthCheckPath

/api/health

📦 Patches applied to your IaC. Ready to deploy:
   Tool detected: azd (found azure.yaml)
   Command:       azd up

Proceed with deployment? (yes / no)

• AZD project (has

  azure.yaml

  ):

  azd up

• Bicep-only:

  az deployment group create --resource-group <rg> --template-file infra/main.bicep --parameters @infra/main.parameters.json

• Terraform:

  terraform plan -out tfplan

  → (show plan summary) →

  terraform apply tfplan

✅ Quick-win patches deployed. Compute is now zone-redundant.

To be **fully zone-redundant**, your storage account also needs to be upgraded:
  • stii5trxva2ark4: currently `Standard_LRS` → needs `Standard_ZRS`

⚠️  This is a two-part change:
   1. Live storage migration (`az storage account migration start`) — takes hours to days
   2. A second deploy to update your IaC's storage SKU to match

Do you want me to start the storage migration now? (yes / no / later)

• yes → the skill runs the migration command itself, polls until complete, then patches the storage SKU in IaC and runs Deploy 2 (now a no-op confirmation). The user does not need to run anything manually.
• no / later → leave the storage SKU patch unapplied. Note in the re-assessment that ZR storage remains a gap; suggest revisiting later.

🔄 Starting storage migration (this can take up to 72 hours)...

   az storage account migration start --name stii5trxva2ark4 \
     --resource-group rg-example --sku Standard_ZRS --no-wait

   Polling: az storage account show --name stii5trxva2ark4 --query sku.name
   ...
   ✅ Migration complete: sku.name = Standard_ZRS

azd up

🟢 Your app is now fully zone-redundant in {region}.

The next step (optional) is multi-region failover with Azure Front Door:
   • Deploys compute + storage in a second region (paired region recommended)
   • Adds Azure Front Door for global load balancing with health-probe-driven failover
   • Protects against full region outages
   • Estimated additional cost: ~2x compute (active-passive); Front Door ~$35/month base

Do you want me to set up multi-region failover now? (yes / no / later)

• yes → proceed with references/configure-multi-region.md. Confirm secondary region choice with the user, then:
  1. Generate the multi-region IaC (Bicep / Terraform additions for the secondary region + Front Door).
  2. Confirm once with the user:

     📦 Multi-region IaC generated. Ready to deploy with \

     azd up`. Proceed? (yes / no)`
  3. On yes, the skill runs the deploy itself (

     azd up

     /

     az deployment group create

     /

     terraform apply

     ) and streams output. Do not stop and tell the user to run it.
  4. After successful deploy, run a final re-assessment so the user sees Multi-region failover flip to 🟢 ON.
• no / later → leave the deployment as-is. Note that single-region zone-redundant is a reliable end state; multi-region can be revisited anytime.

⛔ Do not skip the wait. Do not generate multi-region IaC, deploy a Front Door, or modify any files until the user has explicitly said yes. If core reliability is not yet all 🟢, do not ask about multi-region — finish the core gaps first.

• Run reliability assessments after every significant infrastructure change
• Test failover scenarios periodically (at least quarterly)