Managed Identities — Credentials for Azure Workloads
How Azure workloads authenticate without secrets: system- vs user-assigned identities, the IMDS and App Service token endpoints, token caching and rate limits, federated identity credentials for GitHub Actions and AKS, and the 400s, 401s and 403s that come from the wrong resource, a missing role or a slow cache.
Sign up free to read the full topic
More Cloud topics
- Lambda Advanced — SnapStart, Concurrency and Tuning
- Lex — Conversational AI
- Lightsail — Simplified Cloud for Small Workloads
- Logic Apps — Integration Workflows
- Macie — S3 Data Security and Privacy
- Managed Grafana
- Managed Service for Prometheus
- MemoryDB — Durable In-Memory Database
- Migration Hub — Migration Planning and Tracking
- Multi-Cloud & Hybrid Architecture
- Neptune — Managed Graph Database
- Network Firewall — Managed VPC Inspection
Start free on Cariara · Coding problems · System design studio