Runners
Azure VM
Runner group kind backend_type=azure_vm — one Azure Virtual Machine per execution (not a scale set)
backend_type: azure_vm. Connection: Azure. Status: production-shaped; warm-pool reconcile is not as complete as EC2 VM.
Each execution is a dedicated Azure VM (not a Scale Set member, not a Container Apps Job).
When to choose it
- Per-job isolation on Azure VMs.
- Custom VM size, image, or region that Container Apps cannot express.
Choose Azure VMSS for a scale set. Choose Azure Container Apps for jobs.
Connection
An Azure connection.
Required config
| Key | Type | Meaning |
|---|---|---|
subscription_id | string | Azure subscription. |
resource_group | string | Resource group for the per-execution VM. |
location | string | Azure region (e.g. eastus). |
vm_size | string | VM size (e.g. Standard_D2s_v5). |
Execution control
Suffixed workflows: runner.execution-{stop,restart,sync,logs-sync}-azure-vm.
Warm-pool reconcile for this kind is a sibling port of the EC2 VM controller and may not be running on live groups yet. Do not assume
min/max converge the same way they do on EC2 VM until you have confirmed runner.pool-reconcile-* coverage in the catalog.Purposes
CI and agent are valid. Agent images still require purpose=agent.