**ANALYSIS SKILL** — Design with Microsoft Sovereign Private Cloud on Azure Local: connected vs disconnected operations, use cases, and Foundry Local AI (deploy/run models, BYOM, inference) for on-premises sovereign AI. WHEN: "Sovereign Private Cloud", "sovereign Azure Local", "connected operations", "disconnected operations sovereign", "Foundry Local", "on-premises AI sovereign", "run models on Azure Local", "sovereign AI workloads". USE FOR: designing on-premises sovereign solutions on Azure Local. DO NOT USE FOR: public-cloud sovereignty (use sov-public-cloud), air-gapped operational runbooks (use azlocal-disconnected).
**ANALYSIS SKILL** — Design with Microsoft Sovereign Private Cloud on Azure Local: connected vs disconnected operations, use cases, and Foundry Local AI (deploy/run models, BYOM, inference) for on-premises sovereign AI. WHEN: "Sovereign Private Cloud", "sovereign Azure Local", "connected operations", "disconnected operations sovereign", "Foundry Local", "on-premises AI sovereign", "run models on Azure Local", "sovereign AI workloads". USE FOR: designing on-premises sovereign solutions on Azure Local. DO NOT USE FOR: public-cloud sovereignty (use sov-public-cloud), air-gapped operational runbooks (use azlocal-disconnected).
compatibility
Works with Claude Code, GitHub Copilot, VS Code, and any Agent Skills compatible tool.
Microsoft Sovereign Private Cloud (on Azure Local)
AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE
This skill is grounded in the vendored Microsoft docs under docs/upstream/azure-sovereign-clouds/private/. 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 a Sovereign Private Cloud solution on Azure Local
Choose connected vs disconnected operations for sovereign requirements
Run on-premises sovereign AI with Foundry Local (models, BYOM, inference)
Rules
Prefer the vendored docs under docs/upstream/azure-sovereign-clouds/private/; cite the exact file used.
Map sovereign requirements to private-cloud scenarios before choosing an operations model.
Route air-gapped operational runbooks to azlocal-disconnected.
Microsoft Learn / discovered governance wins over the mirror on any conflict.
Steps
Overview & use cases — map sovereign requirements to private-cloud scenarios.
Operations model — choose connected or disconnected operations (see azlocal-disconnected).
Sovereign AI — deploy Foundry Local, run a first model, and plan inference/BYOM.
