Part 1 covered the front door: an agent sends an RFC 8693 exchange request and the broker checks it against a resource map.

This part covers what happens next. The broker has to produce an Entra token that Graph or another API will accept, for the

right user, acting through the right agent. That turns out to need more than a client secret, and this part explains why.

The pieces in Entra

Microsoft's Agent ID feature gives an AI agent its own identity in Entra. Three objects matter here.

An agent identity blueprint. An application object that describes a kind of agent: its name, what it may do, and which Graph permissions its agents may inherit. Blueprints are the templates. The blueprint has its own certificate credential, an identifier URI of the form api://<appId> , and a delegated scope called access_as_user .

Agent identities. Each is created from a blueprint and represents one running agent. An agent identity is a service principal, so it can be granted access and audited on its own.

The user.…