Skip to content
DevOps AI ToolKit
Newsletter
All prompts
Azure with AI Difficulty: Advanced ClaudeChatGPTCursor

VM Scale Set Autoscale & Orchestration Review Prompt

Review an Azure Virtual Machine Scale Set for scaling correctness and resilience by analyzing autoscale rules, orchestration mode, upgrade policy, health probes, and zone balancing to stop flapping, slow scale-out, and unsafe instance replacement.

Target user
Cloud infrastructure engineers and SREs
Difficulty
Advanced
Tools
Claude, ChatGPT, Cursor

The prompt

You are a senior Azure compute engineer who reviews Virtual Machine Scale Sets for scaling behavior and rollout safety.

I will provide:
- VMSS config: `az vmss show -g <rg> -n <vmss> -o json` (orchestrationMode Uniform/Flexible, upgradePolicy, singlePlacementGroup, zones, sku capacity)
- Autoscale settings: `az monitor autoscale show` / `az monitor autoscale rule list` (metric, operator, threshold, scale action, cooldown)
- Health: application health extension / load balancer health probe config and instance health states
- Metric history for the driving signal (CPU, queue depth, custom metric) over a representative window
- The symptom: too-slow scale-out, flapping in/out, uneven zone distribution, or instances cycling during upgrades

Your job:

1. **Diagnose the scaling symptom** — connect it to a concrete cause: threshold too high/low, cooldown too short (flapping) or too long (slow), a lagging metric, or min/max bounds pinning capacity.
2. **Review scale rules** — check that scale-out and scale-in thresholds have adequate separation (hysteresis), that the aggregation window suits the metric, and that scale-in is conservative.
3. **Assess orchestration and upgrade policy** — evaluate Uniform vs Flexible fit, and whether Automatic/Rolling upgrade policy with a health probe is safe or will replace unhealthy-looking-but-fine instances.
4. **Check resilience** — zone balancing, overprovisioning, and whether the health probe accurately reflects app readiness so autoheal doesn't churn good instances.
5. **Recommend tuning** — specific thresholds, cooldowns, bounds, and upgrade/health settings — each as advisory steps with the read-only command to confirm current state first.

Output as: (a) symptom diagnosis, (b) scale-rule review with hysteresis/cooldown findings, (c) orchestration/upgrade assessment, (d) resilience review, (e) tuning recommendations with confirming read-only commands.

Stay read-only: do not change capacity, autoscale rules, or trigger upgrades — produce findings for an operator to apply under change control.

Run this prompt with AI

Test it, get an AI-improved version, or compare models — live in the Prompt Workspace. No copy-paste.

Related prompts

More Azure with AI prompts & error guides

Browse every Azure with AI prompt and troubleshooting guide in one place.

Free download · 368-page PDF

Reading prompts? Get all 500 in one free PDF

500 battle-tested, copy-paste AI prompts engineered by a senior systems engineer — every one with fill-in placeholders and safety/back-out notes. Drop your email and it's yours.

  • 500 prompts: Linux · Kubernetes · Terraform · OpenStack · GitLab · Docker · Monitoring · Incident Response
  • Instant PDF download — yours free, forever
  • Plus one practical AI-workflow email a week (no spam)

Single opt-in · unsubscribe anytime · no spam.