**WORKFLOW SKILL** — Plan, deploy, and operate Azure Local disconnected operations (air-gapped / no continuous Azure connectivity): network, identity, security, PKI, control-plane appliance, and local management via CLI/PowerShell. WHEN: "Azure Local disconnected operations", "air-gapped Azure Local", "Azure Local without internet", "disconnected operations deploy", "local control plane appliance", "disconnected identity", "disconnected PKI", "sovereign air gap Azure Local". USE FOR: air-gapped Azure Local deployments and local operations. DO NOT USE FOR: connected-instance deployment (use azlocal-deploy).
**WORKFLOW SKILL** — Plan, deploy, and operate Azure Local disconnected operations (air-gapped / no continuous Azure connectivity): network, identity, security, PKI, control-plane appliance, and local management via CLI/PowerShell. WHEN: "Azure Local disconnected operations", "air-gapped Azure Local", "Azure Local without internet", "disconnected operations deploy", "local control plane appliance", "disconnected identity", "disconnected PKI", "sovereign air gap Azure Local". USE FOR: air-gapped Azure Local deployments and local operations. DO NOT USE FOR: connected-instance deployment (use azlocal-deploy).
compatibility
Works with Claude Code, GitHub Copilot, VS Code, and any Agent Skills compatible tool.
This skill is grounded in the vendored Microsoft docs under docs/upstream/azure-local/manage/ (the disconnected-operations-* pages). Prefer those files over prior knowledge, cite the file you used, and treat Microsoft Learn as canonical when the weekly mirror lags.
Triggers
Activate this skill when the user wants to:
Design an air-gapped Azure Local deployment with a local control plane
Operate VMs, registry, identity, and policy without Azure reachability
Plan disconnected network, identity, security, or PKI
Rules
Prefer the vendored docs under docs/upstream/azure-local/manage/; cite the exact file used.
Plan the dedicated management cluster (network/identity/security/PKI) before deploying.
Use the local CLI/PowerShell control path — never assume outbound Azure connectivity.
Microsoft Learn / discovered governance wins over the mirror on any conflict.
Steps
Plan the dedicated management cluster: network, identity, security, PKI.
Acquire & prepare nodes, then deploy disconnected operations and register.
Operate locally via Azure CLI / PowerShell; run Arc VMs and a local container registry.
Monitor & recover with on-demand/fallback log collection and backup/restore.
