What problem does it solve?
This Skill prevents developers from accidentally deploying to the wrong Azure tenant or subscription when running multiple concurrent terminals, scripts, or agent sessions on the same machine.
Core Features & Use Cases
- Per-tenant isolation for Azure CLI and AZD: Forces tenant-scoped state via
AZURE_CONFIG_DIR and AZD_CONFIG_DIR, avoiding shared ~/.azure and ~/.azd collisions.
- Verify-before-act guardrails: Requires an explicit tenant + subscription assertion immediately before any destructive action like
azd up, azd deploy, az deployment ... create, az group create, or deletes.
- Index-driven tenant selection: Uses a personal JSON tenant index (optionally overridden by
AZURE_TENANT_INDEX) to map aliases to tenant IDs, config directories, and allowed subscriptions.
- Safe auth behavior: Enforces
az login --tenant <id> and azd auth login --tenant-id <id>, and avoids re-login when tokens are already valid.
Quick Start
Set AZURE_CONFIG_DIR and AZD_CONFIG_DIR from the tenant index alias you want, then run your azd up workflow only after the tenant+subscription assertion passes.