{"id":793,"date":"2026-11-19T19:30:46","date_gmt":"2026-11-19T19:30:46","guid":{"rendered":"https:\/\/www.algofuse.ai\/blog\/agent-365-goes-multiplatform-what-a-unified-agent-control-plane-actually-controls\/"},"modified":"2026-11-19T19:30:46","modified_gmt":"2026-11-19T19:30:46","slug":"agent-365-goes-multiplatform-what-a-unified-agent-control-plane-actually-controls","status":"publish","type":"post","link":"https:\/\/www.algofuse.ai\/blog\/agent-365-goes-multiplatform-what-a-unified-agent-control-plane-actually-controls\/","title":{"rendered":"Agent 365 Goes Multiplatform: What a Unified Agent Control Plane Actually Controls"},"content":{"rendered":"<p>Most enterprises did not decide to run agents on five platforms. It happened one team at a time. Sales built something in Salesforce Agentforce, data engineering stood up a Genie space in Databricks, a product group shipped on Amazon Bedrock, and a developer quietly installed Claude Code on a laptop.<\/p>\n<p>Each choice made sense locally. Together they produced a problem no single vendor console can see: nobody can answer &#8220;how many agents do we have, who owns them, and what can they touch?&#8221;<\/p>\n<p>That is the gap Microsoft Agent 365 is aimed at. Since general availability on May 1, 2026, it has moved from a Microsoft-centric registry toward a multiplatform control plane. This article looks at what that means in practice, what is verified, where public sources disagree, and how to decide whether a cross-platform control plane belongs in your stack.<\/p>\n<p><em>A note on sourcing: figures below come from Microsoft&#8217;s published materials and secondary reporting. Where sources conflict, we say so. Verify licensing and connector status with your Microsoft account team before committing budget.<\/em><\/p>\n<p><img decoding=\"async\" src=\"https:\/\/szukdzugaodusagltwla.supabase.co\/storage\/v1\/object\/public\/marketing-media\/f71482aa-ece0-4f48-be89-4a95e0933103\/f9823da7-c5d9-46dc-985a-18960a183139\/image\/1795116416483.png\" alt=\"Central agent registry connected to Amazon Bedrock, Google Vertex, Salesforce Agentforce, Anthropic, Databricks and Microsoft Copilot Studio\" \/><\/p>\n<h2>What &#8220;Control Plane&#8221; Means for Agents<\/h2>\n<p>In networking and Kubernetes, the control plane decides and records; the data plane does the work. Applying that idea to agents means separating where an agent runs from where it is registered, identified, permissioned, and monitored.<\/p>\n<p>The agent still executes inside Bedrock, Vertex, Agentforce, or Copilot Studio. The control plane holds the shared metadata: owner, identity, lifecycle state, permissions, usage, and risk.<\/p>\n<h3>What it is not<\/h3>\n<p>Microsoft describes Agent 365 as a coordination layer, not a replacement for platform-specific administration. Builders keep working in Copilot Studio, Power Platform, or the AWS console. The control plane adds a shared view for security, identity, and AI administrators who previously had no common pane.<\/p>\n<p>This distinction matters. If you expect one console to author, tune, and deploy every agent, you will be disappointed. If you expect one place to answer audit and risk questions, the model fits.<\/p>\n<h3>Why a registry comes first<\/h3>\n<p>Governance without inventory is guesswork. Every later control (access reviews, threat detection, data loss prevention, retirement of stale agents) depends on knowing the agent exists. That is why the registry is the foundation and why most of the multiplatform work so far has focused on synchronizing inventories.<\/p>\n<h2>The Timeline: From Microsoft-Only Registry to Cross-Cloud Sync<\/h2>\n<p>Agent 365 reached commercial general availability on May 1, 2026. At launch, its distinctive features were a registry, Entra Agent ID identities, access controls, and discovery of local &#8220;shadow&#8221; agents through Defender and Intune. Connectors to AWS and Google Cloud arrived as public preview.<\/p>\n<p>Over the following months, reporting indicates the connectors matured. Registry synchronization for Amazon Bedrock, Google&#8217;s Gemini Enterprise agent platform, Anthropic Claude, Databricks Genie, and Salesforce Agentforce is described as generally available as of July 2026. Snowflake, Oracle OCI, and UiPath are reported as planned next.<\/p>\n<h3>Identity extends to partners<\/h3>\n<p>Microsoft has also said it is extending Entra Agent ID to agents from partners including Google, Salesforce, Databricks, Snowflake, Anthropic, OpenAI, Oracle, SAP, ServiceNow, and UiPath. Connected agents receive an Entra Agent ID, which gives them a common identity that conditional access and governance policies can reference.<\/p>\n<h3>Scale claims<\/h3>\n<p>Microsoft reports more than 50 million agents registered since launch. Treat that number carefully. Registered is not the same as active, and a large share likely reflects automatically created agents inside Microsoft&#8217;s own products. It shows adoption of the registry, not 50 million independently governed production workloads.<\/p>\n<h2>Three Discovery Paths, Not One<\/h2>\n<p>A common misunderstanding is that a control plane &#8220;finds everything.&#8221; In reality Agent 365 uses several distinct discovery mechanisms, each with different coverage and different confidence.<\/p>\n<ol>\n<li><strong>Native Microsoft agents<\/strong> built in Copilot Studio, Foundry, and related tools appear because they are born inside the tenant.<\/li>\n<li><strong>Cloud registry sync<\/strong> pulls inventories and metadata from external platforms through connectors, using permissions you grant to those clouds.<\/li>\n<li><strong>Endpoint discovery<\/strong> uses Defender and Intune, plus Global Secure Access, to spot local agents and MCP servers on managed devices.<\/li>\n<\/ol>\n<p>Each path has blind spots. Cloud sync only sees what the connector&#8217;s permissions expose. Endpoint discovery only sees managed devices. An agent running on a personal machine against a SaaS API using a personal token may appear in none of them.<\/p>\n<h2>Shadow Agents: The Real Reason Security Teams Care<\/h2>\n<p>Registry sync is the tidy part. Local agents are the messy part. Tools such as Claude Code, GitHub Copilot CLI, and OpenAI Codex run in a developer&#8217;s terminal with the developer&#8217;s credentials, often connected to MCP servers that reach internal systems.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/szukdzugaodusagltwla.supabase.co\/storage\/v1\/object\/public\/marketing-media\/f71482aa-ece0-4f48-be89-4a95e0933103\/f9823da7-c5d9-46dc-985a-18960a183139\/image\/1795116479388.png\" alt=\"Magnifying glass revealing shadow agents such as Claude Code, GitHub Copilot CLI and MCP servers on an endpoint\" \/><\/p>\n<p>Microsoft&#8217;s discovery began with OpenClaw and has expanded. Reports put coverage at more than 60 local agent types, up from roughly 20 at the earlier stage, including newly detected unknown agents flagged by security sensors.<\/p>\n<h3>What the context adds<\/h3>\n<p>The useful part is not the list of tools but the surrounding context: which device, which identity, which MCP servers, and which cloud resources the agent can reach. That turns &#8220;someone installed a CLI tool&#8221; into &#8220;this agent, under this user, can reach this storage account.&#8221;<\/p>\n<h3>From visibility to enforcement<\/h3>\n<p>Defender and Intune can block or isolate unsanctioned agent execution. Industry commentary frames this as the shift from inventory toward enforcement. Expect friction here: blocking developer tools without a sanctioned alternative tends to push usage to unmanaged devices.<\/p>\n<h2>Identity: Why Entra Agent ID Is the Load-Bearing Piece<\/h2>\n<p>Agents that share a service account or inherit a user&#8217;s full permissions are the hardest to audit. Giving each agent its own identity means actions can be attributed, permissions scoped, and access revoked without disabling a human or a shared credential.<\/p>\n<p>Microsoft positions Entra as the identity foundation and Agent 365 as the inventory and governance layer on top, with Microsoft consolidating registry experiences so the two do not compete. In practice, that means identity teams and AI teams will need to agree on who owns agent lifecycle policy.<\/p>\n<h3>Questions to settle early<\/h3>\n<ul>\n<li>Who is the accountable human owner for each agent, and what happens when that person leaves?<\/li>\n<li>What is the default permission scope for a newly registered agent?<\/li>\n<li>Which agents may access sensitive data, and who approves that?<\/li>\n<li>When is an inactive agent retired automatically?<\/li>\n<\/ul>\n<h2>Security and Data: Defender and Purview in the Bundle<\/h2>\n<p>Agent 365 is not only a list. It combines the registry and governance layer with Entra Agent ID, Defender threat protection, and Purview data controls. That bundling is deliberate: the same agent record can inform threat detection and data policy.<\/p>\n<p>For regulated organizations, the Purview angle is often decisive. Audit logs and data classification tied to an agent identity make it possible to answer a regulator&#8217;s question about which automated system accessed which records.<\/p>\n<h2>What It Costs<\/h2>\n<p>Pricing is where public information is clearest, with one caveat on prerequisites.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/szukdzugaodusagltwla.supabase.co\/storage\/v1\/object\/public\/marketing-media\/f71482aa-ece0-4f48-be89-4a95e0933103\/f9823da7-c5d9-46dc-985a-18960a183139\/image\/1795116533111.png\" alt=\"Pricing comparison of Agent 365 at $15 per user per month versus Microsoft 365 E7 at $99 per user per month\" \/><\/p>\n<ul>\n<li><strong>Agent 365 standalone add-on:<\/strong> $15 per user per month, billed annually.<\/li>\n<li><strong>Microsoft 365 E7:<\/strong> listed at $99 per user per month with Teams (reported as $90.45 without), and includes Agent 365.<\/li>\n<li><strong>Licensing model:<\/strong> per user, not per agent.<\/li>\n<li><strong>Prerequisites:<\/strong> a qualifying base such as Microsoft 365 E5\/A5, Business Premium, or the Defender and Purview suites. Microsoft sources conflict on exact requirements, so confirm.<\/li>\n<\/ul>\n<h3>Why per-user licensing is unusual<\/h3>\n<p>Per-user pricing means cost does not rise when you add the 10,000th agent. That favors organizations with many agents and a modest number of governing users. It can look expensive for a company with few agents and thousands of employees, since the license applies across users rather than to the agents themselves.<\/p>\n<p>Model it both ways: your user count times $15 times twelve, against the cost of the manual inventory and audit work it replaces.<\/p>\n<h2>What Early Adopters Report<\/h2>\n<p>Public case material is thin on quantified outcomes. Two data points stand out.<\/p>\n<p>Microsoft Digital reports visibility into more than 500,000 agents across its own environment, consolidating inventory, ownership, usage, lifecycle, and risk. It used the data to analyze adoption of its Cowork agent among 58,000 active users. Truist Financial reportedly uses Agent 365 to manage, govern, and observe more than 13,000 declarative agents.<\/p>\n<p>Notice what these examples show: inventory, ownership, and observability. They do not yet show measured reductions in incidents or cost. Microsoft&#8217;s own launch material offered no quantified customer success metrics.<\/p>\n<h2>Limits and Open Questions<\/h2>\n<p>A balanced view requires naming what a control plane cannot do.<\/p>\n<h3>Metadata sync is not deep control<\/h3>\n<p>Syncing inventory from Bedrock or Agentforce does not mean you can edit an agent&#8217;s permissions inside those platforms from Agent 365. Lifecycle controls across third-party platforms were described as planned in some materials. Test which actions are read-only versus actionable for each connector.<\/p>\n<h3>Vendor neutrality<\/h3>\n<p>A Microsoft-run control plane governing competitors&#8217; agents will always raise the question of depth and priority. Microsoft platforms get native integration; others get connectors. Evaluate parity per platform, not on the headline list.<\/p>\n<h3>Alternatives and overlap<\/h3>\n<p>Cloud providers and AI platform vendors are building their own governance consoles, and standalone AI security vendors exist. Many organizations will end up with a hybrid: a cross-platform registry plus native consoles for deep configuration.<\/p>\n<h2>A Practical Rollout Sequence<\/h2>\n<p><img decoding=\"async\" src=\"https:\/\/szukdzugaodusagltwla.supabase.co\/storage\/v1\/object\/public\/marketing-media\/f71482aa-ece0-4f48-be89-4a95e0933103\/f9823da7-c5d9-46dc-985a-18960a183139\/image\/1795116596235.png\" alt=\"Four-stage lifecycle diagram: Discover, Identify, Govern, Enforce\" \/><\/p>\n<ol>\n<li><strong>Discover.<\/strong> Connect the cloud registries you already use and turn on endpoint discovery in monitor-only mode. Expect surprises.<\/li>\n<li><strong>Identify.<\/strong> Assign an owner and an Entra Agent ID to every agent worth keeping. Flag the rest for retirement.<\/li>\n<li><strong>Govern.<\/strong> Set default permission scopes, data policies, and review cycles with identity, security, and AI teams jointly accountable.<\/li>\n<li><strong>Enforce.<\/strong> Only after a sanctioned path exists, block unsanctioned local agents and unregistered deployments.<\/li>\n<\/ol>\n<p>Skipping to enforcement is the common mistake. Blocking before you offer an approved route creates workarounds and hides the very usage you wanted to see.<\/p>\n<h2>Conclusion: Decide on the Problem, Not the Product<\/h2>\n<p>Agent 365&#8217;s multiplatform expansion reflects a real shift: agents are now spread across clouds, SaaS tools, and laptops, and governance has to span all of them. A shared registry with a common identity is a sensible first layer.<\/p>\n<p>Key takeaways:<\/p>\n<ul>\n<li>A control plane governs metadata and identity; it does not replace platform consoles.<\/li>\n<li>Three discovery paths (native, cloud sync, endpoint) each have blind spots.<\/li>\n<li>Per-user pricing at $15 per month rewards agent-heavy organizations; model your own numbers.<\/li>\n<li>Public evidence shows visibility gains, not yet measured risk reduction.<\/li>\n<li>Sequence rollout as discover, identify, govern, enforce, in that order.<\/li>\n<\/ul>\n<p>Before buying, count your agents honestly. If you cannot, that is your answer about whether you need a control plane.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Microsoft Agent 365 now syncs agents from AWS, Google, Salesforce and more. Here is what a unified control plane covers, costs, and still can&#8217;t do.<\/p>\n","protected":false},"author":1,"featured_media":792,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[510],"tags":[519,80,136,517,486],"class_list":["post-793","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ai-automation","tag-agent-365","tag-ai-agents","tag-ai-governance","tag-microsoft-entra-agent-id","tag-shadow-ai"],"_links":{"self":[{"href":"https:\/\/www.algofuse.ai\/blog\/wp-json\/wp\/v2\/posts\/793","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.algofuse.ai\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.algofuse.ai\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.algofuse.ai\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.algofuse.ai\/blog\/wp-json\/wp\/v2\/comments?post=793"}],"version-history":[{"count":0,"href":"https:\/\/www.algofuse.ai\/blog\/wp-json\/wp\/v2\/posts\/793\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.algofuse.ai\/blog\/wp-json\/wp\/v2\/media\/792"}],"wp:attachment":[{"href":"https:\/\/www.algofuse.ai\/blog\/wp-json\/wp\/v2\/media?parent=793"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.algofuse.ai\/blog\/wp-json\/wp\/v2\/categories?post=793"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.algofuse.ai\/blog\/wp-json\/wp\/v2\/tags?post=793"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}