Presenting Entra Agent ID at the EMEA AI Bootcamp
Agents are changing how enterprises operate, and identity is central to governing them securely. I had the chance to present at a virtual EMEA bootcamp on the Microsoft Entra Suite and Entra Agent ID, a couple of days of internal readiness sessions for over 100 attendees across the Gulf, Europe, and Africa, mostly architects and security engineers preparing to take agent identity to enterprise customers.
The session
My session focused on AI agent security with Entra Agent ID. I led a deep dive into the architecture and design, walked the end to end flow of how an agent is issued an identity, granted scoped access, and continuously evaluated, and showed how it fits holistically into the broader Microsoft security and AI ecosystem. A practical, demo led look at securing agents from first principles rather than slideware.
Why agent identity matters
As autonomous AI agents take on real work inside the enterprise, each one needs a verifiable identity, scoped access, and continuous evaluation. Entra Agent ID extends proven identity governance to agents so teams can grant least privilege, audit what an agent did, and revoke access the moment it is no longer needed. The same Zero Trust principles that govern people now govern agents.
It was a real team effort. I presented alongside a great colleague, with several others covering the broader Entra Suite, and the interest from across the region was energizing. Thanks to Seda, GTM Manager at Microsoft in Dubai, who organized and ran the bootcamp, and to everyone who joined for two well run days.
Learn more
- Overview and docs: aka.ms/EntraAgentID
- Pro-dev samples: GitHub samples
- A365 SDK and CLI: aka.ms/a365SDK
For the full recap, photos, and the conversation, see my LinkedIn post. Good to see how much the region is investing in securing the agent era.
Read next
- Digital Identity
Entra Agent ID Across Clouds: Part 5, Anti-Patterns
Final article in the five-part series on running Microsoft Entra Agent ID against third-party clouds. Closes the loop with the variants and failure modes that consume the same operational budget as the federated pattern without delivering its security properties, and ends with the takeaways worth pinning to the team wiki.
- Digital Identity
Entra Agent ID Across Clouds: Part 4, FIC, Cross-Tenant, and OBO
Fourth article in the five-part series on running Microsoft Entra Agent ID against third-party clouds. Opens up the Federated Identity Credential as a first-class object: single-tenant, cross-tenant SaaS shape, and the orthogonal world of on-behalf-of (OBO) where the agent acts for a signed-in user.
- Digital Identity
Entra Agent ID Across Clouds: Part 3, Managed Identity and Entra Objects
Third article in the five-part series on running Microsoft Entra Agent ID against third-party clouds. Pins down what the UAMI actually is in this architecture, why SAMI breaks federation, the three distinct Entra objects (UAMI, Blueprint, Agent Identity) and the three claims (sub, azp, oid) they each populate, and the production trade-off between federating the UAMI or the Agent Identity to the cloud.
Worth reading again?
Get the next one in your inbox.