Azure Local
MicrosoftOfficialCreated by Microsoft
- Skill
- Tool integration
- Cloud and DevOps
- MIT
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a structured approach to managing Azure Local (formerly Azure Stack HCI) environments. It covers the full lifecycle from initial planning and prerequisites to deployment, workload management (including VMs and AKS on Azure Local), networking, security, and ongoing maintenance. The skill emphasizes safety by requiring read-only verification before executing any destructive or configuration-changing operations and provides guidance on when to escalate to specialized multi-rack procedures.
What it does
- Guides users through Azure Local planning, sizing, and deployment prerequisites.
- Manages lifecycle updates and cluster maintenance tasks.
- Facilitates the management of workloads including Azure Local VMs and AKS on Azure Local.
- Assists in configuring SDN, network security, and load balancing.
- Provides troubleshooting steps for cluster failures and health issues.
- Ensures safe operations by requiring confirmation before risky changes.
When to use it
- When planning or deploying a standard 1-16 node hyperconverged or up to 64-node disaggregated Azure Local cluster.
- When performing lifecycle updates or managing cluster health.
- When managing VMs, AKS clusters, or network resources on Azure Local.
- When troubleshooting connectivity, SDN, or cluster-level issues.
- When you need to verify prerequisites for Arc registration or custom location setup.
Advantages
- Ensures adherence to official Microsoft Learn documentation and best practices.
- Promotes operational safety through a read-only-first approach.
- Provides clear boundaries between standard deployments and complex multi-rack scenarios.
- Centralizes guidance for both Azure control-plane and local cluster management tasks.
Usage examples
- “What are the network prerequisites for deploying a new Azure Local cluster?”
- The agent will provide a summary of physical and host network requirements, including links to the relevant Microsoft Learn documentation for network patterns.
- “How do I check the update status of my Azure Local cluster?”
- The agent will guide you through using the appropriate Azure CLI or PowerShell commands to assess and report the current update status of your cluster.
- “I need to troubleshoot a VM that is not starting on my Azure Local cluster.”
- The agent will initiate the troubleshooting workflow, starting with read-only checks of the VM state and cluster health before suggesting remediation steps.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/microsoft/azure-local/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip azure-local.zip -d .agents/skills
Documentation by Microsoft
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.
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. |
Files
- ATTRIBUTION.mdAdded by AutoGineer983 B
- LICENSELicence file added by AutoGineer1.1 KiB
- SKILL.md3.3 KiB
- references/docs-map.md7.6 KiB
- references/mcp-and-cli-tools.md3.4 KiB
- references/resource-types.md2.5 KiB
- references/safety-rules.md2.1 KiB
- workflows/networking-and-security/networking-and-security.md3.5 KiB
- workflows/operate-and-update/operate-and-update.md3.6 KiB
- workflows/plan-and-deploy/plan-and-deploy.md4.3 KiB
- workflows/troubleshooting/troubleshooting.md3.7 KiB
- workflows/workload-management/workload-management.md3.4 KiB
workflows/networking-and-security/networking-and-security.md
Networking and Security for Azure Local
Use this workflow for Azure Local physical networking, validated topology selection, SDN, NSGs, software load balancer, gateways, datacenter firewall, private endpoints, security baseline, governance, and compliance.
Networking flow
Identify layer - Physical host/storage network, cloud deployment connectivity, SDN fabric, tenant/workload networking, or VM/AKS workload networking.
Load current docs - Use docs-map for physical network requirements, network reference patterns, SDN overview, private endpoints, and firewall/proxy guidance.
Collect topology - Node count, storage switchless/switched design, converged/non-converged adapters, VLANs, IP ranges, DNS, gateways, proxy, and firewall requirements.
Validate support - Confirm the selected topology is supported for portal or ARM deployment.
Plan changes - For SDN/NSG/load balancer/gateway changes, map dependent workloads and rollback requirements before making changes.
Apply with confirmation - Network changes can interrupt management or workloads. Ask before applying changes.
Validate reachability - Check Arc connectivity, management endpoints, workload IPs, NSG behavior, load balancer/gateway health, DNS, and monitoring.
Security flow
Start from secure defaults - Azure Local is secure by default with a baseline of security settings. Do not disable baseline controls without an explicit reason.
Map governance - Confirm Azure Policy, Defender for Cloud, Azure Monitor, RBAC, identity, and compliance requirements.
Check secrets and certificates - For private endpoints, SDN, and local identity scenarios, verify certificate and Key Vault requirements from docs.
Apply least privilege - Use Azure RBAC and Azure Local-specific roles for VM/workload administration.
Document exceptions - Any security exception must include reason, scope, owner, and validation plan.
SDN routing
| Signal | Area |
|---|---|
| Network Controller, SDN infrastructure, SDN Express, SDN wizard | SDN deployment/management docs |
| NSG, default network access policy, tags | Network security group docs |
| Software load balancer, public IP assignment | Load balancer docs |
| Gateway connections, multisite, route reflector | Gateway and multisite docs |
| Datacenter firewall | Datacenter firewall docs |
| SDN certificate, Kerberos SPN, Network Controller security | SDN security docs |
Guardrails
Confirm topology and current state before changing IP ranges, VLANs, gateways, DNS, NSGs, load balancers, or firewall policy.
Do not recommend unsupported network patterns for the user's node count/storage design.
Do not disable security baseline controls or Defender/Policy protections as a workaround without explicit confirmation and risk disclosure.
Use safety-rules for any change that can disrupt management, storage, or workloads.
Handoff
Deployment topology and initial Arc/private endpoint setup -> Plan and Deploy.
Workload logical networks, NICs, VM connectivity, and AKS networking -> Workload Management.
SDN or connectivity failure -> Troubleshooting.
Related references
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 · 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 or Microsoft.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download azure-local.zip