Skip to main content

SOAT vs Microsoft Foundry Agent Service

Microsoft Foundry Agent Service is a managed agent platform (Proprietary (Microsoft Azure commercial service), managed). SOAT is agent infrastructure (Apache-2.0, self-hosted). Of the 15 capabilities the benchmark tracks, Microsoft Foundry Agent Service covers 12 natively and SOAT 12.

At a glance​

Microsoft Foundry Agent ServiceSOAT
Typea managed agent platformagent infrastructure
LicenseProprietary (Microsoft Azure commercial service)Apache-2.0
Deploymentmanagedself-hosted
Native capabilities12 of 1512 of 15
Last verified2026-08-142026-08-14

Where each one leads​

  • Microsoft Foundry Agent Service is native where SOAT is not: channels, code execution.
  • SOAT is native where Microsoft Foundry Agent Service is not: data & secrets, multi-tenancy.

What Microsoft Foundry Agent Service is​

Managed Azure service for building and scaling agents as either configuration-defined prompt agents or container-based hosted agents, with the Responses API as the single model and tool entry point. Runtime, tools, Entra identity, tracing, and evaluation live inside a Foundry project; there is no self-hosted distribution. Microsoft Foundry Agent Service documentation.

Capability by capability​

Agent runtime​

Agent loop, sessions, and generation lifecycle.

  • Microsoft Foundry Agent Service: Native. The Agent Runtime hosts prompt and hosted agents, managing conversations, tool calls, and session state behind a managed autoscaled endpoint. (source)
  • SOAT: Native. Agents, sessions, chats, and generations with full lifecycle tracking. (source)

Orchestration​

Multi-step pipelines, workflows, and triggers.

  • Microsoft Foundry Agent Service: Native. Workflows provide a declarative visual builder for multi-agent sequences with branching, variables, and human-in-the-loop approval steps, plus A2A connections. (source)
  • SOAT: Native. DAG orchestrations, workflow state machines, durable tasks, and triggers (manual, webhook, schedule). (source)

Knowledge & memory​

Documents, embeddings, semantic search, and recall.

  • Microsoft Foundry Agent Service: Native. The File Search tool indexes uploaded documents into managed vector stores, with an additional memory tool and Azure AI Search grounding available. (source)
  • SOAT: Native. Documents with per-chunk embeddings, named memories, unified semantic search, and ingestion rules for PDFs, images, and audio. (source)

Tools & integration​

Tool calling, MCP, providers, and webhooks.

  • Microsoft Foundry Agent Service: Native. The tool catalog offers built-in tools, OpenAPI tools, function calling, remote MCP servers, and Toolbox bundling curated tools behind one managed MCP endpoint. (source)
  • SOAT: Native. HTTP, MCP, client, and agent-to-agent tools; model routes with failover; webhooks; any LLM provider. (source)

Identity & governance​

IAM, guardrails, approvals, quotas, and audit.

  • Microsoft Foundry Agent Service: Native. Agents can hold a dedicated Microsoft Entra identity with Azure RBAC, integrated guardrails and content filters, per-tool approval requirements, and documented quotas. (source)
  • SOAT: Native. AWS-inspired IAM, actors, scoped API keys, guardrails, human approvals, quotas, and an append-only audit log. (source)

Observability​

Traces, activity, usage, and failure queues.

  • Microsoft Foundry Agent Service: Native. Agent tracing records every model call and tool invocation with Application Insights integration, service dashboards, and continuous production evaluation. (source)
  • SOAT: Native. Traces of every tool call and model response, activity feed, usage/cost tracking, and an exceptions queue. (source)

Data & secrets​

File storage and encrypted secrets.

  • Microsoft Foundry Agent Service: Partial. Files and vector stores are service-managed and tool credentials sit in project connections, but durable storage and secrets rely on Azure Storage and Key Vault. (source)
  • SOAT: Native. File storage over local/S3/GCS backends and encrypted secrets storage. (source)

Evaluation​

Datasets, scorers, and eval-gated improvement.

  • Microsoft Foundry Agent Service: Native. Evaluations run uploaded JSONL datasets against an agent using rubric, quality, safety, and custom evaluators, returning per-run and per-row scores. (source)
  • SOAT: Native. Datasets, scorers, and scored runs; eval-gated promotion of agent versions. (source)

Channels​

Built-in gateways to messaging platforms and UIs.

  • Microsoft Foundry Agent Service: Native. Agents publish from the Foundry portal into Microsoft Teams and Microsoft 365 Copilot via a generated Teams manifest and Azure Bot Service channel. (source)
  • SOAT: Absent. Surfaces are REST, MCP, CLI, and SDK — no built-in gateways to messaging platforms like Slack, WhatsApp, or Telegram.

Code execution​

Sandboxed code or terminal runtimes for agents.

  • Microsoft Foundry Agent Service: Native. The Code Interpreter tool executes agent-written Python in a sandbox, with a custom variant allowing configured packages and Container Apps resources. (source)
  • SOAT: Absent. Tool types are HTTP, MCP, client, and agent-to-agent — no built-in sandboxed code or terminal runtime.

Human-in-the-loop​

Pausing a run for human approval, then resuming it.

  • Microsoft Foundry Agent Service: Native. An MCP tool configured to always require approval emits an approval request item that suspends the tool call until the caller submits a matching approval response. (source)
  • SOAT: Native. Approvals are a first-class human-decision queue with frozen evidence, and guardrails classify each tool call so risky actions pause for a decision. (source)

Multi-tenancy​

Projects or workspaces scoping resources and permissions.

  • Microsoft Foundry Agent Service: Partial. A Foundry project scopes agents and Azure RBAC roles with optional per-agent role scopes, but tenancy is plain Azure RBAC on ARM resources rather than an agent-service tenant model. (source)
  • SOAT: Native. Projects are multi-tenant namespaces scoping every resource, with IAM policies and quotas enforced per project. (source)

Declarative deployment​

Templates that provision agent resources as one stack.

  • Microsoft Foundry Agent Service: Native. Agents and their deployments are first-class ARM resource types authorable in Bicep, ARM JSON, or Terraform, with parent-child dependency resolution and pinned version references. (source)
  • SOAT: Native. Formations provision providers, memories, tools, agents, orchestrations, and webhooks from one template, resolving refs into a dependency graph with tracked operations. (source)

Versioning & rollout​

Agent versions, canary rollout, gated promotion.

  • Microsoft Foundry Agent Service: Native. Saved agent versions are immutable and referenced by name and version, with version history, per-version diffing, request routing to a specific version, and rollback. (source)
  • SOAT: Native. Every config change is archived as an append-only agent version, with canary rollout to a slice of traffic and eval-gated promotion. (source)

Skill learning​

Agents authoring reusable skills from their own experience.

  • Microsoft Foundry Agent Service: Partial. The preview agent optimizer discovers and refines reusable skills for a hosted agent using datasets generated from its own traces, but a human applies and redeploys the winning candidate. (source)
  • SOAT: Absent. Memories and knowledge store retrievable context, but agents do not author or refine reusable skills from their own experience.

How this is rated​

Each rating comes from the public documentation linked beside it: Native is built in, Via plugin needs an add-on, Partial covers part of the capability, Absent is not offered. Every solution side by side is on the benchmark. A rating that is out of date is a bug: open an issue.