A multi-agent event planning workflow built with Microsoft Agent Framework - combining Semantic Kernel's enterprise orchestration with AutoGen's multi-agent patterns.
Note
Ignite 2025 Lab: LAB513 - Build A2A and MCP Systems Using SWE Agents and Agent Framework
This sample shows you how to build a production-ready multi-agent system with:
- Multi-Agent Orchestration: 5 specialized agents coordinating event planning
- Human-in-the-Loop: Interactive approval and feedback during workflow execution
- Tool Integration: Web search, weather APIs, calendar management, and code interpreter
- Azure Deployment: One-click deployment with Azure Developer CLI (azd)
The system uses a coordinator-centric star topology where the Event Coordinator routes tasks to specialized agents and synthesizes their outputs into a comprehensive event plan:
Each specialist agent has access to domain-specific tools for their area of expertise:
Tool Integration:
- Venue Specialist: Web Search (Bing Grounding)
- Budget Analyst: Code Interpreter (Python REPL)
- Catering Coordinator: Web Search (Bing Grounding)
- Logistics Manager: Weather API (Open-Meteo) + Calendar Tools (iCalendar)
- All Agents: MCP Sequential Thinking (Model Context Protocol for complex reasoning)
- Python 3.11+
- uv - Python package manager
- Azure CLI (az)
- Azure Developer CLI (azd)
- Azure subscription
# Clone and navigate to the repository
git clone https://github.com/microsoft/spec-to-agents.git
cd spec-to-agents
# Login to Azure
az login
azd auth login
# Deploy everything (provisions resources, generates .env, installs dependencies)
azd upWhat happens:
- β Provisions Microsoft Foundry + OpenAI models
- β
Generates
.envwith connection details - β
Installs Python dependencies via
uv sync
Interactive Console (Recommended):
uv run consoleDevUI (Visual Interface):
uv run appThen navigate to the URL shown (by default http://localhost:8080)
Try this event planning request:
Plan a corporate holiday party for 50 people on December 6th, 2025 in Seattle
with a budget of $5,000. Include venue options, catering for dietary restrictions,
and check the weather forecast.
The agents will collaborate to:
- Search for suitable venues
- Calculate budget breakdown
- Recommend catering options
- Check weather and create calendar event
- Synthesize a comprehensive plan
spec-to-agents/
βββ src/spec_to_agents/
β βββ main.py # DevUI entry point (uv run app)
β βββ console.py # Interactive CLI entry point (uv run console)
β βββ agents/ # Agent definitions (budget_analyst, venue_specialist, etc.)
β βββ prompts/ # System prompts for each agent
β βββ tools/ # Tool implementations (web search, weather, calendar, mcp)
β βββ workflow/ # Workflow orchestration logic
β βββ utils/ # Shared utilities and clients
βββ tests/ # Unit and integration tests
βββ infra/ # Azure infrastructure (Bicep templates)
βββ scripts/ # Post-provisioning hooks
All agents use store=True for automatic conversation history management via Azure AI Service - no manual message tracking required.
Framework-native ctx.request_info() enables pausing workflows for user input with automatic state preservation.
Agents return Pydantic models with explicit routing decisions (next_agent field), enabling dynamic workflow orchestration.
Run Tests:
uv run pytestDetailed Setup: See DEV_SETUP.md for debugging instructions and manual configuration.
Provisioned automatically by azd up:
- Microsoft Foundry: AIServices resource and Project for service managed agents
- Azure OpenAI: gpt-5-mini (primary) and gpt-4.1-mini (web search)
- Bing Search: Grounding API for web searches
- Container Registry & App: For deployment (optional)
- Application Insights: Telemetry and monitoring
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA).
This project is licensed under the MIT License - see the LICENSE file for details.


