1# Durable Functions
2 
3Long-running orchestrations with checkpointing and state management.
4 
5## Storage Backend
6 
7Durable Functions requires a storage backend to persist orchestration state, queues, and history.
8 
9| Backend | Recommendation | Notes |
10|---------|---------------|-------|
11| **Durable Task Scheduler** | **✅ Required** | Fully managed Azure service. Best performance, lowest latency, built-in monitoring. Supports all languages (.NET, Python, Java, JavaScript). |
12| Azure Storage (default) | ⛔ Do not use | Legacy backend. Higher latency, harder to monitor, no built-in RBAC. Not permitted for new projects. |
13| MSSQL | Specialized | SQL Server backend. Only when SQL infrastructure already exists and user explicitly requests it. |
14 
15> **⛔ MANDATORY**: You **MUST** use **Durable Task Scheduler** as the storage backend for ALL new Durable Functions projects. Do NOT use Azure Storage as the backend — it is legacy and not permitted. Generate the DTS Bicep module (`Microsoft.DurableTask/schedulers` + `taskHubs`), RBAC role assignment (Durable Task Data Contributor), and `DURABLE_TASK_SCHEDULER_CONNECTION_STRING` app setting. See the [Durable Task Scheduler reference](../durable-task-scheduler/README.md) for setup, language-specific guidance, and Bicep templates.
16 
17## When to Use
18 
19- Multi-step workflows
20- Fan-out/fan-in patterns
21- Human interaction workflows
22- Long-running processes
23 
24## Get Durable Templates
25 
26Use the [Azure Functions Templates workflow](templates/README.md) to discover and fetch durable samples:
27 
28**MCP Tool:** `functions_template_get(language)` → filter `resource == "durable"`
29 
30**Fallback:** CDN manifest → filter `resource == "durable"`
31 
32Available patterns: Fan-out/Fan-in, Order Processing (with Bicep), Distributed Tracing, Large Payload, Saga, AI Travel Planner, PDF Summarizer, .NET Aspire integration.
33