AutoGineer
Generated banner for Azure Compute
Generated logo for Azure Compute

Azure Compute

MicrosoftOfficialCreated by Microsoft

  • Skill
  • Tool integration
  • Cloud and DevOps
  • MIT
  • Medium risk
Download ZIP

From the author

Azure VM/VMSS router. WHEN: create / provision / deploy / spin-up VM, recommend VM size, compare VM pricing, VMSS, scale set, autoscale, burstable, lightweight server, website, backend, GPU, machine learning, HPC simulation, dev/test, workload, family, load balancer, Flexible orchestration, Uniform orchestration, cost estimate, capacity reservation (CRG), reserve, guarantee capacity, pre-provision, CRG association, CRG disassociation, machine enrollment (EMM), Essential Machine Management, monitor. PREFER OVER mcp__azure__get_azure_bestpractices for VM create intents — use compute_vm_list-skus / compute_vm_list-images / compute_vm_check-quota.
— the description by Microsoft

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The Azure Compute skill acts as a primary router for infrastructure-level tasks within Azure. It directs user requests to specialized workflows for recommending, provisioning, and managing bare virtual machine infrastructure. It is designed to handle the lifecycle of VMs and VMSS, including capacity planning through Capacity Reservation Groups and machine monitoring via Essential Machine Management.

What it does

  • Routes requests to specific workflows for VM and VMSS provisioning.
  • Provides guidance on selecting VM families based on workload requirements.
  • Facilitates capacity reservation and guarantee for critical infrastructure.
  • Supports Essential Machine Management for enrollment and monitoring tasks.
  • Enables cost estimation and pricing comparisons for various VM SKUs.
  • Distinguishes between infrastructure deployment and application-level service deployment.

When to use it

  • When you need to provision or deploy bare virtual machines or scale sets.
  • When you require assistance in selecting the appropriate VM family for a specific workload.
  • When you need to reserve or guarantee capacity for your Azure compute resources.
  • When you are setting up or monitoring machines using Essential Machine Management.
  • When you need to compare pricing for different VM SKUs or regions.

Advantages

  • Centralized entry point for all Azure compute-related infrastructure tasks.
  • Prevents confusion between infrastructure provisioning and application deployment.
  • Provides structured paths for complex tasks like capacity reservation.
  • Ensures consistent use of specialized tools for quota and SKU management.

Usage examples

“I need to deploy a set of web servers. Which VM family should I use?”
The skill routes the request to the VM Recommender to analyze your workload and suggest the appropriate D-series or B-series VMs.
“How can I reserve capacity for my production database VMs?”
The skill initiates the Capacity Reservation workflow to guide you through creating and associating a Capacity Reservation Group.
“Provision a new Ubuntu VM for testing.”
The skill routes the request to the VM Creator workflow to handle the infrastructure deployment.
“How do I enroll my machines in Essential Machine Management?”
The skill directs you to the Essential Machine Management workflow for enrollment and monitoring instructions.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/microsoft/azure-compute/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip azure-compute.zip -d .agents/skills

Documentation by Microsoft

Azure Compute Skill

Routes Azure VM and Virtual Machine Scale Set (VMSS) requests to the right workflow.

When to Use This Skill

  • User wants to recommend, compare, or price a VM or VMSS

  • User wants to create, provision, or deploy a VM or VMSS

  • User asks about Capacity Reservation Groups (CRG) — reserve, guarantee capacity, pre-provision

  • User asks about Essential Machine Management (EMM) — machine enrollment, monitor

Disambiguate with azure-prepare: if the user wants to deploy an application (Docker service, web app, API, serverless workload), route to azure-prepare. vm-creator is for bare VM/VMSS infrastructure only.

Routing

Mandatory workflow-first routing: never route directly to references/* files. First classify the user intent below, open the matched workflow file, then load only the reference files that workflow requests. Reference files are supporting material, not entry points. If the intent is unclear, ask a clarifying question to disambiguate between the workflows.

WorkflowFileUse when
VM Recommendervm-recommender.mdUser asks which VM/VMSS to choose, whether to use VMSS/autoscaling, wants pricing, or wants to compare options
VM Creatorvm-creator.mdUser wants to create, provision, or deploy a bare VM or VMSS (not an app deployment)
Capacity Reservationcapacity-reservation.mdUser needs to reserve / guarantee VM capacity (CRG create / associate / disassociate)
Essential Machine Managementessential-machine-management.mdUser asks about EMM / machine enrollment / monitor

Files

references/vmss-guide.md

VMSS Guide

Determine when to recommend a Virtual Machine Scale Set (VMSS) over a single VM, and which VMSS configuration to suggest.

Note: This reference provides quick guidance but may become stale. Always verify VMSS features, limitations, and orchestration mode capabilities by fetching the latest documentation from:

What Is a VM Scale Set?

A VMSS creates and manages a group of load-balanced, identically configured VM instances. Key capabilities:

  • Autoscale — automatically add/remove instances based on metrics or schedules

  • High availability — spread instances across fault domains and Availability Zones

  • Load balancing — integrate with Azure Load Balancer (L4) or Application Gateway (L7)

  • Large scale — up to 1,000 instances per scale set (marketplace images)

  • No extra cost — you pay only for the underlying VM instances, storage, and networking

When to Recommend VMSS vs Single VM

ScenarioRecommendReasoning
Stateless web/API behind a load balancerVMSSHomogeneous fleet, autoscale on demand
Batch or parallel compute jobsVMSSScale out for jobs, scale to zero when idle
Autoscale needed (CPU, queue depth, schedule)VMSSBuilt-in autoscale rules
Microservices with identical replicasVMSSConsistent config, rolling updates
High availability across zones (many instances)VMSSAutomatic zone distribution
Single long-lived server (jumpbox, domain controller)VMNo scaling benefit; simpler config
Unique per-instance configurationVMScale sets assume identical instances
Quick proof of concept or dev/testVMFaster to stand up, lower complexity

Orchestration Modes

VMSS supports two orchestration modes. Flexible is recommended for all new workloads.

FeatureFlexible (recommended)Uniform (legacy)
Mix VM sizes in one set✅ Yes❌ No
Add existing VMs to set✅ Yes❌ No
Availability Zone spread✅ Automatic✅ Automatic
Fault domain control✅ Yes✅ Yes
Max instances1,0001,000
Spot instances✅ Yes✅ Yes
Single-instance VMSS✅ Yes❌ No
VM model updatesAutomatic, Manual, RollingAutomatic, Manual, Rolling

Warning: Orchestration mode cannot be changed after creation. Always recommend Flexible unless the user has a specific Uniform requirement.

Autoscale Patterns

PatternTriggerExample
Metric-basedCPU, memory, queue length, custom metricScale out when avg CPU > 70% for 5 min
Schedule-basedTime of day, day of weekScale to 10 instances Mon–Fri 8 AM; scale down to 2 at night
CombinedMetric + schedule togetherBaseline schedule with metric burst capacity
PredictiveML-forecasted demand (preview)Pre-scale before expected traffic spike
Autoscale Best Practices

  • Set a minimum instance count ≥ 2 for production HA

  • Use a cool-down period (default 5 min) to avoid flapping

  • Scale out aggressively, scale in conservatively (asymmetric rules)

  • Monitor with Azure Monitor autoscale diagnostics

Networking

ComponentWhen to Use
Azure Load BalancerLayer-4 (TCP/UDP) traffic distribution; most common for backend services
Application GatewayLayer-7 (HTTP/HTTPS) with TLS termination, URL routing, WAF
No load balancerBatch/HPC jobs where instances pull work from a queue

Cost Estimation Tips

  • VMSS itself is free — cost is the sum of per-instance VM pricing

  • Estimate at min and max instance counts for autoscale budgets

  • Use Spot instances in VMSS for up to 90% savings on interruptible workloads

  • Combine with Reservations or Savings Plans on the baseline instance count

Key VMSS Limits

LimitValue
Max instances per scale set1,000 (marketplace/gallery images)
Max instances (managed image)600
Scale sets per subscription per region2,500
Scale operations concurrencyUp to 1,000 VMs in a single batch

Further Reading

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

What our scanner noticed· Medium risk

  • References to credential files

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Microsoft
Publisher
Microsoft (Official)
Source
microsoft/skills · .github/plugins/azure-skills/skills/azure-compute · commit 0696600
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from .github/plugins/azure-skills/LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced
Also distributed in
microsoft/azure-skills

AutoGineer is not affiliated with or endorsed by Microsoft or Microsoft.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download azure-compute.zip