← ClaudeAtlas

azure-authlisted

Container-adapted Azure CLI authentication. Supports managed identity, service principal, device code, and browser login flows for headless environments. Use when the user says "login to azure", "az login", "authenticate azure", "connect subscription", or when any Azure operation fails with auth errors.
f5-sales-demo/marketplace · ★ 0 · DevOps & Infrastructure · score 71
Install: claude install-skill f5-sales-demo/marketplace
**Canonical skill URI**: `skill://azure:azure-auth` # Azure CLI Authentication (Container-Adapted) This skill guides authentication for headless container environments where browser-based login may not be available. ## Authentication Methods ### Method 1: Managed Identity (Recommended for Azure-Hosted) Best for VMs, Container Instances, App Service, and other Azure-hosted compute. No credentials needed — identity is assigned to the resource. **Command:** ```bash az login --identity --output json ``` For user-assigned managed identity: ```bash az login --identity --username <CLIENT_ID> --output json ``` ### Method 2: Service Principal (Recommended for Automation) Best for CI/CD pipelines and automated environments. Requires a registered application with client credentials. **Prerequisites:** - App registration with a client secret or certificate - `AZURE_CLIENT_ID`, `AZURE_CLIENT_SECRET`, `AZURE_TENANT_ID` set **Command:** ```bash az login --service-principal \ --username "$AZURE_CLIENT_ID" \ --password "$AZURE_CLIENT_SECRET" \ --tenant "$AZURE_TENANT_ID" \ --output json ``` For certificate-based auth: ```bash az login --service-principal \ --username "$AZURE_CLIENT_ID" \ --tenant "$AZURE_TENANT_ID" \ --password /path/to/cert.pem \ --output json ``` ### Method 3: Device Code (Headless/Container) Use when no browser is available and no service principal is configured. **Command:** ```bash az login --use-device-code --output json ``` ### Met