AI Platforms
Microsoft Foundry Agent Service Moves Toward GA
Published June 04, 2026 by Dillip Chowdary
Microsoft says Foundry Agent Service is moving into a production posture with richer orchestration, deployment, memory, tool, and observability controls for enterprise agents.
What Changed
- Runtime path: Hosted agents, tools, memory, and managed sessions are being packaged as a first-party service surface instead of custom glue code.
- Enterprise control: The update emphasizes identity, governed tool access, auditability, and repeatable deployment for multi-agent apps.
- Developer effect: Teams can keep agent logic closer to Azure AI Foundry while moving evaluation and rollout into standard release workflows.
Architecture Impact
For engineering teams, the important shift is that agent infrastructure is becoming a managed platform layer. Identity, memory, tool invocation, evaluation, telemetry, and publishing are no longer optional wrappers around a model call. They are now part of how production teams control reliability, cost, and blast radius.
The practical design question is where state lives and who can act on it. Agents that read documents, query operational data, call tools, or publish work need typed interfaces, permission boundaries, and observable handoffs. Without those controls, faster agent development can create a wider operational risk surface.
Rollout Checklist
Start with one contained workflow, define the approved tools, log every action, and require human review for writes into production systems. Add regression evaluations for prompts, tool schemas, and retrieval sources before expanding the agent to more users.
Treat Foundry agents like services: version prompts, tool contracts, memory stores, and evaluation gates before expanding access.