Field note · AWS and Azure · July 2026
Amazon Bedrock AgentCore vs Microsoft Foundry Agent Service
AWS exposes modular agent operating services. Microsoft combines hosted agents, the Responses API, Foundry tools, Entra Agent ID, API Management and enterprise publishing. The responsibilities align, but the product boundaries do not.
Modular agent runtime and operating services.
Compare responsibilities, maturity and trust boundaries.
Integrated agent and enterprise governance platform.
Do not compare product names alone
AgentCore is a collection of modular services that can be used together or attached to agents running elsewhere. Foundry Agent Service is a managed platform with prompt agents, containerized hosted agents, the Responses API and an integrated tools surface.
The useful comparison is responsibility by responsibility: where the agent runs, how it calls tools, whose identity it uses, where state lives, how actions are governed and what evidence is available.
Runtime and agent loop
AgentCore Runtime hosts custom agent containers while AgentCore Harness supplies a managed loop with isolated microVM sessions. Microsoft Foundry offers prompt agents for a fully managed loop and hosted agents for containerized Agent Framework, LangGraph, OpenAI Agents SDK, Anthropic Agent SDK, GitHub Copilot SDK or custom code.
AWS makes Harness and Runtime explicit choices. Microsoft presents prompt and hosted agents behind one Foundry Agent Service surface and a shared Responses API.
Tools and traffic governance
AgentCore Gateway converts APIs and Lambda functions into MCP tools, fronts MCP and A2A traffic and can route models. Microsoft Foundry provides a tool catalog with web search, file search, memory, code interpreter, MCP servers and custom functions.
For broader traffic governance, Azure API Management adds the AI gateway layer. It governs models, MCP servers, A2A APIs and self-hosted endpoints, including providers outside Azure. This is the closest Azure architectural match to AgentCore Gateway, but it is a separate API Management capability rather than one Agent Service module.
Identity models differ in emphasis
AgentCore Identity manages agent workload identities, delegated user access and external credentials, and it can be used with Runtime, ECS, EKS, Lambda or on-prem agents.
Microsoft Entra Agent ID represents agents as dedicated identity objects with blueprints, sponsors, lifecycle governance and delegated or autonomous token flows. Foundry automatically integrates agent identities with Entra and Azure RBAC. Microsoft is especially strong where identity governance and Microsoft 365 distribution are central requirements.
Memory, code and computer interaction
AgentCore offers Memory as a standalone service plus Browser and Code Interpreter as isolated managed tools. Foundry Agent Service exposes memory, code interpreter and other tools through its tool catalog. Computer Use exists as a separate specialized tool and must be assessed for preview status and production constraints.
In either platform, long-term memory should be scoped by user, tenant and purpose. Code and browser execution require separate network, file and credential controls.
Observability and evaluations
AgentCore Observability integrates with CloudWatch and OpenTelemetry. Evaluations can analyze sessions, traces and spans, and Optimization can use evaluation signals to improve configurations through controlled experiments.
Foundry provides traces, metrics and Application Insights integration, plus agent evaluation and trace-based evaluation. It can also register external agents that run on another cloud or on premises and associate OpenTelemetry traces with a Foundry agent record.
Governance extends beyond the runtime
AgentCore Policy integrates with Gateway and uses deterministic authorization for tool calls. AgentCore Registry catalogs agents, tools, skills, MCP servers and custom resources.
Microsoft combines Foundry publishing, Entra Agent Registry, Agent ID and Agent 365 governance. Azure API Management can register and govern agents and tools running across environments. These capabilities form an enterprise control plane rather than a single direct equivalent to AgentCore Policy or Registry.
Closest service map
Selection guide
Choose AWS when your data plane, tools and operating model already live in AWS and you want modular services that can attach to many frameworks and runtimes. Choose Microsoft when Entra identity, Microsoft 365 distribution, Azure API Management and centralized enterprise agent governance are primary advantages.
For multi-cloud estates, keep tool contracts, evaluation datasets, trace schemas and durable workflows portable. Use each cloud’s identity and policy services natively rather than building a weak common denominator.
Executive takeaway
AgentCore and Foundry are converging on the same production concerns, but they package them differently. AWS is modular and composable. Microsoft is increasingly integrated around Foundry, Entra and Agent 365. The correct decision follows identity, data boundary, operating ownership and distribution channel.