Topic starter
11/12/2025 10:28 am
TL;DR: Microsoft Agent 365 adds agent IDs, lifecycle rules, policy templates, risk-based access controls, and auditability for Microsoft environments, but enterprise agents still span AWS, GCP, SaaS, CI/CD, and internal frameworks, according to Entro Security. The governance challenge is not agent identity in one stack, but cross-environment discovery, ownership, and blast-radius control.
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: How should enterprises govern AI agents across multiple clouds and SaaS platforms?
A: Enterprises should treat AI agents as distributed NHIs and govern them with a unified model for discovery, ownership, secrets, and policy enforcement across every runtime they touch.
Q: Why do single-platform agent controls still leave a governance gap?
A: Single-platform controls leave a gap because they only cover the portion of the agent lifecycle that occurs inside that platform.
Q: What signals show that agent governance is fragmented in practice?
A: The main signs are duplicate agent registries, inconsistent ownership records, unresolved secrets tied to the same agent, and separate policy views across clouds.
Practitioner guidance
- Map all agent runtimes across the enterprise Inventory agents in Azure, AWS, GCP, SaaS, CI/CD, and internal frameworks so the governance model starts with actual execution locations rather than assumed platform boundaries.
- Trace every agent credential source Identify the secrets, API keys, tokens, and delegated access paths that power each agent, then assign an owner to each credential source and downstream dependency.
- Consolidate cross-environment entitlement visibility Build one view of agent permissions across clouds and applications so entitlement drift does not hide behind separate vendor consoles or local admin boundaries.
Bottom line: Microsoft Agent 365 improves agent governance inside Microsoft ecosystems, but that does not close the wider enterprise control gap.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 10 months ago 3 times by Abdelrahman
This topic was modified 6 days ago by NHI Mgmt Group
06/10/2026 8:38 pm
Cross-environment agent governance is now the baseline problem, not an advanced use case. Microsoft Agent 365 shows that the industry now accepts AI agents as identities, but identity without enterprise-wide visibility remains a local control. The gap is not conceptual. It is operational, because agents already span Microsoft, AWS, GCP, SaaS, and internal frameworks. Practitioners should assume the governance problem starts at discovery, not at policy definition.
A few things that frame the scale:
- 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 happens when an AI agent is given permissions in one environment but operates in many?
A: The agent can act like a distributed non-human identity with a larger effective blast radius than the local control plane assumes. Permissions that look narrow in one system may combine with tokens, connectors, and delegated services elsewhere. The result is overreach that becomes hard to contain because ownership is split across platforms.
👉 Read our full editorial: Microsoft Agent 365 and the cross-environment AI agent control gap