Microsoft Entra Agent ID on Kubernetes
Welcome to the comprehensive guide for setting up Microsoft Entra Agent ID on Kubernetes.
Microsoft Entra Agent ID is a new feature for Microsoft Entra that adds support for “AI Agent” workloads. This set of guides will specifically dive deeply into how it works (its full token-exchange mechanism) with the goal of getting it working on Kubernetes (not necessarily AKS, but would apply there too) for Agent and MCP workloads.
Multi-Part Series
This comprehensive series walks through Entra Agent ID from basics to production deployment:
- Part One: Understanding Entra Agent ID - Learn the fundamentals of Entra Agent ID, blueprints, and agent identities
- Part Two: Agent On-Behalf-Of User - Deep dive into OBO token exchange mechanisms
- Part Three: Running on Kubernetes - Deploy the Entra SDK sidecar on Kubernetes
- Part Four: Workload Identity Federation - Eliminate client secrets with workload identity federation
- Part Five: LLM and MCP with Entra Agent ID and AgentGateway - Full working example with AI agents, LLMs, and MCP servers
For additional guides, setup instructions, and reference documentation, visit the GitHub repository.
If you’re interested in updates on this topic, please follow @ceposta on LinkedIn.