Agent building & orchestration
Microsoft Foundry Agent Service
Managed Microsoft platform for building, deploying and scaling agents, offering prompt agents configured in a portal, hosted container agents from frameworks such as Agent Framework and LangGraph, and direct Responses API use. Each hosted agent receives a dedicated Microsoft Entra identity plus managed endpoint, scaling and observability.
commercial · generally available · Research snapshot 2026-09-06
Visit the official product source ↗Where it fits
Agent building & orchestration · Agent identity & access · Observability & traceability
Useful conversation with: AI platform lead, Cloud architect, Engineering manager.
Ask for a demonstration
Show me a hosted agent deployed from a container that receives its own Entra identity, and the end-to-end trace of one of its runs.
Capabilities and evidence
Support labels reflect the supplied research. Documentation and vendor claims are not independent product tests. “Not established” means the researcher did not find support; it does not prove a capability is absent.
Documented by provider
Offers prompt agents run with no code or infrastructure, hosted agents supplied as a container image or zipped source, direct Responses API calls, and ephemeral agents defined in application code.
Limit: Documentation does not state per-path regional availability or quota limits.
Source s1
Documented by provider
Hosted agents are provided with a managed endpoint, automatic scaling, a dedicated Microsoft Entra identity, session-level state persistence and end-to-end observability.
Limit: The overview does not detail how Entra permissions are scoped per agent or how least privilege is enforced.
Source s1
Documented by provider
Hosted agents can be built with Agent Framework, LangGraph, the OpenAI Agents SDK, the Anthropic Agent SDK, the GitHub Copilot SDK or custom code.
Limit: Microsoft Agent Framework is documented separately; the overview does not state version support matrices.
Source s1 · Source s2
Documented by provider
Microsoft Agent Framework's Harness Agent documents 'don't-ask-again' tool approval alongside planning, context compaction, memory and observability.
Limit: This is a framework feature exercised in code, not a tenant-level approval workflow in the Agent Service.
Source s2
Not established in this research
Administrative audit logging and role-based permission scoping for agent actions are not established by the pages reviewed.
Limit: Absence of evidence only; Azure platform-level RBAC and logging likely exist but were not verified here.
Source s1
Limitations to discuss
- Governance evidence is limited to identity assignment and observability; approvals are a framework-level developer feature.
- No documented audit trail of agent actions or admin approval gate was verified in this session.
- Product naming has changed repeatedly (Azure AI Agent Service to Foundry Agent Service), so older references may not match current docs.
Sources
- What is Microsoft Foundry Agent Service? · Microsoft Learn · official docs
Access date reported by researcher: 2026-09-06 - Microsoft Agent Framework Overview · Microsoft Learn · official docs
Access date reported by researcher: 2026-09-06
Listing does not imply partnership, supplier status, a working DutyGraph integration, or a compliance certification.
Suggest a correction