workflows/workload-management/workload-management.md
Multi-Rack Workload Management
Use for Arc VMs, images, disks, GPU, and AKS on a multi-rack instance. Multi-rack has its own VM management article set — do not substitute standard Azure Local VM procedures.
Intake
| Question | Why it matters | | --- | --- | | Confirmed multi-rack? | Standard Azure Local VM procedures do not apply. | | Cluster, custom location, resource group | Required scope for every workload command. | | Workload type | VM, AKS, or GPU workloads have different prerequisites. | | Network requirements | Logical network, virtual network, or load balancer must exist first. | | Image source | Marketplace, custom image, or image storage account. |
Sequence
- Confirm scale and scope — Multi-rack, plus cluster and custom location. See resource-types.
- Check VM prerequisites — Fetch
multi-rack-vm-management-prerequisitesvia docs-map. - Prepare networking first — Logical networks and network interfaces must exist before VM creation. See networking.
- Prepare images — Manage VM images or the image storage account per the multi-rack image articles.
- Create or manage VMs — Use the multi-rack Arc VM articles for create, manage, and resource operations.
- Attach storage — Data disks and snapshots per the multi-rack disk articles.
- GPU workloads — Follow GPU preparation before device management.
- AKS — Use the AKS multi-rack architecture doc; AKS on multi-rack differs from AKS on standard Azure Local.
- Access — SSH connectivity and RBAC role assignment per the relevant articles.
Guardrails
- Ask before VM power, delete, disk detach, or snapshot deletion.
- Do not create workloads before confirming the target logical network and custom location.
- Do not reuse standard Azure Local commands or article steps.
- Confirm required CLI extensions are installed — see cli-and-prereqs.
- Follow safety-rules.
Evidence to collect
- Cluster, custom location, resource group, region.
- VM names and resource IDs, power state, provisioning state.
- Attached logical networks and network interfaces.
- Image source and version.
- Disk and snapshot inventory.
- Extension versions and CLI extension versions.