Topic starter
14/07/2026 4:26 pm
TL;DR: Microsoft’s Agent Registry centralises discovery, ownership, and governance for AI agents, while Entra Agent ID governs identity, permissions, and token issuance across autonomous, OBO, and user-context flows, according to Semperis. The core issue is that registry visibility and identity enforcement are separate control planes, so governance fails if teams treat them as interchangeable.
Editorial analysis by NHI Mgmt Group, based on content published by Semperis: “The Agent Registry and How Agent Identities Operate in Entra ID”.
Key questions
Q: How should teams govern AI agents when inventory and identity controls are split?
A: Treat the registry as discovery and lifecycle visibility, and treat Entra Agent ID as the enforcement layer for authentication and permissions.
Q: When does a registry review fail to prove an agent is actually controlled?
A: A registry review fails whenever it shows an agent exists, but does not prove that the agent can or cannot obtain tokens.
Q: What breaks when teams block an agent in the registry but leave Entra identity unchanged?
A: Users may be prevented from installing or using the agent in supported Microsoft 365 experiences, but the underlying identity posture can still be inconsistent.
Practitioner guidance
- Separate registry governance from identity governance Document which team owns inventory, ownership, publication status, and user-facing blocking in the Agent 365 registry, and which team owns Entra Agent ID, token issuance, and access policy enforcement.
- Map each agent to its authentication flow Classify agents as autonomous, OBO, or user-context and record the exact token exchange path, credential type, and resource scope for each.
- Review registry-only agents separately Build a governance queue for agents that appear in the registry but do not have a first-class Entra identity, so they are not lost in identity-only recertification cycles.
Bottom line: Microsoft’s model separates registry governance from identity enforcement, so visibility alone does not prove an AI agent is controlled.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
14/07/2026 4:33 pm
Registry visibility is not identity enforcement. Microsoft’s model confirms a control split that many IAM programmes still blur: discovery, ownership, and lifecycle visibility live in one plane, while token issuance and permissions live in another. That distinction matters because governance can look complete even when identity controls are untouched. Practitioners should stop treating registry coverage as proof of agent control.
A question worth separating out:
Q: How do OBO and autonomous agent flows change access governance?
A: OBO adds a human user token into the exchange, so the agent’s access is partly shaped by delegated user context, while autonomous flows rely on the agent’s own credentials and resource token path. The governance difference is material because the review question changes from user delegation to machine-issued privilege. Teams need flow-specific policy and audit evidence.
👉 Read our full editorial: Microsoft Agent Registry and Entra ID: what it changes for governance