Topic starter
24/09/2026 1:22 pm
TL;DR: Nexis argues that AI agents in Microsoft environments are already accumulating permissions, roles, and group memberships, while governance still treats them as isolated technical objects instead of accountable identities. The real control gap is combined human and agent access, which can create segregation-of-duties conflicts that separate reviews never expose.
Editorial analysis by NHI Mgmt Group, based on content published by Nexis: “Your AI Agents Already Have Access. Is Your Governance Keeping Up?”.
Key questions
Q: What breaks when AI agents are reviewed like human users?
A: Human review assumes access is stable long enough to be observed, approved, and recertified.
Q: Why do AI agents increase segregation-of-duties risk in identity governance?
A: AI agents can hold roles, permissions, and group memberships that extend a human user’s effective reach.
Q: How should organisations assign ownership for AI agents in production?
A: Assign ownership to a named business and technical accountable party before the agent is allowed to act.
Practitioner guidance
- Inventory all active AI agents Build a dated inventory of agents in the Microsoft environment, including origin, intended purpose, and the systems each one can reach.
- Map combined human and agent access Review employee access and agent entitlements together so that segregation-of-duties conflicts created by paired access are visible before approval.
- Assign ownership before production use Require a registered owner for every agent, then tie that owner to existing governance workflows for accountability and review.
Bottom line: AI agents are becoming governed access actors, which means identity programmes must track them alongside human users and not as isolated tools.
What's in the full article
Nexis' full article covers the operational detail this post intentionally leaves for the source:
- The Microsoft tenant assessment workflow used to inventory AI agents and map their reach
- The four review areas, including ownership, access concentration, and cross-identity SoD
- The baseline and benchmark outputs intended for technical and management stakeholders
- The questions the health check uses to judge whether agent permissions are appropriate for purpose
👉 Read Nexis' analysis of AI agent governance and enterprise access sprawl →
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
24/09/2026 1:23 pm
AI agent governance fails when organisations treat agents as technical objects instead of accountable identities. That is the central control error this article exposes. Ownership, entitlement rationale, and relationship visibility are not optional metadata; they are the difference between inventory and governance. The practical conclusion is that AI agents belong inside the same identity governance model as the people who operate them.
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.
- 53% of security leaders expect AI to run major portions of their infrastructure autonomously within the next three years, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: How do teams know if AI access is too broad?
A: AI access is too broad when a tool can read, write, and export data beyond the immediate task or when the credential remains valid after the use case changes. Teams should look for persistent tokens, shared access paths, and permissions that survive the original business need. Those are the signs of unmanaged standing access.
👉 Read our full editorial: AI agent governance is lagging behind enterprise access sprawl