Merge pull request #312597 from hhunter-ms/final-copyedit

[Durable] Copyedit

Author: JamesJBarnett

articles/azure-functions/durable/TOC.yml

@@ -5,8 +5,12 @@
   items:
   - name: What is Durable Task?
     href: what-is-durable-task.md
-  - name: Choose your programming model
+  - name: Choose your hosting model
     href: choose-orchestration-framework.md
+  - name: About Durable Functions
+    href: durable-functions-overview.md
+  - name: About the Durable Task SDKs
+    href: ./durable-task-scheduler/durable-task-overview.md
 - name: Quickstarts
   items:
   - name: Durable Functions
@@ -227,8 +231,6 @@
         href: https://azure.microsoft.com/updates/?product=functions&updatetype=&platform=
 - name: Durable Task SDKs
   items:
-  - name: Overview
-    href: ./durable-task-scheduler/durable-task-overview.md
   - name: Tutorials
     items:
     - name: Configure autoscale for Azure Container Apps hosting

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

@@ -1,5 +1,5 @@
 ---
-title: Choose your programming model
+title: Choose your hosting model
 description: Learn how your hosting platform determines whether to use Durable Functions for Azure Functions or the standalone Durable Task SDKs for self-hosted scenarios.
 author: cgillum
 ms.author: cgillum
@@ -9,20 +9,24 @@ ms.topic: concept-article
 ms.service: azure-functions
 ms.subservice: durable
 titleSuffix: Durable Task
-#Customer intent: As a developer, I want to understand which Durable Task programming model to use based on my hosting platform.
+#Customer intent: As a developer, I want to understand which Durable Task hosting model to use based on my hosting platform.
 ---
 
-# Choose your programming model
+# Choose your hosting model
 
-As described in [What is Durable Task?](what-is-durable-task.md), the Durable Task framework supports two hosting models: **Azure Functions** (via Durable Functions) and **self-hosted** (via the standalone Durable Task SDKs). Both hosting models provide the same core durable execution capabilities (orchestrations, activities, timers, external events, and more) but differ in how your application is hosted, scaled, and deployed.
+As described in [What is Durable Task?](what-is-durable-task.md), the Durable Task framework supports two hosting models: 
+- **Azure Functions** (via [Durable Functions](./durable-functions-overview.md))
+- **Self-hosted** (via [the standalone Durable Task SDKs](./durable-task-scheduler/durable-task-overview.md)). 
 
-In general, where your application runs determines which programming model you use. If you're building on Azure Functions, you use Durable Functions. If you're building on any other compute platform, you use the standalone Durable Task SDKs.
+Both hosting models provide the same core durable execution capabilities (orchestrations, activities, timers, external events, and more) but differ in how your application is hosted, scaled, and deployed.
+
+In general, where your application runs determines which hosting model you use. If you're building on Azure Functions, you use Durable Functions. If you're building on any other compute platform, you use the standalone Durable Task SDKs.
 
 ## Choosing based on hosting platform
 
-If you already know your application's hosting platform, the following table can help you determine which programming model to use:
+If you already know your application's hosting platform, the following table can help you determine which hosting model to use:
 
-| Hosting platform | Programming model |
+| Hosting platform | Hosting model |
 | - | - |
 | **Azure Functions** (Consumption, Flex Consumption, Premium) | Durable Functions |
 | **Azure Container Apps** (with Azure Functions runtime) | Either |
@@ -31,11 +35,11 @@ If you already know your application's hosting platform, the following table can
 | **Virtual machines or on-premises** | Standalone Durable Task SDKs |
 
 > [!NOTE]
-> Azure App Service and Azure Container Apps can both host the Azure Functions runtime, either through [fully managed Azure Functions integration](../functions-scale.md#overview-of-plans) or by deploying the Functions runtime directly. Thus, both platforms support either programming model. For more information on Azure Functions hosting options, see [Azure Functions hosting plans](../functions-scale.md).
+> Azure App Service and Azure Container Apps can both host the Azure Functions runtime, either through [fully managed Azure Functions integration](../functions-scale.md#overview-of-plans) or by deploying the Functions runtime directly. Thus, both platforms support either hosting model. For more information on Azure Functions hosting models, see [Azure Functions hosting plans](../functions-scale.md).
 
-## Comparing the programming models
+## Comparing the hosting models
 
-The following table summarizes the key differences between the two programming models:
+The following table summarizes the key differences between the two hosting models:
 
 | | Durable Functions (Azure Functions) | Standalone Durable Task SDKs (self-hosted) |
 | - | - | - |
@@ -51,7 +55,7 @@ The following table summarizes the key differences between the two programming m
 >
 > The [Flex Consumption](../flex-consumption-plan.md) hosting plan offers [an "always read instances" concept](../flex-consumption-plan.md#always-ready-instances) as cold start mitigation.
 > 
-> Learn more about [Azure Functions hosting options](../functions-scale.md).
+> Learn more about [Azure Functions hosting models](../functions-scale.md).
 
 ### Built-in HTTP APIs
 
@@ -60,7 +64,7 @@ Azure Functions provides HTTP endpoints for your functions app, which the Durabl
 When using the Durable Task SDKs, you need to implement your own HTTP endpoints depending on your hosting compute.
 
 | Feature | Durable Functions | Durable Task SDKs |
-|---------|-------------------|-------------------|
+| ------- | ----------------- | ----------------- |
 | **Management HTTP APIs** | ✅ Built-in | ❌ Implement your own |
 | **Automatic status URLs** | ✅ Built-in | ❌ Implement your own |
 
@@ -84,10 +88,10 @@ Learn more: [Manage orchestration instances](durable-functions-instance-manageme
 Durable Functions supports multiple storage backends, while the Durable Task SDKs exclusively use the Durable Task Scheduler.
 
 > [!TIP]
-> The **Durable Task Scheduler** is a fully managed Azure service that handles orchestration state persistence and execution. It's provisioned as a separate Azure resource with its own [pricing](./durable-task-scheduler/durable-task-scheduler-dedicated-sku.md). It's the recommended backend for Durable Functions and the only supported backend for the Durable Task SDKs.
+> The **Durable Task Scheduler** is a fully managed Azure service that handles orchestration state persistence and execution. It's provisioned as a separate Azure resource with its own [pricing](./durable-task-scheduler/durable-task-scheduler-billing.md). It's the recommended backend for Durable Functions and the only supported backend for the Durable Task SDKs.
 
 | Storage provider | Durable Functions | Durable Task SDKs |
-|------------------|-------------------|-------------------|
+| ---------------- | ----------------- | ----------------- |
 | **Durable Task Scheduler** | ✅ Recommended | ✅ Required |
 | **Azure Storage** | ✅ Supported | ❌ Not supported |
 | **Microsoft SQL Server** | ✅ Supported | ❌ Not supported |
@@ -104,23 +108,23 @@ Learn more: [Task hubs](durable-functions-task-hubs.md)
 ### Diagnostics and versioning
 
 | Feature | Durable Functions | Durable Task SDKs |
-|---------|-------------------|-------------------|
+| ------- | ----------------- | ----------------- |
 | **Durable Task Scheduler dashboard** | ✅ Yes | ✅ Yes |
 | **Application Insights** | ✅ Built-in | Manual setup |
 | **Zero-downtime deployment** | ✅ Functions slots | Platform-specific |
 
 Learn more: [Diagnostics](durable-functions-diagnostics.md) | [Versioning](durable-functions-versioning.md)
 
-Both programming models support the **[Durable Task Scheduler](./durable-task-scheduler/durable-task-scheduler.md)** as a state storage backend, which provides both state storage and extra monitoring capabilities. Durable Functions also supports several bring-your-own (BYO) storage options for scenarios that require them. For more information, see [Storage providers](durable-functions-storage-providers.md).
+Both hosting models support the **[Durable Task Scheduler](./durable-task-scheduler/durable-task-scheduler.md)** as a state storage backend, which provides both state storage and extra monitoring capabilities. Durable Functions also supports several bring-your-own (BYO) storage options for scenarios that require them. For more information, see [Storage providers](durable-functions-storage-providers.md).
 
 ## More considerations
 
-When choosing between the two programming models, consider the following factors:
+When choosing between the two hosting models, consider the following factors:
 
 | Choose Durable Functions if... | Choose standalone Durable Task SDKs if... |
 | - | - |
 | You want built-in Azure Functions triggers (HTTP, Queue, Timer, etc.). | You want full control over your container and its entry points. |
-| You're already familiar with the Azure Functions programming model. | You prefer a lightweight SDK without the Azure Functions runtime overhead. |
+| You're already familiar with the Azure Functions hosting model. | You prefer a lightweight SDK without the Azure Functions runtime overhead. |
 | You want Azure portal integration for function management. | You want the same code to be portable across container platforms (AKS, App Service, etc.). |
 | You need to choose from [multiple storage backends](durable-functions-storage-providers.md). | You have existing non-Functions application code to integrate with. |
 | You need **serverless, event-driven apps** that scale to zero. | You need **always-on, low-latency workloads** without cold start delays. |
@@ -139,7 +143,7 @@ All Durable Task SDKs are open source and available on GitHub. However, some SDK
 
 ### Durable Task Framework (Legacy)
 
-The [Durable Task Framework](https://github.com/Azure/durabletask) (DTFx) is an older, open-source .NET Durable Task library. While it provides similar orchestration primitives, it predates the modern Durable Task SDKs and doesn't include official Microsoft support or the latest features. It also requires you to manage hosting, operational infrastructure, and long-term maintenance themselves.
+The [Durable Task Framework](https://github.com/Azure/durabletask) (DTFx) is an older, open-source .NET Durable Task library. While it provides similar orchestration primitives, it predates the modern Durable Task SDKs and doesn't include official Microsoft support or the latest features. It also requires you to manage hosting, operational infrastructure, and long-term maintenance yourself.
 
 If you're starting a new project, we recommend using the modern Durable Task SDKs or Durable Functions instead.
 
@@ -152,15 +156,12 @@ The [Durable Task SDK for Go](https://github.com/Azure/durabletask-go) is a comm
 
 ## Next steps
 
-Once you've decided which framework to use, get started with the appropriate quickstart:
-
-- **Durable Functions**: [Create your first Durable Functions app](durable-functions-isolated-create-first-csharp.md)
-- **Durable Task SDKs**: [Create an app with Durable Task SDKs](durable-task-scheduler/quickstart-durable-task-scheduler.md)
-
-For more in-depth information:
+Get started with the framework you chose:
 
 > [!div class="nextstepaction"]
-> [Durable Functions overview](what-is-durable-task.md)
+> [Durable Functions overview](durable-functions-overview.md)
 
 > [!div class="nextstepaction"]
-> [Durable Task Scheduler overview](durable-task-scheduler/durable-task-scheduler.md)
+> [Durable Functions overview](./durable-task-scheduler/durable-task-overview.md)
+
+Then, learn more about the [Durable Task Scheduler backend provider](durable-task-scheduler/durable-task-scheduler.md).

articles/azure-functions/durable/durable-functions-azure-storage-provider.md

@@ -165,7 +165,7 @@ Storing payloads to local disks is *not* recommended, since on-disk state isn't
 
 ## Configuring the Azure storage provider
 
-The Azure Storage provider is the default storage provider and doesn't require any explicit configuration, NuGet package references, or extension bundle references. You can find the full set of **host.json** configuration options [here](durable-functions-bindings.md#durable-functions-settings-in-hostjson), under the `extensions/durableTask/storageProvider` path.
+The Azure Storage provider is the default storage provider and doesn't require any explicit configuration, NuGet package references, or extension bundle references. You can find the full set of [Durable Functions host.json configuration options](durable-functions-bindings.md#durable-functions-settings-in-hostjson) under the `extensions/durableTask/storageProvider` path.
 
 ### Connections
 
@@ -178,15 +178,16 @@ If the configured value is both an exact match for a single setting and a prefix
 
 ### Identity-based connections 
 
-If you are using [version 2.7.0 or higher of the extension](https://github.com/Azure/azure-functions-durable-extension/releases/tag/v2.7.0) and the Azure storage provider, instead of using a connection string with a secret, you can have the app use an [Microsoft Entra identity](../../active-directory/fundamentals/active-directory-whatis.md). To do this, you would define settings under a common prefix which maps to the `connectionName` property in the trigger and binding configuration.
+If you are using [version 2.7.0 or higher of the extension](https://github.com/Azure/azure-functions-durable-extension/releases/tag/v2.7.0) and the Azure storage provider, instead of using a connection string with a secret, you can have the app use an [Microsoft Entra identity](/entra/fundamentals/what-is-entra). To do this, you would define settings under a common prefix which maps to the `connectionName` property in the trigger and binding configuration.
 
 To use an identity-based connection for Durable Functions, configure the following app settings:
 
-|Property | Environment variable template                       | Description                                | Example value                                        |
-|-|-----------------------------------------------------|--------------------------------------------|------------------------------------------------|
-| Blob service URI | `<CONNECTION_NAME_PREFIX>__blobServiceUri`| The data plane URI of the blob service of the storage account, using the HTTPS scheme. | https://<storage_account_name>.blob.core.windows.net |
-| Queue service URI | `<CONNECTION_NAME_PREFIX>__queueServiceUri` | The data plane URI of the queue service of the storage account, using the HTTPS scheme. | https://<storage_account_name>.queue.core.windows.net |
-| Table service URI | `<CONNECTION_NAME_PREFIX>__tableServiceUri` | The data plane URI of a table service of the storage account, using the HTTPS scheme. | https://<storage_account_name>.table.core.windows.net |
+| Property | Environment variable template | Description | Example value |
+| -------- | ----------------------------- | ----------- | ------------- |
+| Blob service URI | `<CONNECTION_NAME_PREFIX>__blobServiceUri` | The data plane URI of the blob service of the storage account, using the HTTPS scheme. | `https://<storage_account_name>.blob.core.windows.net` |
+| Queue service URI | `<CONNECTION_NAME_PREFIX>__queueServiceUri` | The data plane URI of the queue service of the storage account, using the HTTPS scheme. | `https://<storage_account_name>.queue.core.windows.net` |
+| Table service URI | `<CONNECTION_NAME_PREFIX>__tableServiceUri` | The data plane URI of a table service of the storage account, using the HTTPS scheme. | `https://<storage_account_name>.table.core.windows.net` |
+<!-- markdownlint-enable MD044 -->
 
 Additional properties may be set to customize the connection. See [Common properties for identity-based connections](../functions-reference.md#common-properties-for-identity-based-connections).
 
@@ -231,7 +232,7 @@ Keep these considerations in mind when choosing the storage account for your Dur
 
 - For performance-sensitive workloads, configure a storage account other than the default account (`AzureWebJobsStorage`). Since Durable Functions uses Azure Storage heavily, using a dedicated storage account isolates Durable Functions storage usage from the internal usage by the Azure Functions host.
 - You need standard general purpose Azure Storage accounts when using the Azure Storage provider. All other storage account types aren't currently supported. 
-- Legacy v1 general purpose storage accounts for Durable Functions is recommended. The newer v2 storage accounts can be more expensive for Durable Functions workloads. [Learn more about Azure Storage account types](../../storage/common/storage-account-overview.md).
+- Legacy v1 general purpose storage accounts for Durable Functions are recommended. The newer v2 storage accounts can be more expensive for Durable Functions workloads. [Learn more about Azure Storage account types](../../storage/common/storage-account-overview.md).
 
 ## Orchestrator scale-out
 
@@ -373,7 +374,7 @@ The following table shows the [expected *maximum* throughput numbers for the sce
 | External event processing | 50 events per second, per instance |
 | Entity operation processing | 64 operations per second |
 
-If you aren't seeing the throughput numbers you expect and your CPU and memory usage appears healthy, check whether the cause is related to [the health of your storage account](../../storage/common/storage-monitoring-diagnosing-troubleshooting.md#troubleshooting-guidance). The Durable Functions extension can put significant load on an Azure Storage account, and sufficiently high loads may result in storage account throttling.
+If you aren't seeing the throughput numbers you expect and your CPU and memory usage appears healthy, check whether the cause is related to [the health of your storage account](/troubleshoot/azure/azure-storage/blobs/alerts/storage-monitoring-diagnosing-troubleshooting#troubleshooting-guidance). The Durable Functions extension can put significant load on an Azure Storage account, and sufficiently high loads may result in storage account throttling.
 
 > [!TIP]
 > In some cases, you can increase the throughput of external events, activity fan-in, and entity operations by increasing the value of the `controlQueueBufferThreshold` setting in your `host.json`. Increasing this value beyond its default causes the Durable Task Framework storage provider to use more memory to prefetch these events more aggressively, reducing delays associated with dequeueing messages from the Azure Storage control queues. For more information, see the [host.json](durable-functions-bindings.md#host-json) reference documentation.