Question

You are building a customer support solution in Azure AI Foundry that requires several specialized agents (billing, technical, and escalation) to collaborate. The orchestration logic is complex: agents must dynamically decide which peer to invoke next based on runtime conversation state, and the flow cannot be predetermined as a fixed sequence. You want to author this coordination logic in code using an open-source multi-agent framework that Microsoft has consolidated its agentic development around, with native integration into Foundry. Which approach should you choose?

Accepted Answer

Use the Microsoft Agent Framework (which unifies Semantic Kernel and AutoGen) to code the multi-agent orchestration with dynamic, graph-based agent-to-agent handoffs

Answer

Deploy each agent as an isolated managed online endpoint and hard-code a fixed round-robin call order in the calling application

Answer

Configure a single Foundry agent with all three tool schemas and rely on max_tokens tuning to separate the concerns

Answer

Use a static DAG workflow with fixed edges to route every request through billing, then technical, then escalation in that exact order