> ## Documentation Index
> Fetch the complete documentation index at: https://labs.prompthon.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Enterprise Agent Control Planes

<div className="not-prose my-4 rounded-md border border-gray-200 bg-gray-50 p-2 text-sm dark:border-gray-800 dark:bg-gray-900/40">
  <div className="mb-2 px-1 text-xs font-semibold uppercase tracking-wide text-gray-500 dark:text-gray-400">Need help?</div>

  <div className="flex flex-wrap gap-2">
    <a className="inline-flex items-center gap-2 rounded-md border border-gray-200 bg-white px-3 py-1.5 font-medium text-gray-700 no-underline shadow-sm hover:border-gray-300 hover:bg-gray-50 dark:border-gray-800 dark:bg-gray-950/60 dark:text-gray-200 dark:hover:bg-gray-900" href="https://discord.gg/sDE2HhGTg4" target="_blank" rel="noreferrer">
      <Icon icon="discord" iconType="brands" size={14} />

      <span>Ask in Discord</span>
    </a>

    <a className="inline-flex items-center gap-2 rounded-md border border-gray-200 bg-white px-3 py-1.5 font-medium text-gray-700 no-underline shadow-sm hover:border-gray-300 hover:bg-gray-50 dark:border-gray-800 dark:bg-gray-950/60 dark:text-gray-200 dark:hover:bg-gray-900" href="https://github.com/Prompthon-IO/agent-systems-handbook/issues/new/choose" target="_blank" rel="noreferrer">
      <Icon icon="github" iconType="brands" size={14} />

      <span>Open a GitHub issue</span>
    </a>

    <a className="inline-flex items-center gap-2 rounded-md border border-gray-200 bg-white px-3 py-1.5 font-medium text-gray-700 no-underline shadow-sm hover:border-gray-300 hover:bg-gray-50 dark:border-gray-800 dark:bg-gray-950/60 dark:text-gray-200 dark:hover:bg-gray-900" href="https://github.com/Prompthon-IO/agent-systems-handbook/blob/main/SUPPORT.md" target="_blank" rel="noreferrer">
      <Icon icon="life-ring" size={14} />

      <span>Support guide</span>
    </a>
  </div>
</div>

## Summary

This note gives contributors a compact source map for two related
enterprise-agent comparison axes: the managed runtime around agents and the
control plane across them.

The immediate triggers are Microsoft's April 28, 2026 framing around
`Intelligence + Trust`, where Microsoft IQ carries business context and Agent
365 carries observability, governance, and security across both Microsoft's own
agent surfaces and third-party environments, AWS's April 28, 2026 launch
framing for Bedrock Managed Agents and AgentCore, and Anthropic's June 2026
Claude Partner Network signals around TCS and DXC bringing Claude into
regulated and mission-critical enterprise systems.

## Why It Matters

Agent-platform comparisons often collapse into model access, orchestration UX,
or framework ergonomics. That misses two different buying questions:

* how much of the runtime should stay managed for the team
* who operates the deployment surface inside regulated industries
* how does an organization observe, govern, and secure a growing set of agents
  that span multiple runtimes and vendors?

This note helps contributors keep two layers separate:

* the managed-runtime layer that handles inference, memory, execution, and
  runtime security for one agent workload
* the partner-delivery layer where consultancies, systems integrators, and
  forward-deployed engineers adapt agent systems to industry-specific
  controls, legacy estates, and compliance requirements
* the control-plane layer that enforces trust, visibility, and policy across
  many agents and environments

It also helps preserve a third boundary:

* the open framework layer where teams still choose their orchestration model
  and application architecture directly

That three-way split is becoming more useful than a simple "which model?"
comparison.

## Scope Notes

Included:

* Microsoft's current commercial framing for `Intelligence + Trust`
* Microsoft IQ as the context and intelligence layer
* Agent 365 as the observability, governance, and security layer
* AWS's launch framing for Bedrock Managed Agents
* AgentCore as the underlying open platform beneath the managed runtime
* Anthropic's Claude Partner Network framing for TCS and DXC deployments in
  regulated industries
* implications for later ecosystem and systems refreshes in this repo

Excluded:

* detailed product implementation walkthroughs
* a broad vendor scorecard across every agent platform
* protocol-level interoperability analysis, which belongs elsewhere in
  `radar/`

## Source Map

* [Unlocking human ambition to drive business growth with AI](https://blogs.microsoft.com/blog/2026/04/28/unlocking-human-ambition-to-drive-business-growth-with-ai/):
  Microsoft's April 28, 2026 post says the two most important elements in an
  AI solution are `Intelligence + Trust`, positions Microsoft IQ as the context
  layer around data and agent development, and positions Agent 365 as the
  observability, governance, and security layer across Microsoft and
  third-party agent environments.
* [Amazon Bedrock now offers OpenAI models, Codex, and Managed Agents (Limited Preview)](https://aws.amazon.com/about-aws/whats-new/2026/04/bedrock-openai-models-codex-managed-agents/):
  AWS positions Bedrock Managed Agents as a fast path to deploy
  production-ready OpenAI-powered agents on AWS, with each agent getting its
  own identity, action logging, and an AgentCore-backed default compute
  environment.
* [Amazon Bedrock Managed Agents](https://aws.amazon.com/bedrock/managed-agents-openai/):
  the product page says the managed runtime handles inference, memory, and
  skills inside the customer's environment and connects the managed surface to
  future AgentCore capabilities such as authorization policy enforcement,
  discovery, observability, and evaluation.
* [Amazon Bedrock AgentCore overview](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/what-is-bedrock-agentcore.html):
  AWS describes AgentCore as an agentic platform for building, deploying, and
  operating agents securely at scale using any framework and foundation model,
  with runtime, memory, identity, observability, and gateway services.
* [awslabs/agentcore-samples](https://github.com/awslabs/agentcore-samples):
  the official AWS sample repo shows that AgentCore is not only a marketing
  label; it already has a substantial code surface for hosted runtimes,
  gateways, memory, observability, browser tooling, and evaluation.
* [microsoft/agent-framework](https://github.com/microsoft/agent-framework):
  the official Microsoft framework repo gives contributors a useful contrast
  point between an open framework surface and Microsoft's separate Agent 365
  control-plane positioning.
* [TCS and Anthropic partner to bring Claude to regulated industries](https://www.anthropic.com/news/tcs-anthropic-partnership):
  Anthropic says TCS will use Claude internally, build Claude-powered products
  for clients in financial services, healthcare, public services, aviation,
  telecom, medical technology, and other regulated industries, and create
  reusable Claude Code skills and plugins for domains such as claims
  adjudication and lending advisory.
* [DXC will integrate Claude into the systems banks, airlines, and other regulated industries rely on](https://www.anthropic.com/news/dxc-anthropic-alliance):
  Anthropic frames DXC as a forward-deployed engineering partner that will
  bring Claude into long-running customer systems for banks, airlines,
  insurers, manufacturers, and government agencies, with DXC OASIS and its
  agentic workflows as an internal proof point.
* [Anthropic invests \$100 million into the Claude Partner Network](https://www.anthropic.com/news/claude-partner-network):
  the network page positions partners as the delivery and adoption layer that
  helps enterprises navigate deployment requirements, compliance, change
  management, training, certification, and production rollout.

## Synthesis

Five contributor-facing takeaways matter most:

* Enterprise agent discussion is shifting beyond model choice. AWS is pushing a
  managed-runtime story, while Microsoft is pushing a control-plane story.
* Trust is being positioned as cross-environment infrastructure, not only as a
  property of one assistant or one runtime. That suggests contributors should
  separate local runtime capability from fleet-level governance.
* Managed runtime is becoming a distinct comparison layer. Bedrock Managed
  Agents packages inference, memory, execution, and auditability inside a
  hosted environment before the question becomes "which framework should we
  write?"
* Partner delivery is becoming its own enterprise-agent layer. Anthropic's TCS
  and DXC announcements are less about a new model interface and more about
  who carries Claude into regulated business processes, legacy systems,
  reusable skills, certification, and ongoing operation.
* A useful lab comparison axis is emerging: open framework, managed runtime,
  partner delivery, and control plane. That split can sharpen both systems
  pages and ecosystem pages without hard-coding one vendor's naming.

For the handbook, the durable lesson is not the vendor label. It is the
category boundary that contributors should preserve when comparing agent
platforms and enterprise deployment stories.

## Related Handbook Paths

* [Reference Notes](/contributor-kit/reference-notes)
* [Agent Platforms And Low-Code Builders](/ecosystem/agent-platforms-and-low-code-builders)
* [Evaluation And Observability](/systems/evaluation-and-observability)
* [Protocols And Interoperability](/systems/protocols-and-interoperability)

## Gaps And Follow-up

* Revisit [Systems: Evaluation and Observability](/systems/evaluation-and-observability)
  with a short section that distinguishes runtime instrumentation from
  organization-level control planes and from managed-runtime defaults.
* Revisit [Agent Platforms And Low-Code Builders](/ecosystem/agent-platforms-and-low-code-builders)
  if more official sources begin using managed runtime versus control plane as a
  stable comparison frame.
* Revisit ecosystem pages if partner networks, certifications, and
  forward-deployed engineering practices become durable comparison criteria for
  enterprise agent platforms.
* Add future sources when other first-party platforms describe comparable
  managed-runtime or fleet-governance surfaces explicitly enough to compare
  without guesswork.

## Update Log

* 2026-06-14: Added Anthropic's TCS, DXC, and Claude Partner Network signals
  so contributors can compare partner-delivery layers alongside managed
  runtimes and control planes for regulated enterprise agent deployments.
* 2026-05-03: Expanded the note with AWS Bedrock Managed Agents and AgentCore
  so contributors can separate open frameworks, managed runtimes, and control
  planes.
* 2026-04-29: Added a contributor-facing note on enterprise agent control
  planes using Microsoft's `Intelligence + Trust` framing as the current source
  spine.