Generated banner for Azure Local Multi Rack
Generated logo for Azure Local Multi Rack

Azure Local Multi Rack

MicrosoftOfficialCreated by Microsoft

  • Skill
  • Workflow
  • Cloud and DevOps
  • MIT
  • No issues found

From the author

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.
— the description by Microsoft

AutoGineer summary

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

The azure-local-multi-rack skill provides a structured approach to planning, deploying, and operating large-scale, multi-rack Azure Local environments. Unlike standard deployments, these rack-scale configurations utilize a specialized control plane involving a Network Fabric Controller (NFC) and Cluster Manager. This skill covers the unique requirements for managing preintegrated racks, SAN storage, and managed network fabrics, ensuring users follow the correct procedures for logical networks, Arc VM management, and fabric operations.

What it does

  • Guides users through planning and deploying rack-scale Azure Local infrastructure.
  • Provides procedures for managing Arc VMs, images, and storage in a multi-rack environment.
  • Facilitates configuration of network fabrics, isolation domains, and load balancers.
  • Supports operational tasks including monitoring, metrics, and serial console access.
  • Ensures correct usage of specialized Azure CLI extensions for multi-rack control planes.
  • Distinguishes between multi-rack and standard Azure Local deployment requirements.

When to use it

  • When deploying or managing rack-scale Azure Local environments with 100+ machines.
  • When working with preintegrated racks, aggregation racks, and managed network fabrics.
  • When utilizing the Microsoft.NetworkCloud and Microsoft.ManagedNetworkFabric control planes.
  • When you need to configure complex networking components like isolation domains or internal load balancers.
  • When troubleshooting issues specific to multi-rack infrastructure components.

Advantages

  • Prevents confusion by clearly separating multi-rack procedures from standard Azure Local workflows.
  • Provides a centralized map to authoritative Microsoft Learn documentation for preview features.
  • Promotes safe operations by requiring read-only verification before executing fabric or SAN changes.
  • Ensures the correct CLI extensions are identified and used for specific resource providers.

Usage examples

“How do I create a new logical network for my multi-rack deployment?”
The agent will guide you through the specific multi-rack logical network creation workflow, ensuring you use the correct network fabric commands rather than standard Azure Local procedures.
“I need to troubleshoot a VM issue on my rack-scale cluster.”
The agent will provide steps for using the serial console and monitoring tools specifically designed for Arc VMs within a multi-rack architecture.
“What are the prerequisites for setting up a new multi-rack instance?”
The agent will outline the necessary Network Fabric Controller and Cluster Manager setup, along with the required Azure CLI extensions and provider registrations.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/microsoft/azure-local-multi-rack/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip azure-local-multi-rack.zip -d .agents/skills

Documentation by Microsoft

Azure Local Multi-Rack

Multi-rack is in preview — say so, and confirm availability from the docs before committing to a design.

Quick Reference

PropertyValue
Best forRack-scale Azure Local: 100+ machines, preintegrated racks, SAN, managed fabric
ScaleMinimum four racks — one aggregation rack plus three or more compute racks
ProvidersMicrosoft.NetworkCloud, Microsoft.ManagedNetworkFabric, Microsoft.AzureStackHCI
CLIaz networkcloud, az networkfabric, az stack-hci-vm
Related skillazure-local for standard 1-16 node and rack-aware deployments

When to Use This Skill

Use when the deployment is multi-rack / rack scale: preintegrated racks, an aggregation rack, a Network Fabric Controller, a Cluster Manager, SAN storage, or the networkcloud / managednetworkfabric CLI extensions.

Do not use for standard Azure Local (1-16 node hyperconverged, up to 64 disaggregated) or rack-aware clusters — hand off to the azure-local skill. If the scale is unclear, ask first: the two have separate, non-interchangeable procedures for the same-sounding tasks (logical networks, VM creation, NSGs).

MCP Tools

No dedicated MCP namespace. Use generic Azure MCP tools: mcp_azure_mcp_extension_cli_generate (confirm networkcloud/networkfabric extensions first), mcp_azure_mcp_monitor (needs Log Analytics), mcp_azure_mcp_resourcehealth (partial; not fabric or SAN health), mcp_azure_mcp_documentation (multi-rack articles only — standard Azure Local pages do not apply).

Details: cli-and-prereqs.

Workflow

  1. Confirm this is multi-rack, not standard Azure Local — see When to Use.

  2. Plan/deploy -> plan-and-deploy

  3. VMs, AKS, images, disks -> workload-management

  4. Fabric, isolation domains, load balancers, NSGs -> networking

  5. Monitoring, metrics, serial console, failures -> operate-and-monitor

Read the matched workflow first and use docs-map. Start read-only. Ask before fabric changes, isolation domain edits, VM power/delete operations, or anything touching the aggregation rack or SAN.

Error Handling

ScenarioRemediation
Scale unknownAsk whether the deployment is multi-rack or standard before recommending procedures.
Standard Azure Local detectedHand off to the azure-local skill; multi-rack procedures do not apply.
Missing CLI extensionInstall per cli-and-prereqs before running commands.
Risky fabric or SAN changeStop and follow safety-rules.
Doc URL 404/redirectSearch Learn for the title, scoped to multi-rack deployments of Azure Local.

Files

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

QuestionWhy it matters
Confirmed multi-rack?Standard Azure Local VM procedures do not apply.
Cluster, custom location, resource groupRequired scope for every workload command.
Workload typeVM, AKS, or GPU workloads have different prerequisites.
Network requirementsLogical network, virtual network, or load balancer must exist first.
Image sourceMarketplace, 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.

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.

Needs: Needs Node.js

Security

No issues found by our static scan· No issues found

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-local-skills/skills/azure-local-multi-rack · commit 0696600
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from .github/plugins/azure-local-skills/LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

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-local-multi-rack.zip