Azure Local
SkillCloud & infraGuides your agent through planning, deploying, operating, and troubleshooting Azure Local clusters step by step.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Azure Local skill
About this capability
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 confi
What this skill tells your AI
The instructions your AI receives, as published by microsoft/skills in .github/plugins/azure-local-skills/skills/azure-local/SKILL.md and read by ahel’s review.
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.
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
- Operate/update -> operate-and-update
- VMs, AKS, images, disks, networks -> workload-management
- SDN, NSG, load balancer, gateway -> networking-and-security
- Failures -> troubleshooting
Read the matched workflow first and use docs-map. Start read-only. Ask before updates, deletes, reimages, network changes, VM power/delete operations, or Arc bridge/custom location changes.
Error Handling
| Scenario | Remediation |
|---|---|
| Scale unknown | Ask whether the deployment is standard or multi-rack before giving procedures. |
| Multi-rack detected | Hand off to the azure-local-multi-rack skill; these procedures do not apply. |
| Version unknown | Ask for the Azure Local version, or use latest docs. |
| Risky change detected | Stop and follow safety-rules. |
| No local access | Stay with Azure control-plane checks only. |
| Doc URL 404/redirect | Search Learn for the article title with the user's version. |
Signals
- GitHub stars
- 3k
- Forks
- 348
- Last commit
- Sep 2026
ahel recommends instead
Advanced
- Catalog kind
- skill
- Gateway key
azure-local-microsoft- Source
- github.com/microsoft/skills