AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

azure-local-multi-rack

Plan, deploy, operate, and troubleshoot multi-rack (rack scale) deployments of Azure Local — preintegrated racks scaling to hundreds of machines, built on Network Fabric Controller, Cluster Manager, SAN storage, and managed network fabric. Use for the Microsoft.NetworkCloud and Microsoft.ManagedNetworkFabric control plane. NOT for standard 1-16 node Azure Local, and NOT for rack-aware clusters (two racks as availability zones, up to 8 nodes, synchronous replication) — those are standard scale. WHEN: multi-rack, rack scale Azure Local, aggregation rack, compute rack, Network Fabric Controller, NFC, Cluster Manager, network fabric, isolation domain, az networkcloud, az networkfabric, multi-rack logical network, multi-rack Arc VM.

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read microsoft--azure-local-multi-rack at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 9

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

  1. Confirm scale and scope — Multi-rack, plus cluster and custom location. See resource-types.
  2. Check VM prerequisites — Fetch multi-rack-vm-management-prerequisites via docs-map.
  3. Prepare networking first — Logical networks and network interfaces must exist before VM creation. See networking.
  4. Prepare images — Manage VM images or the image storage account per the multi-rack image articles.
  5. Create or manage VMs — Use the multi-rack Arc VM articles for create, manage, and resource operations.
  6. Attach storage — Data disks and snapshots per the multi-rack disk articles.
  7. GPU workloads — Follow GPU preparation before device management.
  8. AKS — Use the AKS multi-rack architecture doc; AKS on multi-rack differs from AKS on standard Azure Local.
  9. 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.

Related references