review

Signed-off-by: Hannah Hunter <[email protected]>

Author: hhunter-ms

articles/azure-functions/durable/TOC.yml

@@ -116,23 +116,23 @@
     href: ./durable-task-scheduler/durable-task-scheduler.md
   - name: Choosing an orchestration framework
     href: ./durable-task-scheduler/choose-orchestration-framework.md
-  - name: Concepts
-    items:
-    - name: Identity
-      href: ./durable-task-scheduler/durable-task-scheduler-identity.md
-    - name: Monitoring dashboard
-      href: ./durable-task-scheduler/durable-task-scheduler-dashboard.md
-    - name: Auto-purge 
-      href: ./durable-task-scheduler/durable-task-scheduler-auto-purge.md
+  - name: Create Durable Task Scheduler resources
+    href: ./durable-task-scheduler/develop-with-durable-task-scheduler.md
+  - name: Identity
+    href: ./durable-task-scheduler/durable-task-scheduler-identity.md
+  - name: Monitoring dashboard
+    href: ./durable-task-scheduler/durable-task-scheduler-dashboard.md
+  - name: Auto-purge 
+    href: ./durable-task-scheduler/durable-task-scheduler-auto-purge.md
   - name: Durable Functions
     items:
       - name: Throughput benchmark
         href: ./durable-task-scheduler/durable-task-scheduler-work-item-throughput.md
-      - name: Create Durable Task Scheduler resources
-        href: ./durable-task-scheduler/develop-with-durable-task-scheduler.md
+      - name: Durable Task Scheduler in Durable Functions
+        href: ./durable-task-scheduler/develop-with-durable-task-scheduler-functions.md
   - name: Durable Task SDKs
     items:
-    - name: Autoscale with the Durable Task SDKs in Azure Container Apps
+    - name: Configure autoscale for Azure Container Apps hosting
       href: ./durable-task-scheduler/durable-task-scheduler-auto-scaling.md
   - name: Billing
     href: ./durable-task-scheduler/durable-task-scheduler-dedicated-sku.md
@@ -166,7 +166,7 @@
       items:
       - name: Durable Functions
         href: /python/api/azure-functions-durable/azure.durable_functions
-      - name: Resource Management - Durable Task SDK
+      - name: Durable Task SDK - Management APIs
         href: /python/api/azure-mgmt-durabletask/azure.mgmt.durabletask
     - name: Java API
       items:

articles/azure-functions/durable/durable-functions-mssql-container-apps-hosting.md

@@ -1,23 +1,21 @@
 ---
-title: "Host a Durable Functions app in Azure Container Apps"
+title: Host a Durable Functions app in Azure Container Apps (preview)
 description: Learn how to host a Durable Functions app using the MSSQL backend in Azure Container Apps.
 ms.topic: how-to
 ms.date: 05/06/2025
 ---
 
-# Host a Durable Functions app in Azure Container Apps (.NET isolated)
+# Host a Durable Functions app in Azure Container Apps (preview)
 
-While Durable Functions supports several [storage providers](./durable-functions-storage-providers.md) or *backends*, autoscaling of the app is only available when using the Microsoft SQL (MSSQL) backend. If another backends is used, you need to [manually set up scaling](../functions-container-apps-hosting.md#event-driven-scaling) today.
+While Durable Functions supports several [storage providers](./durable-functions-storage-providers.md) or *backends*, autoscaling apps hosted in Azure Container Apps is only available with the Microsoft SQL (MSSQL) backend. If another backend is used, you need to [manually set up scaling](../functions-container-apps-hosting.md#event-driven-scaling).
 
 In this article, you learn how to:
 
 > [!div class="checklist"]
 >
-> - Create a local Durable Functions project with a cusom Dockerfile. 
-> - Run the worker and client projects.
-> - Review orchestration status and history via the Durable Task Scheduler dashboard.
-
- shows how to host a Durable Functions app in Azure Container Apps. 
+> - Create a Docker image from a local Durable Functions project. 
+> - Create an Azure Container App and related resources.
+> - Deploy the image to the Azure Container App and set up authentication.
 
 ## Prerequisites 
 
@@ -31,7 +29,7 @@ In this article, you learn how to:
 
 ## Create a local Durable Functions project
 
-In Visual Studio Code, [create a .NET isolated Durable Functions project configured to use the MSSQL backend](./quickstart-mssql.md). 
+In Visual Studio Code, [create a **.NET isolated** Durable Functions project configured to use the MSSQL backend](./quickstart-mssql.md). 
 
 [Test the app locally](./quickstart-mssql.md#test-locally) and return to this article. 
 
@@ -213,17 +211,15 @@ A [workload profile](../functions-container-apps-hosting.md#hosting-and-workload
 
 ### Create databases
 
-The function app requires an Azure Storage account and an Azure SQL Database as its storage backend. The Azure SQL Database backend persists state information as your orchestrations run. 
-
 1. Create an Azure Storage account, which is required by the function app.
 
    ```azurecli
    az storage account create --name $storage --location $location --resource-group $resourceGroup --sku Standard_LRS
    ```
 
-1. In the Azure portal, you can [create an Azure SQL database](/azure/azure-sql/database/single-database-create-quickstart). During creation:
-    - Enable Azure services and resources to access this server (under _Networking_)
-    - Set the value for _Database collation_ (under _Additional settings_) to `Latin1_General_100_BIN2_UTF8`.
+1. In the Azure portal, [create an Azure SQL database](/azure/azure-sql/database/single-database-create-quickstart) to persist state information. During creation:
+    - Enable Azure services and resources to access this server (under **Networking**)
+    - Set the value for **Database collation** (under **Additional settings**) to `Latin1_General_100_BIN2_UTF8`.
 
 > [!NOTE] 
 > Refrain from enabling the **Allow Azure services and resources to access this server** setting for production scenarios. Production applications should implement more secure approaches, such as stronger firewall restrictions or virtual network configurations.

articles/azure-functions/durable/durable-task-scheduler/choose-orchestration-framework.md

@@ -127,10 +127,9 @@ Walk through one of the following quickstarts to configure your applications to
 | **Local development quickstart** | [Create an app with Durable Task SDKs and Durable Task Scheduler](./quickstart-portable-durable-task-sdks.md) using either the .NET, Python, or Java SDKs. | Run a fan-in/fan-out orchestration locally using the Durable Task Scheduler emulator and review orchestration history using the dashboard. |
 | **Deploy to Azure Container Apps using Azure Developer CLI** | [Configure Durable Task SDKs in your container app with Azure Functions Durable Task Scheduler][./quickstart-container-apps-durable-task-sdk.md] | Deploy a function chaining pattern solution using the Azure Developer CLI. |
 
-## Limitations
- 
-- **The Durable Task Framework (DTFx) support**
-   - DTFx is an open-source .NET orchestration framework similar to the .NET Durable Task SDK. While it *can* be used to build apps that run on platforms like Azure Kubernetes Services, **DTFx doesn't receive official Microsoft support**.
+
+> [!NOTE]
+> The Durable Task Framework (DTFx) is an open-source .NET orchestration framework similar to the .NET Durable Task SDK. While it *can* be used to build apps that run on platforms like Azure Kubernetes Services, **DTFx doesn't receive official Microsoft support**.
 
 ## Next steps
 

articles/azure-functions/durable/durable-task-scheduler/durable-task-scheduler-auto-purge.md

@@ -7,7 +7,7 @@ ms.date: 05/06/2025
 
 # Set autopurge retention policies for Azure Functions Durable Task Scheduler (preview)
 
-Orchestration history data should be purged periodically to free up storage resources. Otherwise, the app observes performance degradation as history data accumulates overtime. The Durable Task Scheduler offers a lightweight, configurable autopurge feature that helps you manage orchestration data clean-up without manual intervention.
+To prevent reaching the memory limit of a [capacity unit (CU)](./durable-task-scheduler-dedicated-sku.md#dedicated-sku-concepts), it's best practice to periodically purge orchestration history data. The Durable Task Scheduler offers a lightweight, configurable autopurge feature that helps you manage orchestration data clean-up without manual intervention.
 
 Autopurge operates asynchronously in the background, optimized to minimize system resource usage and prevent interference with other Durable Task operations. Although autopurge doesn't adhere to a strict schedule, its clean-up rate generally aligns with your orchestration scheduling rate.
 

articles/azure-functions/durable/durable-task-scheduler/durable-task-scheduler-auto-scaling.md

@@ -1,17 +1,20 @@
 ---
-title: "Autoscaling in Azure Container Apps pattern for the Durable Task SDKs"
+title: "Configure autoscaling for Durable Task SDK app hosted in Azure Container Apps (preview)"
 description: Learn how to implement autoscaling with the Durable Task Scheduler using the Durable Task .NET SDK in Azure Container Apps.
 ms.subservice: durable-task-scheduler
 ms.topic: how-to
 ms.date: 05/06/2025
 ---
 
-# Autoscaling in Azure Container Apps pattern for the Durable Task SDKs
+# Configure autoscaling for Durable Task SDK app hosted in Azure Container Apps (preview)
 
 You can implement autoscaling in container apps that use the Durable Task Scheduler. Autoscaling maintains the reliability and scalability of long-running workflows by adapting to changing demands without manual intervention. 
 
 Control autoscaling by setting the range of application replicas deployed in response to an orchestration, activity, or entity being triggered. The scaler dynamically adjusts the number of container app replicas within that range, allowing your solution to handle spikes in the workload and prevent resource exhaustion. 
 
+> [!NOTE]
+> Autoscaling is supported for apps built using the Durable Task SDKs and hosted in Azure Container Apps.
+
 ## Configure the autoscaler
 
 You can set the autoscaler configuration via the Azure portal, a Bicep template, and the Azure CLI. 
@@ -95,7 +98,7 @@ az containerapp create \
 
 ## Experiment with the sample
 
-The [Autoscaling in Azure Container Apps sample](https://github.com/Azure-Samples/Durable-Task-Scheduler/tree/main/samples/scenarios/AutoscalingInACA) demonstrates how to implement autoscaling with the Azure Durable Task Scheduler using the .NET SDK in Azure Container Apps. The function chaining application pattern showcases an orchestration workflow that benefits from dynamically scaling worker instances based on load.
+In the [Autoscaling in Azure Container Apps sample](https://github.com/Azure-Samples/Durable-Task-Scheduler/tree/main/samples/scenarios/AutoscalingInACA), you use the Azure Developer CLI to implement autoscaling for a container app built with the .NET Durable Task SDK and hosted in Azure Container Apps. The sample showcases an orchestration using the function chaining pattern.
 
 > [!NOTE]
 > Although this sample uses the Durable Task .NET SDK, autoscaling is language-agnostic.

articles/azure-functions/durable/durable-task-scheduler/durable-task-scheduler-dedicated-sku.md

@@ -29,6 +29,12 @@ The following table explains the minimum cost and features provided with each CU
 
 Find the price of a capacity unit in a given region on the [Azure Functions pricing page](https://azure.microsoft.com/pricing/details/functions/). 
 
+## Rate limit
+
+For scheduling new orchestrations, a limit of 200 requests per second per capacity unit applies for the *scheduler* globally, across all task hubs. 
+
+If the rate limit is exceeded, the gRPC status code `RESOURCE_EXHAUSTED` is returned. This code is similar to HTTP `429 (Too many requests)`.
+
 ## Determine the number of Capacity Units needed
 
 > [!NOTE]

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

@@ -19,7 +19,7 @@ You can grant the following Durable Task Scheduler related roles to an identity:
 | **Durable Task Data Reader** | Role to read all Durable Task Scheduler data. Assign this role if you only need a list of orchestrations and entities payloads. |
 
 > [!NOTE]
-> Most computes require the *Durable Task Data Contributor* role. 
+> Most Durable Functions apps require the *Durable Task Data Contributor* role. 
 
 In this article, you learn how to grant permissions to an identity resource and configure your compute app to use the identity for access to schedulers and task hubs. 
 

articles/azure-functions/durable/quickstart-mssql.md

@@ -66,7 +66,8 @@ In Visual Studio Code, create a local Azure Functions project.
 
 Visual Studio Code installs Azure Functions Core Tools if it's required to create the project. It also creates a function app project in a folder. This project contains the [host.json](../functions-host-json.md) and [local.settings.json](../functions-develop-local.md#local-settings-file) configuration files.
 
-Another file, *HelloOrchestration.cs*, contains the basic building blocks of a Durable Functions app:
+Another file, *HelloOrchestration.cs*, contains the basic building blocks of a Durable Functions app:  
+
 | Method | Description |
 | -----  | ----------- |
 | `HelloOrchestration` | Defines the Durable Functions app orchestration. In this case, the orchestration starts, creates a list, and then adds the result of three functions calls to the list. When the three function calls finish, it returns the list. |