Topic starter
11/05/2026 8:41 pm
TL;DR: Microsoft Agent 365 adds useful identity primitives for AI agents, including agent IDs, lifecycle rules, policy templates, risk-based access, and auditability, according to Entro Security, but it remains bounded by the Microsoft ecosystem while enterprise agents run across Azure, AWS, GCP, SaaS, CI/CD, and AI platforms. Cross-environment governance, not isolated agent administration, is the real control problem.
Editorial analysis by NHI Mgmt Group, based on content published by Entro Security: “Microsoft Agent 365 Pushes AI Identity Forward but Enterprise Agents Still Need Cross-Environment Control”.
Key questions
Q: What breaks when AI agents are governed separately in each cloud?
A: Separate governance breaks the attack narrative.
Q: Why do AI agents create more identity risk than ordinary SaaS integrations?
A: AI agents can operate continuously, chain multiple tools, and act on delegated permissions with little human oversight.
Q: How do security teams know if agent governance is actually working?
A: It is working only if the team can answer three questions quickly for any agent: what it can reach, what it did recently, and whether that behaviour matches intent.
Practitioner guidance
- Map agent identity ownership across every runtime Inventory AI agents across Azure, AWS, GCP, SaaS, CI/CD, and internal frameworks, then assign a named owner and lifecycle state to each one.
- Scope agent privileges to the narrowest enforceable context Review each agent's secrets, tokens, and entitlements to confirm the access model is enforceable outside the environment where it was issued.
- Unify discovery before enforcing policy templates Build a cross-environment view of sanctioned and shadow agents first, then apply policy templates only after the estate can be seen end to end.
Bottom line: Microsoft Agent 365 gives AI agents formal identity primitives, but the enterprise problem remains wider than any single cloud control plane.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
11/05/2026 8:42 pm
Microsoft Agent 365 validates the need for identity-grade AI agent governance, but it does not solve the enterprise boundary problem. Agent IDs, lifecycle rules, and auditability are the right primitives for treating agents as non-human identities. The problem is that enterprise agents do not respect product boundaries, so a Microsoft-native control plane only covers part of the operational surface. The implication is that AI agent governance has to be designed as an estate-wide discipline, not a single-platform feature.
A few things that frame the scale:
- 70% of organisations grant AI systems more access than they would give a human employee performing the exact same job, 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: What should teams do when agent identities are scattered across tools and clouds?
A: They should start by building a complete inventory of sanctioned and shadow agents, then map secrets, entitlements, and ownership to each one. Without that foundation, policy templates and audit trails are applied to an incomplete estate, which leaves unmanaged agent activity outside the control boundary. Discovery has to come before enforcement.
👉 Read our full editorial: Microsoft Agent 365 raises the bar on AI agent identity governance