Agent Identities: Design Deep Dive

Semperis practice checkpoint two wires up the Entra ID agent permission model: direct app-only roles on the agent identity plus inheritable delegated permissions granted at the blueprint level.

A hands-on checkpoint walking through Entra ID's three agent authentication flows (autonomous, OBO, agent-user), decoding tokens to show how claims map to blueprints, identities and permissions.

Chapter six of Semperis' Entra ID agent-identity guide covers common misconfigurations: agent IDs without owners or sponsors, blueprints relying on client secrets, and over-privileged agents.

Chapter five of the Semperis guide explains Microsoft's Agent Registry as the inventory and governance plane for agents, distinct from Entra Agent ID, and how agents authenticate in three flows.

Semperis' first practice checkpoint builds a real Entra ID Agent ID object set — blueprint, blueprint principal, credentials, agent identity and agent user — using Microsoft Graph and PowerShell.

Semperis found Entra ID's Directory.ReadWrite.All permission can be abused to escalate privileges, disrupt services, or take over a tenant—the Hidden Consent Grant attack, rated potentially severe.