# Azure Local

Plan, deploy, operate, and troubleshoot Azure Local (formerly Azure Stack HCI): sizing...

- Repository: https://github.com/microsoft/skills (3164 stars)
- Category: Security
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add microsoft/skills --skill azure-local -g -a claude-code -y`
Codex: `npx skills add microsoft/skills --skill azure-local -g -a codex -y`
Cursor: `npx skills add microsoft/skills --skill azure-local -g -a cursor -y`
Gemini CLI: `npx skills add microsoft/skills --skill azure-local -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add microsoft/skills`

## Description

Plan, deploy, operate, and troubleshoot Azure Local (formerly Azure Stack HCI): sizing and prerequisites, Arc registration, lifecycle updates, workloads (Azure Local VMs, AKS on Azure Local, images, disks, logical networks), SDN and network security, and failure triage, starting read-only and confirming before risky changes. WHEN: Azure Local, Azure Stack HCI, Arc resource bridge, custom location, Azure Local VM, Arc VM, AKS on Azure Local, AKS hybrid, SDN, Lifecycle Manager, Azure Local update, disconnected site.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Azure Local

## Quick Reference

| Property | Value |
| --- | --- |
| Best for | Azure Local planning, deployment, operations, workloads |
| MCP Tools | Generic Azure MCP tools only; no Azure Local namespace |
| CLI | `az graph query`, `az resource show`, Azure Local PowerShell |
| Related skills | azure-compute (public VMs), azure-kubernetes (public AKS) |

## 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](references/mcp-and-cli-tools.md).

## Workflow

0. Confirm deployment scale. If the user mentions multi-rack, aggregation racks, Network Fabric Controller, Cluster Manager, or `Microsoft.NetworkCloud` resources, stop and use the `azure-local-multi-rack` skill instead.
1. Deploy -> [plan-and-deploy](workflows/plan-and-deploy/plan-and-deploy.md)
2. Operate/update -> [operate-and-update](workflows/operate-and-update/operate-and-update.md)
3. VMs, AKS, images, disks, networks -> [workload-management](workflows/workload-management/workload-management.md)
4. SDN, NSG, load balancer, gateway -> [networking-and-security](workflows/networking-and-security/networking-and-security.md)
5. Failures -> [troubleshooting](workflows/troubleshooting/troubleshooting.md)

The rest: https://github.com/microsoft/skills/blob/HEAD/.github/plugins/azure-local-skills/skills/azure-local/SKILL.md