Merge pull request #312464 from MicrosoftDocs/main

Auto Publish – main to live - 2026-03-02 06:00 UTC

Author: learn-build-service-prod[bot]

articles/azure-functions/durable/durable-functions-orchestration-versioning.md

@@ -9,7 +9,7 @@ ms.custom: fasttrack-edit
 #Customer intent: As a Durable Functions developer, I want to deploy breaking changes to my orchestrations without interrupting in-flight instances, so that I can maintain zero-downtime deployments.
 ---
 
-# Orchestration versioning in Durable Functions (Azure Functions) - public preview
+# Orchestration versioning in Durable Functions (Azure Functions)
 
 Orchestration versioning addresses [the core challenge](durable-functions-versioning.md) of deploying changes to orchestrator functions while maintaining the deterministic execution model that Durable Functions requires. Without this feature, breaking changes to orchestrator logic or activity function signatures would cause in-flight orchestration instances to fail during replay because they would break the [determinism requirement](durable-functions-code-constraints.md) that ensures reliable orchestration execution. This built-in feature provides automatic version isolation with minimal configuration. It's backend agnostic, so it can be used by apps leveraging any of the Durable Function's [storage providers](durable-functions-storage-providers.md), including the [Durable Task Scheduler](./durable-task-scheduler/durable-task-scheduler.md).
 
@@ -36,46 +36,45 @@ The orchestration versioning feature operates on these core principles:
 
 - **Forward Protection**: The runtime automatically prevents workers running older orchestrator versions from executing orchestrations started by newer orchestrator versions.
 
-> [!IMPORTANT]
-> Orchestration versioning is currently in public preview.
-
 ## Prerequisites
 
 Before using orchestration versioning, ensure you have the required package versions for your programming language.
 
-If you're using a non-.NET language (JavaScript, Python, PowerShell, or Java) with [extension bundles](../extension-bundles.md), your function app must reference **Extension Bundle version 4.26.0 or later**. Configure the `extensionBundle` range in `host.json` so that the minimum version is at least `4.26.0`, for example:
+If you're using a non-.NET language (JavaScript, Python, PowerShell, or Java) with [extension bundles](../extension-bundles.md), your function app must reference **Extension Bundle version 4.30.0 or later**. Configure the `extensionBundle` range in `host.json` so that the minimum version is at least `4.30.0`, for example:
 
 ```json
 {
     "version": "2.0",
     "extensionBundle": {
         "id": "Microsoft.Azure.Functions.ExtensionBundle",
-        "version": "[4.26.0, 5.0.0)"
+        "version": "[4.30.0, 5.0.0)"
     }
 }
 ```
 
 See the [extension bundle configuration documentation](../extension-bundles.md) for details on choosing and updating bundle versions.
 
+In addition to the extension bundle requirement for non-.NET languages, you also need to use the minimum version of the language-specific SDK package listed below. Both the extension bundle and the SDK package are required for orchestration versioning to work correctly.
+
 # [C#](#tab/csharp)
 
-Use `Microsoft.Azure.Functions.Worker.Extensions.DurableTask` version [1.5.0](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker.Extensions.DurableTask/1.5.0) or later.
+Use `Microsoft.Azure.Functions.Worker.Extensions.DurableTask` version [1.14.0](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker.Extensions.DurableTask/1.14.0) or later.
 
 # [JavaScript](#tab/javascript)
 
-Use `durable-functions` version [3.2.0](https://www.npmjs.com/package/durable-functions/v/3.2.0) or later.
+Use `durable-functions` version [3.3.0](https://www.npmjs.com/package/durable-functions/v/3.3.0) or later.
 
 # [Python](#tab/python)
 
-Use `azure-functions-durable` version [1.3.3](https://pypi.org/project/azure-functions-durable/1.3.3/) or later.
+Use `azure-functions-durable` version [1.5.0](https://pypi.org/project/azure-functions-durable/1.5.0/) or later.
 
 # [PowerShell](#tab/powershell)
 
-Use `AzureFunctions.PowerShell.Durable.SDK` version [2.0.0](https://www.powershellgallery.com/packages/AzureFunctions.PowerShell.Durable.SDK/2.0.0) or later. Make sure you're using the standalone [Durable Functions PowerShell SDK](durable-functions-powershell-v2-sdk-migration-guide.md).
+Use `AzureFunctions.PowerShell.Durable.SDK` version [2.2.0](https://www.powershellgallery.com/packages/AzureFunctions.PowerShell.Durable.SDK/2.2.0) or later. Make sure you're using the standalone [Durable Functions PowerShell SDK](durable-functions-powershell-v2-sdk-migration-guide.md).
 
 # [Java](#tab/java)
 
-Use `durabletask-azure-functions` version [1.6.1](https://mvnrepository.com/artifact/com.microsoft/durabletask-azure-functions/1.6.1) or later.
+Use `durabletask-azure-functions` version [1.6.3](https://mvnrepository.com/artifact/com.microsoft/durabletask-azure-functions/1.6.3) or later.
 
 ---
 
@@ -633,16 +632,36 @@ public static async Task<HttpResponseData> HttpStart(
 ```
 
 # [JavaScript](#tab/javascript)
+```javascript
+const HttpStart: HttpHandler = async (request: HttpRequest, context: InvocationContext): Promise<HttpResponse> => {
+    const client = df.getClient(context);
+    const instanceId = await client.startNew("ProcessOrderOrchestrator", {
+        input: orderId,
+        version: "1.0"
+    });
 
-Starting an orchestration with a specific version different from the current `defaultVersion` specified in your `host.json` is currently not supported in JavaScript.
+    // ...
+};
+```
 
 # [Python](#tab/python)
+```python
+@myApp.route(route="orchestrators/{functionName}")  
+@myApp.durable_client_input(client_name="client")  
+async def http_start(req: func.HttpRequest, client):
+    instance_id = await client.start_new("ProcessOrderOrchestrator", client_input=order_id, version="1.0")
 
-Starting an orchestration with a specific version different from the current `defaultVersion` specified in your `host.json` is currently not supported in Python.
+    # ...
+```
 
 # [PowerShell](#tab/powershell)
+```powershell
+param($Request, $TriggerMetadata)
 
-Starting an orchestration with a specific version different from the current `defaultVersion` specified in your `host.json` is currently not supported in PowerShell.
+$instanceId = Start-DurableOrchestration -FunctionName "ProcessOrderOrchestrator" -Input $orderId -Version "1.0"
+
+# ...
+```
 
 # [Java](#tab/java)
 
@@ -688,16 +707,39 @@ public static async Task<string> RunMainOrchestrator(
 ```
 
 # [JavaScript](#tab/javascript)
+```javascript
+const RunMainOrchestrator: OrchestrationHandler = function* (context: OrchestrationContext) {
+    const paymentResult = yield context.df.callSubOrchestrator(
+        "ProcessPaymentOrchestrator",
+        orderId,
+        { version: "1.0" }
+    );
 
-Starting a sub-orchestration with a specific version different from the current `defaultVersion` specified in your `host.json` is currently not supported in JavaScript.
+    // ...
+};
+```
 
 # [Python](#tab/python)
+```python
+@myApp.orchestration_trigger(context_name="context")
+def run_main_orchestrator(context: df.DurableOrchestrationContext):
+    payment_result = yield context.call_sub_orchestrator(
+        "ProcessPaymentOrchestrator",
+        order_id,
+        version="1.0"
+    )
 
-Starting a sub-orchestration with a specific version different from the current `defaultVersion` specified in your `host.json` is currently not supported in Python.
+    # ...
+```
 
 # [PowerShell](#tab/powershell)
+```powershell
+param($Context)
 
-Starting a sub-orchestration with a specific version different from the current `defaultVersion` specified in your `host.json` is currently not supported in PowerShell.
+$paymentResult = Invoke-SubOrchestrator -FunctionName "ProcessPaymentOrchestrator" -Input $orderId -Version "1.0"
+
+# ...
+```
 
 # [Java](#tab/java)
 

articles/azure-functions/durable/durable-functions-versioning.md

@@ -203,9 +203,6 @@ Because of these potential failures, the "do nothing" strategy is not recommende
 
 ### Orchestration versioning
 
-> [!NOTE]
-> Orchestration versioning is currently in public preview.
-
 The orchestration versioning feature allows different versions of orchestrations to coexist and execute concurrently without conflicts and non-determinism issues, making it possible to deploy updates while allowing in-flight orchestration instances to complete without manual intervention.
 
 With orchestration versioning:

articles/azure-functions/durable/durable-task-scheduler/durable-task-scheduler-versioning.md

@@ -1,5 +1,5 @@
 ---
-title: Configure Versioning for Durable Task Scheduler (preview)
+title: Configure Versioning for Durable Task Scheduler
 description: Learn how to use orchestration versioning in Durable Task Scheduler.
 ms.topic: how-to
 ms.date: 12/03/2025
@@ -9,7 +9,7 @@ ms.reviewer: hannahhunter
 zone_pivot_groups: df-languages
 ---
 
-# Orchestration Versioning (preview)
+# Orchestration Versioning
 
 Upgrading and downgrading orchestrations is a key consideration when working with durable orchestration systems. If an orchestration is interrupted and later resumed (for instance, during a host update), Durable Task Scheduler replays the events of the orchestration, ensuring all previous steps were executed successfully before taking the next step. This action ensures reliability, one of the core promises of the durable execution paradigm. 
 

articles/frontdoor/scenarios.md

@@ -5,7 +5,7 @@ author: johndowns
 ms.author: jodowns
 ms.service: azure-frontdoor
 ms.topic: concept-article
-ms.date: 02/13/2023
+ms.date: 03/02/2026
 ---
 
 # Accelerate and secure your web application with Azure Front Door
@@ -46,7 +46,7 @@ When you have strict network security requirements, you can use Azure Front Door
 By using Front Door, you can create resilient, highly available solutions.
 
 - **Load balancing and failover:** Front Door is a global load balancer. Front Door monitors the health of your origin servers, and if an origin becomes unavailable, [Front Door can route requests to an alternative origin](routing-methods.md). You can also use Front Door to spread traffic across your origins to reduce the load on any one origin server.
-- **Anycast routing:** Front Door itself has a [large number of PoPs](edge-locations-by-region.md), each of which can serve traffic for any request. [Anycast routing](front-door-traffic-acceleration.md#select-the-front-door-edge-location-for-the-request-anycast) steers traffic to the closest available Front Door PoP, and if a PoP is unavailable, clients are automatically routed to the next closest PoP.
+- **Automatic routing:** Front Door itself has a [large number of PoPs](edge-locations-by-region.md), each of which can serve traffic for any request. [Azure Front Door's routing architecture](front-door-traffic-acceleration.md) automatically steers traffic to the closest available Front Door PoP, and if a PoP is unavailable, clients are automatically routed to the next closest PoP.
 - **Caching:** By using the Front Door cache, you reduce the load on your application servers. If your servers are unavailable, Front Door might be able to continue to serve cached responses until your application recovers.
 
 ### Cost optimization
@@ -78,7 +78,7 @@ The following diagram illustrates a generic solution architecture using Front Do
 
 ### Client to Front Door
 
-Traffic from the client first arrives at a Front Door PoP. Front Door has a [large number of PoPs](edge-locations-by-region.md) distributed worldwide, and [Anycast](front-door-traffic-acceleration.md#select-the-front-door-edge-location-for-the-request-anycast) routes the clients to their closest PoP.
+Traffic from the client first arrives at a Front Door PoP. Front Door has a [large number of PoPs](edge-locations-by-region.md) distributed worldwide, and [Azure Front Door's routing architecture](front-door-traffic-acceleration.md) automatically routes traffic to the closest available Front Door PoP.
 
 When the request is received by Front Door's PoP, Front Door uses your [custom domain name](front-door-custom-domain.md) to serve the request. Front Door performs [TLS offload](end-to-end-tls.md) by using either a Front Door-managed TLS certificate or a custom TLS certificate.