Zero-downtime deployment for Durable Functions

The reliable execution model of Durable Functions requires that orchestrations be deterministic, which creates an additional challenge to consider when you deploy updates. When a deployment contains changes to activity function signatures or orchestrator logic, in-flight orchestration instances fail. This situation is especially a problem for instances of long-running orchestrations, which might represent hours or days of work.

To prevent these failures from happening, you have two options:

  • Delay your deployment until all running orchestration instances have completed.
  • Make sure that any running orchestration instances use the existing versions of your functions.

The following chart compares the three main strategies to achieve a zero-downtime deployment for Durable Functions:

Strategy When to use Pros Cons
Versioning Applications that don't experience frequent breaking changes. Simple to implement. Increased function app size in memory and number of functions.
Code duplication.
Status check with slot A system that doesn't have long-running orchestrations lasting more than 24 hours or frequently overlapping orchestrations. Simple code base.
Doesn't require additional function app management.
Requires additional storage account or task hub management.
Requires periods of time when no orchestrations are running.
Application routing A system that doesn't have periods of time when orchestrations aren't running, such as those time periods with orchestrations that last more than 24 hours or with frequently overlapping orchestrations. Handles new versions of systems with continually running orchestrations that have breaking changes. Requires an intelligent application router.
Could max out the number of function apps allowed by your subscription. The default is 100.

The remainder of this document describes these strategies in more detail.


The descriptions for these zero-downtime deployment strategies assume you are using the default Azure Storage provider for Durable Functions. The guidance may not be appropriate if you are using a storage provider other than the default Azure Storage provider. For more information on the various storage provider options and how they compare, see the Durable Functions storage providers documentation.


Define new versions of your functions and leave the old versions in your function app. As you can see in the diagram, a function's version becomes part of its name. Because previous versions of functions are preserved, in-flight orchestration instances can continue to reference them. Meanwhile, requests for new orchestration instances call for the latest version, which your orchestration client function can reference from an app setting.

Versioning strategy

In this strategy, every function must be copied, and its references to other functions must be updated. You can make it easier by writing a script. Here's a sample project with a migration script.


This strategy uses deployment slots to avoid downtime during deployment. For more detailed information about how to create and use new deployment slots, see Azure Functions deployment slots.

Status check with slot

While the current version of your function app is running in your production slot, deploy the new version of your function app to your staging slot. Before you swap your production and staging slots, check to see if there are any running orchestration instances. After all orchestration instances are complete, you can do the swap. This strategy works when you have predictable periods when no orchestration instances are in flight. This is the best approach when your orchestrations aren't long-running and when your orchestration executions don't frequently overlap.

Function app configuration

Use the following procedure to set up this scenario.

  1. Add deployment slots to your function app for staging and production.

  2. For each slot, set the AzureWebJobsStorage application setting to the connection string of a shared storage account. This storage account connection string is used by the Azure Functions runtime to securely store the functions' access keys.

  3. For each slot, create a new app setting, for example, DurableManagementStorage. Set its value to the connection string of different storage accounts. These storage accounts are used by the Durable Functions extension for reliable execution. Use a separate storage account for each slot. Don't mark this setting as a deployment slot setting.

  4. In your function app's host.json file's durableTask section, specify connectionStringName (Durable 2.x) or azureStorageConnectionStringName (Durable 1.x) as the name of the app setting you created in step 3.

The following diagram shows the described configuration of deployment slots and storage accounts. In this potential predeployment scenario, version 2 of a function app is running in the production slot, while version 1 remains in the staging slot.

Deployment slots and storage accounts

host.json examples

The following JSON fragments are examples of the connection string setting in the host.json file.

Functions 2.0

  "version": 2.0,
  "extensions": {
    "durableTask": {
      "hubName": "MyTaskHub",
      "storageProvider": {
        "connectionStringName": "DurableManagementStorage"

Functions 1.x

  "durableTask": {
    "azureStorageConnectionStringName": "DurableManagementStorage"

CI/CD pipeline configuration

Configure your CI/CD pipeline to deploy only when your function app has no pending or running orchestration instances. When you're using Azure Pipelines, you can create a function that checks for these conditions, as in the following example:

public static async Task<IActionResult> StatusCheck(
    [HttpTrigger(AuthorizationLevel.Function, "get", "post")] HttpRequestMessage req,
    [DurableClient] IDurableOrchestrationClient client,
    ILogger log)
    var runtimeStatus = new List<OrchestrationRuntimeStatus>();


    var result = await client.ListInstancesAsync(new OrchestrationStatusQueryCondition() { RuntimeStatus = runtimeStatus }, CancellationToken.None);
    return (ActionResult)new OkObjectResult(new { HasRunning = result.DurableOrchestrationState.Any() });

Next, configure the staging gate to wait until no orchestrations are running. For more information, see Release deployment control using gates

Deployment gate

Azure Pipelines checks your function app for running orchestration instances before your deployment starts.

Deployment gate (running)

Now the new version of your function app should be deployed to the staging slot.

Staging slot

Finally, swap slots.

Application settings that aren't marked as deployment slot settings are also swapped, so the version 2 app keeps its reference to storage account A. Because orchestration state is tracked in the storage account, any orchestrations running on the version 2 app continue to run in the new slot without interruption.

Deployment slot

To use the same storage account for both slots, you can change the names of your task hubs. In this case, you need to manage the state of your slots and your app's HubName settings. To learn more, see Task hubs in Durable Functions.

Application routing

This strategy is the most complex. However, it can be used for function apps that don't have time between running orchestrations.

For this strategy, you must create an application router in front of your Durable Functions. This router can be implemented with Durable Functions. The router has the responsibility to:

  • Deploy the function app.
  • Manage the version of Durable Functions.
  • Route orchestration requests to function apps.

The first time an orchestration request is received, the router does the following tasks:

  1. Creates a new function app in Azure.
  2. Deploys your function app's code to the new function app in Azure.
  3. Forwards the orchestration request to the new app.

The router manages the state of which version of your app's code is deployed to which function app in Azure.

Application routing (first time)

The router directs deployment and orchestration requests to the appropriate function app based on the version sent with the request. It ignores the patch version.

When you deploy a new version of your app without a breaking change, you can increment the patch version. The router deploys to your existing function app and sends requests for the old and new versions of the code, which are routed to the same function app.

Application routing (no breaking change)

When you deploy a new version of your app with a breaking change, you can increment the major or minor version. Then the application router creates a new function app in Azure, deploys to it, and routes requests for the new version of your app to it. In the following diagram, running orchestrations on the 1.0.1 version of the app keep running, but requests for the 1.1.0 version are routed to the new function app.

Application routing (breaking change)

The router monitors the status of orchestrations on the 1.0.1 version and removes apps after all orchestrations are finished.

Tracking store settings

Each function app should use separate scheduling queues, possibly in separate storage accounts. If you want to query all orchestrations instances across all versions of your application, you can share instance and history tables across your function apps. You can share tables by configuring the trackingStoreConnectionStringName and trackingStoreNamePrefix settings in the host.json settings file so that they all use the same values.

For more information, see Manage instances in Durable Functions in Azure.

Tracking store settings

Next steps