Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

Azure Durable Functions review

#21 of 29 in Process Orchestration Software

A code-first Azure service for durable, stateful orchestration and long-running processes.

7.1/10Editor score
Azure Durable Functions7.1 Visit Microsoft

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

Azure Durable Functions extends Azure Functions with stateful serverless workflow orchestration in code. It is designed for long-running processes, distributed coordination, parallel workflows, API orchestration, business process automation, and human-in-the-loop approvals. Orchestrator, activity, and entity functions provide the core building blocks, while the service manages state, checkpoints, retries, recovery, and execution history. It is available through web and API environments and supports .NET, JavaScript, TypeScript, Python, PowerShell, and Java.

Pricing is usage-based infrastructure pricing rather than a standalone subscription. Flex Consumption offers on-demand and always-ready billing modes, plus 250,000 monthly free executions and a 100,000 GB-s monthly free grant. Consumption uses per-second resource consumption billing, with 1 million monthly free requests and a 400,000 GB-s monthly free grant. Premium bills by vCPU-seconds and allocated memory, with no execution charge and at least one instance allocated per plan. Durable Task Scheduler Consumption adds pay-per-use access to a managed orchestration-state backend, while Dedicated uses single-tenant resources at a fixed monthly cost per Capacity Unit. The published pricing approach requires regional meter selection and calculator-based estimation.

Its strongest case is complex, durable coordination: external events and timers support approval workflows, fan-out/fan-in handles parallel processing, and workflow version isolation helps separate revisions. Application Insights tracking, distributed tracing, custom orchestration status reporting, state persistence, and audit logs add visibility around execution. Azure users who want code-defined, stateful processes should consider it for reliable orchestration across long-running and human-involved steps. It is less suitable for teams seeking a standalone subscription product, a non-cloud deployment model, or a visual-first workflow tool. Teams using the in-process programming model should also account for its scheduled support end on November 10, 2026.

Azure Durable Functions pros and cons

  • Where it wins
    • Checkpoints, retries, recovery, timers, and human approvals
    • Fan-out/fan-in, version isolation, and distributed tracing
    • Supports .NET, JavaScript, TypeScript, Python, PowerShell, and Java
  • Where it doesn't
    • Paid usage model with no free plan
    • Regional pricing uses meters and a pricing calculator
    • In-process programming model support ends November 10, 2026

Azure Durable Functions fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update