Generated banner for Azure Compute
Generated logo for Azure Compute

Azure Compute

MicrosoftOfficialCreated by Microsoft

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

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://mp-staging.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

workflows/vm-creator/references/delivery-options/github-pr.md

Mode C — Sync to a GitHub repo

Step 1 — Gather repo + branch + path

Ask three things (batch into one message; accept all three at once or walk through them):

  1. Repo — accept any of:

    • owner/name (e.g., myorg/azure-infra)

    • Full URL (e.g., https://github.com/myorg/azure-infra)

    • Local checkout path (e.g., ~/source/azure-infra) — skips clone

  2. Branch — default: infra/vm-{vm-name}. Refuse to commit directly to main / master / default. Always a branch + PR.

  3. Target path inside repo — default: infra/{vm-name}/. If the repo has a recognizable infra root (/terraform, /bicep, /infrastructure), suggest that.

Step 2 — Pre-flight

# 1. gh installed and authenticated
gh auth status        # must succeed; if not, fall back to Mode C-fallback below

# 2. user has push rights
gh repo view {owner/repo} --json viewerPermission --jq '.viewerPermission'
# Must be ADMIN, MAINTAIN, or WRITE; otherwise pivot to fork-and-PR

# 3. branch doesn't already exist
gh api repos/{owner/repo}/branches/{branch}  # 404 = good (new branch)

If gh is missing or unauthenticated, switch to Mode C-fallback — don't block.

Step 3 — Clone, write, commit, push, PR

Echo each command so the user can replay:

# 1. Working tree
TMP=$(mktemp -d) && cd "$TMP"
gh repo clone {owner/repo} .

# 2. Branch off the default branch
DEFAULT_BRANCH=$(gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name')
git checkout -b {branch} "origin/$DEFAULT_BRANCH"

# 3. Write the artifact files (same layout as Mode B)
mkdir -p {targetPath}
# ... Write tool calls for each file ...

# 4. Stage, commit, push
git add {targetPath}
git commit -m "Add {vm-name} VM infrastructure (Bicep)" \
           -m "Generated by azure-compute vm-creator workflow."
git push -u origin {branch}

# 5. Open the PR
gh pr create \
  --title "Add {vm-name} VM infrastructure" \
  --body  "$(cat <<'EOF'
## Summary
Adds Bicep templates to provision \`{vm-name}\` in \`{location}\`.

## Plan Card
{paste-plan-card-markdown}

## Deploy
\`\`\`bash
cd {targetPath}
az deployment group create --resource-group {resourceGroup} \\
  --template-file main.bicep --parameters vmName={vm-name} ...
\`\`\`
EOF
)" \
  --base "$DEFAULT_BRANCH" --head {branch}

Echo the PR URL back:

✅ Opened PR: https://github.com/myorg/azure-infra/pull/42

Step 4 — Optional follow-ups

After the PR is open, offer (don't force):

  • "Want me to add a GitHub Action to validate this with az deployment group what-if on every PR?" — generates .github/workflows/bicep-whatif.yml

  • "Want OIDC auth so CI can apply without a service principal secret?" — points at the azure-prepare skill

Mode C-fallback (no gh / unauthenticated / no push rights)

Write the files to ~/Desktop/{vm-name}-infra/ (Mode B path) and print:

⚠ I can't push for you (gh auth status failed), so I wrote the files locally.

To open the PR yourself:

cd ~/Desktop/dev-vm-infra
git init && git add . && git commit -m "Add dev-vm infrastructure"
git remote add origin [email protected]:myorg/azure-infra.git
git checkout -b infra/vm-dev-vm
git push -u origin infra/vm-dev-vm
gh pr create --fill   # after `gh auth login`

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.

Download ZIP

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