Topic starter
04/06/2026 6:43 pm
TL;DR: PlainID says expanded support for AWS AgentCore and Microsoft Foundry extends agent registry, discovery, enrichment, management and enforcement across enterprise agent environments, as organisations move from experimentation to production-scale deployments and need consistent authorization across data, MCP tools and actions.
Editorial analysis by NHI Mgmt Group, based on content published by PlainID: “PlainID Expands Support for AWS AgentCore and Microsoft Foundry Across Its Agentic Security and Authorization Platform”.
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 native agent controls fall short once an AI agent reaches other systems?
A: Native controls are usually scoped to one platform, so they stop being authoritative when an agent calls into internal enterprise systems, external tools, or another cloud.
Q: Should IAM teams be involved in AI agent governance from the start?
A: Yes, because AI agents inherit access, secrets, and revocation problems that are already IAM concerns.
Practitioner guidance
- Define an independent authorization layer Separate policy decisions from any single agent platform so authorization can be applied consistently across AWS AgentCore, Microsoft Foundry, internal systems, data, and tools.
- Inventory and classify every agent Create a live registry that captures ownership, platform, connected resources, and policy scope for each agent before production rollout.
- Enrich agent profiles with business context Attach business purpose, data sensitivity, and tool relationships to each agent record so policy decisions are based on context rather than platform labels.
Bottom line: Agentic AI governance now depends on consistent authorization across platforms, not just on securing a single agent runtime.
What's in the full announcement
PlainID's full article covers the operational detail this post intentionally leaves for the source:
- Expanded platform coverage details for AWS AgentCore and Microsoft Foundry support
- The vendor's description of how registry, discovery, enrichment, management, and enforcement fit together
- PlainID's framing of independent authorization across AWS, Microsoft, and internal systems
- The specific enterprise use cases the article says benefit from broader agent coverage
👉 Read PlainID's analysis of agentic identity governance across AWS AgentCore and Microsoft Foundry →
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
04/06/2026 6:54 pm
Agentic identity governance is becoming a control-plane problem, not a product feature problem. Once enterprises deploy agents across multiple platforms, the decisive issue is whether authorization follows the agent across systems. Platform-native guardrails can help locally, but they do not solve governance once the agent crosses into enterprise data or another cloud boundary. Practitioners should evaluate agent governance as an independent policy layer, not as an extension of whichever platform built the agent.
A few things that frame the scale:
- Only 5.7% of organisations have full visibility into their service accounts, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: What is the difference between platform-native guardrails and independent authorization for agents?
A: Platform-native guardrails protect actions inside one vendor environment, while independent authorization governs the agent across environments. The first is perimeter control, the second is a portable policy model that stays effective when the agent crosses into other systems or cloud boundaries.
👉 Read our full editorial: Agentic identity governance expands across AWS AgentCore and Foundry