Azure Local
Quick Reference
When to Use This Skill
Use for Azure Local, Azure Stack HCI, Azure Local VMs, AKS on Azure Local, AKS hybrid, SDN, lifecycle updates, disconnected sites, or troubleshooting. Covers standard deployments (1-16 node hyperconverged, up to 64 disaggregated) and rack-aware clusters.
Do not use for cloud VM or public AKS guidance, or for multi-rack (rack scale) deployments — those use a separate control plane and procedure set. Hand off to the azure-local-multi-rack skill.
MCP Tools
Azure Local has no dedicated MCP namespace. Use generic Azure MCP tools: mcp_azure_mcp_extension_cli_generate (ARG/CLI inventory), mcp_azure_mcp_monitor (needs Log Analytics), mcp_azure_mcp_resourcehealth (partial; not local cluster health), mcp_azure_mcp_documentation (pass the user's version when known).
Scope and limitations: mcp-and-cli-tools [blocked].
Workflow
- Confirm deployment scale. If the user mentions multi-rack, aggregation racks, Network Fabric Controller, Cluster Manager, or
Microsoft.NetworkCloudresources, stop and use theazure-local-multi-rackskill instead. - Deploy -> plan-and-deploy [blocked]
- Operate/update -> operate-and-update [blocked]
- VMs, AKS, images, disks, networks -> workload-management [blocked]
- SDN, NSG, load balancer, gateway -> networking-and-security [blocked]
- Failures -> troubleshooting [blocked]
Read the matched workflow first and use docs-map [blocked]. Start read-only. Ask before updates, deletes, reimages, network changes, VM power/delete operations, or Arc bridge/custom location changes.
