This directory contains samples for durable agent hosting using the Durable Task Scheduler. These samples demonstrate the worker-client architecture pattern, enabling distributed agent execution with persistent conversation state.
- 01_single_agent: Host a single conversational agent and interact with it via a client. Demonstrates basic worker-client architecture and agent state management.
- 02_multi_agent: Host multiple domain-specific agents (physicist and chemist) and route requests to the appropriate agent based on the question topic.
- 03_single_agent_streaming: Enable reliable, resumable streaming using Redis Streams with agent response callbacks. Demonstrates non-blocking agent execution and cursor-based resumption for disconnected clients.
- 04_single_agent_orchestration_chaining: Chain multiple invocations of the same agent using durable orchestration, preserving conversation context across sequential runs.
- 05_multi_agent_orchestration_concurrency: Run multiple agents concurrently within an orchestration, aggregating their responses in parallel.
- 06_multi_agent_orchestration_conditionals: Implement conditional branching in orchestrations with spam detection and email assistant agents. Demonstrates structured outputs with Pydantic models and activity functions for side effects.
- 07_single_agent_orchestration_hitl: Human-in-the-loop pattern with external event handling, timeouts, and iterative refinement based on human feedback. Shows long-running workflows with external interactions.
These samples are designed to be run locally in a cloned repository.
The following prerequisites are required to run the samples:
- Python 3.9 or later
- Azure CLI installed and authenticated (
az login) or an API key for the Azure OpenAI service - Azure OpenAI Service with a deployed model (gpt-4o-mini or better is recommended)
- Durable Task Scheduler (local emulator or Azure-hosted)
- Docker installed if running the Durable Task Scheduler emulator locally
These samples are configured to use the Azure OpenAI service with RBAC permissions to access the model. You'll need to configure the RBAC permissions for the Azure OpenAI service to allow the Python app to access the model.
Below is an example of how to configure the RBAC permissions for the Azure OpenAI service to allow the current user to access the model.
Bash (Linux/macOS/WSL):
az role assignment create \
--assignee "yourname@contoso.com" \
--role "Cognitive Services OpenAI User" \
--scope /subscriptions/<your-subscription-id>/resourceGroups/<your-resource-group-name>/providers/Microsoft.CognitiveServices/accounts/<your-openai-resource-name>PowerShell:
az role assignment create `
--assignee "yourname@contoso.com" `
--role "Cognitive Services OpenAI User" `
--scope /subscriptions/<your-subscription-id>/resourceGroups/<your-resource-group-name>/providers/Microsoft.CognitiveServices/accounts/<your-openai-resource-name>More information on how to configure RBAC permissions for Azure OpenAI can be found in the Azure OpenAI documentation.
Most samples use the Durable Task Scheduler (DTS) to support hosted agents and durable orchestrations. DTS also allows you to view the status of orchestrations and their inputs and outputs from a web UI.
To run the Durable Task Scheduler locally, you can use the following docker command:
docker run -d --name dts-emulator -p 8080:8080 -p 8082:8082 mcr.microsoft.com/dts/dts-emulator:latestThe DTS dashboard will be available at http://localhost:8082.
Each sample reads configuration from environment variables. You'll need to set the following environment variables:
Bash (Linux/macOS/WSL):
export FOUNDRY_PROJECT_ENDPOINT="https://your-project.services.ai.azure.com/api/projects/your-project"
export FOUNDRY_MODEL="your-deployment-name"PowerShell:
$env:FOUNDRY_PROJECT_ENDPOINT="https://your-project.services.ai.azure.com/api/projects/your-project"
$env:FOUNDRY_MODEL="your-deployment-name"Navigate to the sample directory and install dependencies. For example:
cd samples/04-hosting/durabletask/01_single_agent
pip install -r requirements.txtIf you're using uv for package management:
uv pip install -r requirements.txtEach sample follows a worker-client architecture. Most samples provide separate worker.py and client.py files, though some include a combined sample.py for convenience.
Running with separate worker and client:
In one terminal, start the worker:
python worker.pyIn another terminal, run the client:
python client.pyRunning with combined sample:
python sample.pyThe sample output is displayed directly in the terminal where you ran the Python script. Agent responses are printed to stdout with log formatting for better readability.
You can also see the state of agents and orchestrations in the Durable Task Scheduler dashboard at http://localhost:8082.