Full-Code · Enterprise Platformsactive

Azure AI Foundry Agent Service

also known as Azure AI Agent Service, Microsoft Foundry Agent Service

Type: full-code  ·  Vendor: Microsoft Azure  ·  Language: API (multi-language SDKs: Python, .NET, JavaScript, Java, REST)  ·  License: proprietary  ·  Status: active  ·  Status in practice: mature  ·  First released: 2025-05-19

Links: homepage docs

Fully managed Azure platform for building, deploying, and scaling AI agents that combine a Foundry-catalog model, instructions, and tools, with built-in identity, content safety, tracing, evaluation, and three agent shapes (prompt, workflow, hosted-container).

Description. Foundry Agent Service hosts and scales agents on Azure-managed runtime. An agent is a model from the Foundry catalog plus instructions plus tools; the service handles tool execution, conversation state, Microsoft Entra identity, content filters, virtual-network isolation, tracing into Application Insights, and a build-test-deploy-monitor lifecycle with immutable versioning. Three agent types coexist: prompt agents (configuration-only), workflow agents (declarative YAML or visual designer for sequential / group-chat / human-in-the-loop orchestrations), and hosted agents (your container running Microsoft Agent Framework, LangGraph, Semantic Kernel, or custom code, per-session VM-isolated). The catalog of built-in tools includes Web Search, Code Interpreter, File Search, Azure AI Search, Function calling, OpenAPI tools, Image Generation, Browser Automation, Computer Use, plus MCP and A2A as custom tool surfaces.

Agent loop shape. Managed agent runtime around a Foundry-catalog model. Prompt agents run a single-agent tool-use loop: model reasons over instructions, the service decides whether to call a built-in tool (web search, code interpreter, file search, MCP, OpenAPI, function call), executes, observes, continues. Workflow agents bind that loop into a declarative graph of nodes (agent invocation, if/else, for-each, human-in-the-loop, group chat) defined in YAML or the visual designer. Hosted agents replace the inner loop with user code in a per-session VM-isolated sandbox that calls Foundry models, Toolbox MCP, and the Responses / Invocations / Activity / A2A protocols. Every run is traced, versioned, and gated by content filters and Entra identity.

Primary use cases

  • no-code prompt agents in the Foundry portal
  • declarative multi-step workflows that orchestrate agents and business logic
  • containerized custom-code agents (Agent Framework / LangGraph / Semantic Kernel) on managed VMs
  • enterprise tool integration via MCP, OpenAPI, and Azure connectors
  • publishing agents to Microsoft 365, Teams, and the Entra Agent Registry

Key concepts

  • Prompt / Workflow / Hosted agents (docs)Three agent shapes: prompt (configuration-only), workflow (declarative orchestration), hosted (your container on managed runtime).
  • Foundry tool catalog tool-use (docs)Built-in tools (web search, Code Interpreter, File Search, Azure AI Search, Functions) plus custom tools (MCP, OpenAPI, A2A) registered through the portal.
  • Workflows orchestrator-workers (docs)Visual / YAML orchestration with sequential, group-chat, and human-in-the-loop patterns.
  • Hosted agents agent-resumption (docs)Per-session VM-isolated containers with persistent $HOME and /files; Responses / Invocations / Activity / A2A protocols.
  • Guardrails and content filters prompt-injection-defense (docs)Integrated content filters with cross-prompt-injection (XPIA) protection.
  • Agent identity and tracing (docs)Per-agent Microsoft Entra identity, RBAC, Application Insights tracing of every model call and tool invocation.

Patterns this full-code implements

Neighbourhood

Click any neighbour to follow the lineage. Scroll to zoom, drag to pan.