Azure Compute Skill
Recommend Azure VM sizes, VM Scale Sets (VMSS), and configurations by analyzing workload type, performance requirements, scaling needs, and budget. No Azure subscription required — all data comes from public Microsoft documentation and the unauthenticated Retail Prices API.
When to Use This Skill
- User asks which Azure VM or VMSS to choose for a workload
- User needs VM size recommendations for web, database, ML, batch, HPC, or other workloads
- User wants to compare VM families, sizes, or pricing tiers
- User asks about trade-offs between VM options (cost vs performance)
- User needs a cost estimate for Azure VMs without an Azure account
- User asks whether to use a single VM or a scale set
- User needs autoscaling, high availability, or load-balanced VM recommendations
- User asks about VMSS orchestration modes (Flexible vs Uniform)
Workflow
Use reference files for initial filtering
CRITICAL: then always verify with live documentation from learn.microsoft.com before making final recommendations. If web_fetch fails, use reference files as fallback but warn the user the information may be stale.
Step 1: Gather Requirements
Ask the user for (infer when possible):
| Requirement |
Examples |
| Workload type |
Web server, relational DB, ML training, batch processing, dev/test |
| vCPU / RAM needs |
"4 cores, 16 GB RAM" or "lightweight" / "heavy" |
| GPU needed? |
Yes → GPU families; No → general/compute/memory |
| Storage needs |
High IOPS, large temp disk, premium SSD |
| Budget priority |
Cost-sensitive, performance-first, balanced |
| OS |
Linux or Windows (affects pricing) |
| Region |
Affects availability and price |
| Instance count |
Single instance, fixed count, or variable/dynamic |
| Scaling needs |
None, manual scaling, autoscale based on metrics or schedule |
| Availability needs |
Best-effort, fault-domain isolation, cross-zone HA |
| Load balancing |
Not needed, Azure Load Balancer (L4), Application Gateway (L7) |
Step 2: Determine VM vs VMSS
Workflow:
- Review VMSS Guide to understand when VMSS vs single VM is appropriate
- Use the gathered requirements to decide which approach fits best
- REQUIRED: If recommending VMSS, fetch current documentation to verify capabilities:
web_fetch https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/overview
web_fetch https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-autoscale-overview
- If
web_fetch fails, proceed with reference file guidance but include this warning:
Unable to verify against latest Azure documentation. Recommendation based on reference material that may not reflect recent updates.
Needs autoscaling?
├─ Yes → VMSS
├─ No
│ ├─ Multiple identical instances needed?
│ │ ├─ Yes → VMSS
│ │ └─ No
│ │ ├─ High availability across fault domains / zones?
│ │ │ ├─ Yes, many instances → VMSS
│ │ │ └─ Yes, 1-2 instances → VM + Availability Zone
│ │ └─ Single instance sufficient? → VM
| Signal |
Recommendation |
Why |
| Autoscale on CPU, memory, or schedule |
VMSS |
Built-in autoscale; no custom automation needed |
| Stateless web/API tier behind a load balancer |
VMSS |
Homogeneous fleet with automatic distribution |
| Batch / parallel processing across many nodes |
VMSS |
Scale out on demand, scale to zero when idle |
| Mixed VM sizes in one group |
VMSS (Flexible) |
Flexible orchestration supports mixed SKUs |
| Single long-lived server (jumpbox, AD DC) |
VM |
No scaling benefit; simpler management |
| Unique per-instance config required |
VM |
Scale sets assume homogeneous configuration |
| Stateful workload, tightly-coupled cluster |
VM (or VMSS case-by-case) |
Evaluate carefully; VMSS Flexible can work for some stateful patterns |
Warning: If the user is unsure, default to single VM for simplicity. Recommend VMSS only when scaling, HA, or fleet management is clearly needed.
Step 3: Select VM Family
Workflow:
Review VM Family Guide to identify 2-3 candidate VM families that match the workload requirements
REQUIRED: verify specifications for your chosen candidates by fetching current documentation:
web_fetch https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/<family-category>/<series-name>
Examples:
- B-series:
https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/general-purpose/b-family
- D-series:
https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/general-purpose/ddsv5-series
- GPU:
https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/gpu-accelerated/nc-family
If considering Spot VMs, also fetch:
web_fetch https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/use-spot
If web_fetch fails, proceed with reference file guidance but include this warning:
Unable to verify against latest Azure documentation. Recommendation based on reference material that may not reflect recent updates or limitations (e.g., Spot VM compatibility).
This step applies to both single VMs and VMSS since scale sets use the same VM SKUs.
Step 4: Look Up Pricing
Query the Azure Retail Prices API — Retail Prices API Guide
Tip: VMSS has no extra charge — pricing is per-VM instance. Use the same VM pricing from the API and multiply by the expected instance count to estimate VMSS cost. For autoscaling workloads, estimate cost at both the minimum and maximum instance count.
Step 5: Present Recommendations
Provide 2–3 options with trade-offs:
| Column |
Purpose |
| Hosting Model |
VM or VMSS (with orchestration mode if VMSS) |
| VM Size |
ARM SKU name (e.g., Standard_D4s_v5) |
| vCPUs / RAM |
Core specs |
| Instance Count |
1 for VM; min–max range for VMSS with autoscale |
| Estimated $/hr |
Per-instance pay-as-you-go from API |
| Why |
Fit for the workload |
| Trade-off |
What the user gives up |
Tip: Always explain why a family fits and what the user trades off (cost vs cores, burstable vs dedicated, single VM simplicity vs VMSS scalability, etc.).
For VMSS recommendations, also mention:
- Recommended orchestration mode (Flexible for most new workloads)
- Autoscale strategy (metric-based, schedule-based, or both)
- Load balancer type (Azure Load Balancer for L4, Application Gateway for L7/TLS)
Step 6: Offer Next Steps
Error Handling
| Scenario |
Action |
| API returns empty results |
Broaden filters — check armRegionName, serviceName, armSkuName spelling |
| User unsure of workload type |
Ask clarifying questions; default to General Purpose D-series |
| Region not specified |
Use eastus as default; note prices vary by region |
| Unclear if VM or VMSS needed |
Ask about scaling and instance count; default to single VM if unsure |
| User asks VMSS pricing directly |
Use same VM pricing API — VMSS has no extra charge; multiply by instance count |
References
- VM Family Guide — Family-to-workload mapping and selection
- Retail Prices API Guide — Query patterns, filters, and examples
- VMSS Guide — When to use VMSS, orchestration modes, and autoscale patterns
1---2name: azure-compute3description: Recommend Azure VM sizes, VM Scale Sets (VMSS), and configurations based on workload requirements, performance needs, and budget constraints. No Azure account required — uses public documentation and the Azure Retail Prices API. WHEN: recommend VM size, which VM should I use, choose Azure VM, VM ...4license: MIT5---6# Azure Compute Skill
7
8Recommend Azure VM sizes, VM Scale Sets (VMSS), and configurations by analyzing workload type, performance requirements, scaling needs, and budget. No Azure subscription required — all data comes from public Microsoft documentation and the unauthenticated Retail Prices API.
9
10## When to Use This Skill
11
12- User asks which Azure VM or VMSS to choose for a workload
13- User needs VM size recommendations for web, database, ML, batch, HPC, or other workloads
14- User wants to compare VM families, sizes, or pricing tiers
15- User asks about trade-offs between VM options (cost vs performance)
16- User needs a cost estimate for Azure VMs without an Azure account
17- User asks whether to use a single VM or a scale set
18- User needs autoscaling, high availability, or load-balanced VM recommendations
19- User asks about VMSS orchestration modes (Flexible vs Uniform)
20
21## Workflow
22
23> Use reference files for initial filtering
24
25> **CRITICAL: then always verify with live documentation** from learn.microsoft.com before making final recommendations. If `web_fetch` fails, use reference files as fallback but warn the user the information may be stale.
26
27### Step 1: Gather Requirements
28
29Ask the user for (infer when possible):
30
31| Requirement | Examples |
32| ---------------------- | ------------------------------------------------------------------ |
33| **Workload type** | Web server, relational DB, ML training, batch processing, dev/test |
34| **vCPU / RAM needs** | "4 cores, 16 GB RAM" or "lightweight" / "heavy" |
35| **GPU needed?** | Yes → GPU families; No → general/compute/memory |
36| **Storage needs** | High IOPS, large temp disk, premium SSD |
37| **Budget priority** | Cost-sensitive, performance-first, balanced |
38| **OS** | Linux or Windows (affects pricing) |
39| **Region** | Affects availability and price |
40| **Instance count** | Single instance, fixed count, or variable/dynamic |
41| **Scaling needs** | None, manual scaling, autoscale based on metrics or schedule |
42| **Availability needs** | Best-effort, fault-domain isolation, cross-zone HA |
43| **Load balancing** | Not needed, Azure Load Balancer (L4), Application Gateway (L7) |
44
45### Step 2: Determine VM vs VMSS
46
47**Workflow:**
48
491. Review [VMSS Guide](references/vmss-guide.md) to understand when VMSS vs single VM is appropriate
502. Use the gathered requirements to decide which approach fits best
513. **REQUIRED: If recommending VMSS**, fetch current documentation to verify capabilities:
52 ```bash
53 web_fetch https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/overview
54 web_fetch https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-autoscale-overview
55 ```
564. **If `web_fetch` fails**, proceed with reference file guidance but include this warning:
57 > Unable to verify against latest Azure documentation. Recommendation based on reference material that may not reflect recent updates.
58
59```text
60Needs autoscaling?
61├─ Yes → VMSS
62├─ No
63│ ├─ Multiple identical instances needed?
64│ │ ├─ Yes → VMSS
65│ │ └─ No
66│ │ ├─ High availability across fault domains / zones?
67│ │ │ ├─ Yes, many instances → VMSS
68│ │ │ └─ Yes, 1-2 instances → VM + Availability Zone
69│ │ └─ Single instance sufficient? → VM
70```
71
72| Signal | Recommendation | Why |
73| --------------------------------------------- | ----------------------------- | --------------------------------------------------------------------- |
74| Autoscale on CPU, memory, or schedule | **VMSS** | Built-in autoscale; no custom automation needed |
75| Stateless web/API tier behind a load balancer | **VMSS** | Homogeneous fleet with automatic distribution |
76| Batch / parallel processing across many nodes | **VMSS** | Scale out on demand, scale to zero when idle |
77| Mixed VM sizes in one group | **VMSS (Flexible)** | Flexible orchestration supports mixed SKUs |
78| Single long-lived server (jumpbox, AD DC) | **VM** | No scaling benefit; simpler management |
79| Unique per-instance config required | **VM** | Scale sets assume homogeneous configuration |
80| Stateful workload, tightly-coupled cluster | **VM** (or VMSS case-by-case) | Evaluate carefully; VMSS Flexible can work for some stateful patterns |
81
82> **Warning:** If the user is unsure, default to **single VM** for simplicity. Recommend VMSS only when scaling, HA, or fleet management is clearly needed.
83
84### Step 3: Select VM Family
85
86**Workflow:**
87
881. Review [VM Family Guide](references/vm-families.md) to identify 2-3 candidate VM families that match the workload requirements
892. **REQUIRED: verify specifications** for your chosen candidates by fetching current documentation:
90 ```bash
91 web_fetch https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/<family-category>/<series-name>
92 ```
93
94 Examples:
95 - B-series: `https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/general-purpose/b-family`
96 - D-series: `https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/general-purpose/ddsv5-series`
97 - GPU: `https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/gpu-accelerated/nc-family`
98
993. **If considering Spot VMs**, also fetch:
100 ```bash
101 web_fetch https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/use-spot
102 ```
103
1044. **If `web_fetch` fails**, proceed with reference file guidance but include this warning:
105 > Unable to verify against latest Azure documentation. Recommendation based on reference material that may not reflect recent updates or limitations (e.g., Spot VM compatibility).
106
107This step applies to both single VMs and VMSS since scale sets use the same VM SKUs.
108
109### Step 4: Look Up Pricing
110
111Query the Azure Retail Prices API — [Retail Prices API Guide](references/retail-prices-api.md)
112
113> **Tip:** VMSS has no extra charge — pricing is per-VM instance. Use the same VM pricing from the API and multiply by the expected instance count to estimate VMSS cost. For autoscaling workloads, estimate cost at both the minimum and maximum instance count.
114
115### Step 5: Present Recommendations
116
117Provide **2–3 options** with trade-offs:
118
119| Column | Purpose |
120| -------------- | ----------------------------------------------- |
121| Hosting Model | VM or VMSS (with orchestration mode if VMSS) |
122| VM Size | ARM SKU name (e.g., `Standard_D4s_v5`) |
123| vCPUs / RAM | Core specs |
124| Instance Count | 1 for VM; min–max range for VMSS with autoscale |
125| Estimated $/hr | Per-instance pay-as-you-go from API |
126| Why | Fit for the workload |
127| Trade-off | What the user gives up |
128
129> **Tip:** Always explain *why* a family fits and what the user trades off (cost vs cores, burstable vs dedicated, single VM simplicity vs VMSS scalability, etc.).
130
131For VMSS recommendations, also mention:
132- Recommended orchestration mode (Flexible for most new workloads)
133- Autoscale strategy (metric-based, schedule-based, or both)
134- Load balancer type (Azure Load Balancer for L4, Application Gateway for L7/TLS)
135
136### Step 6: Offer Next Steps
137
138- Compare reservation / savings plan pricing (query API with `priceType eq 'Reservation'`)
139- Suggest [Azure Pricing Calculator](https://azure.microsoft.com/pricing/calculator/) for full estimates
140- For VMSS: suggest reviewing [autoscale best practices](https://learn.microsoft.com/en-us/azure/azure-monitor/autoscale/autoscale-best-practices) and [VMSS networking](https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-networking)
141
142## Error Handling
143
144| Scenario | Action |
145| ------------------------------- | ------------------------------------------------------------------------------ |
146| API returns empty results | Broaden filters — check `armRegionName`, `serviceName`, `armSkuName` spelling |
147| User unsure of workload type | Ask clarifying questions; default to General Purpose D-series |
148| Region not specified | Use `eastus` as default; note prices vary by region |
149| Unclear if VM or VMSS needed | Ask about scaling and instance count; default to single VM if unsure |
150| User asks VMSS pricing directly | Use same VM pricing API — VMSS has no extra charge; multiply by instance count |
151
152## References
153
154- [VM Family Guide](references/vm-families.md) — Family-to-workload mapping and selection
155- [Retail Prices API Guide](references/retail-prices-api.md) — Query patterns, filters, and examples
156- [VMSS Guide](references/vmss-guide.md) — When to use VMSS, orchestration modes, and autoscale patterns
JantonioFC