Topic starter
28/04/2026 4:17 pm
TL;DR: Microsoft Agent Identity Platform preview adds agent identities to Entra ID and a new Agent ID Administrator role, but Silverfort found that the role could take ownership of arbitrary service principals and then add credentials for full takeover before Microsoft fixed it. The boundary error shows how new NHI controls can inherit old privilege paths if scoping is not exact.
Editorial analysis by NHI Mgmt Group, based on content published by Silverfort: “Agent ID Administrator scope overreach: Service Principal takeover in Entra ID”.
By the numbers:
- 99% of orgs have at least one privileged service principal; over half use agent identities (of those, almost half have 100+).
Key questions
Q: What breaks when an agent identity role can affect non-agent service principals?
A: The boundary between agent governance and application governance breaks, and ownership becomes a takeover primitive.
Q: Why do privileged service principals make role-scope gaps so dangerous?
A: Because the attacker does not need to create new privilege, only inherit what the target already has.
Q: How can security teams tell whether identity role scoping is working?
A: Look for consistent enforcement by object type, not just by role name or documentation.
Practitioner guidance
- Audit service principal ownership paths Review who can become owner of non-agent service principals and verify that new identity roles cannot cross object-family boundaries.
- Monitor credential creation on high-value principals Alert on any new secret or certificate added to service principals that hold directory roles or high-impact Graph permissions.
- Separate agent identity administration from application administration Ensure roles created for AI agent management cannot modify owners, credentials, or permissions on general service principals.
Bottom line: A role intended for agent identities was able to cross its boundary and manipulate non-agent service principals, exposing a real scoping failure.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 6 days ago by NHI Mgmt Group
06/10/2026 9:39 pm
Scope drift in a new identity role is still a privilege escalation problem. The most important lesson is not that Microsoft added a new agent control plane, but that the control plane reused a shared service principal surface without preserving the intended boundary. That is a classic governance failure in NHI design: a role name suggests narrow authority, while the underlying object model still permits broader control. Practitioners should treat boundary accuracy as a first-class security requirement.
A few things that frame the scale:
- 19% of organisations give AI systems dramatically more access than human employees, nearly one in five granting unrestricted privilege, according to the 2026 Infrastructure Identity Survey.
- Only 44% of organisations have implemented any policies to manage their AI agents, despite 92% agreeing that governing AI agents is critical to enterprise security, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What should teams do when new AI agent identities share directory primitives with existing apps?
A: Treat the shared primitives as a boundary-testing requirement before rollout. Separate the permissions that manage agent identities from the permissions that manage general service principals, then confirm the enforcement layer blocks cross-object inheritance. Without that test, a new identity type can inherit old privilege paths and widen the attack surface.
👉 Read our full editorial: Agent ID Administrator scope gaps expose service principal takeover risk