Topic starter
01/07/2026 2:07 am
TL;DR: Agent identities sit at the centre of a fast-moving governance problem because attackers already target identity systems to control access, and Microsoft’s Agent ID preview still leaves changing behaviours and APIs in play, according to Semperis. The critical gap is that agent identities are not people, so human IAM assumptions no longer hold.
Editorial analysis by NHI Mgmt Group, based on content published by Semperis: “Understanding and Preventing Entra ID Agent Identity Attacks: A Comprehensive Guide”.
Key questions
Q: What breaks when Entra ID agent identities are managed like human accounts?
A: Human account governance assumes a stable person, predictable approval chains, and reviewable behaviour.
Q: Why do preview-stage agent identity features create governance risk?
A: Preview-stage features can change token claims, APIs, and registration behaviour while teams are still defining policy.
Q: How should IAM teams scope permissions for agent identities?
A: Scope permissions by named business function, not by broad platform convenience or presumed workload similarity.
Practitioner guidance
- Classify agent identities separately from human users Create a distinct governance category for agent identities so access requests, ownership, and lifecycle decisions are not forced through human-only workflows.
- Test claims and token behaviour before production use Validate how registrations, claims, and permissions behave in a non-production tenant while Microsoft’s Agent ID features are still changing.
- Map every agent permission to an explicit business purpose Require a named service objective for each permission set so reviewers can judge whether the agent’s effective scope is justified.
Bottom line: Agent identities in Entra ID expose a control gap because human IAM assumptions do not cleanly apply to software subjects.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
01/07/2026 2:29 am
Agent identities expose an assumption gap, not just an implementation gap. Identity programmes were built on the assumption that the subject is either a person or a clearly bounded workload with stable ownership. Once an agent can act through Entra ID, that assumption becomes fragile because the subject may generate, combine, and use access in ways that are not visually or operationally similar to human IAM. Practitioners should treat this as a control-model mismatch, not a cosmetic extension of existing account management.
A few things that frame the scale:
- 88% of organisations have embedded AI agents in their workflows, according to KPMG's 2026 report.
A question worth separating out:
Q: When should organisations re-evaluate identity controls for AI agents and non-human identities?
A: They should re-evaluate them as soon as delegated access, autonomous decision-making, or machine-to-machine trust enters production. At that point, human-centred review cycles are no longer enough, because access can be used in ways that are not tied to a predictable person or session.
👉 Read our full editorial: Entra ID agent identities expose the next IAM control gap