update hosting model etc

hhunter-ms · hhunter-ms · commit 3ed4773529e1 · 2026-03-04T14:14:06.000-05:00
Signed-off-by: Hannah Hunter &lt;94493363+hhunter-ms@users.noreply.github.com&gt;
diff --git a/articles/azure-functions/durable/TOC.yml b/articles/azure-functions/durable/TOC.yml
@@ -5,7 +5,7 @@
   items:
   - name: What is Durable Task?
     href: what-is-durable-task.md
-  - name: Choose your hosting option
+  - name: Choose your hosting model
     href: choose-orchestration-framework.md
 - name: Quickstarts
   items:
diff --git a/articles/azure-functions/durable/choose-orchestration-framework.md b/articles/azure-functions/durable/choose-orchestration-framework.md
@@ -1,5 +1,5 @@
 ---
-title: Choose your hosting option
+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 hosting option
+# 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
 
@@ -111,16 +115,16 @@ Learn more: [Task hubs](durable-functions-task-hubs.md)
 
 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. |
diff --git a/articles/azure-functions/durable/durable-functions-overview.md b/articles/azure-functions/durable/durable-functions-overview.md
@@ -15,7 +15,7 @@ ms.subservice: durable
 Durable Functions is an extension of [Azure Functions](../functions-overview.md) that lets you build stateful workflows in a serverless environment by writing orchestrator, activity, and entity functions in code. The Durable Functions runtime manages state, checkpoints, retries, and recovery so your workflows can run reliably for long periods.
 
 > [!TIP]
-> Not sure whether to use Durable Functions or the standalone Durable Task SDKs? See [Choose your hosting option](choose-orchestration-framework.md).
+> Not sure whether to use Durable Functions or the standalone Durable Task SDKs? See [Choose your hosting model](choose-orchestration-framework.md).
 
 ## Supported languages
 
@@ -48,6 +48,6 @@ After your first workflow is running, explore [Task hubs](durable-functions-task
 > [Create your first durable function (C#)](durable-functions-isolated-create-first-csharp.md)
 
 - [What is Durable Task?](what-is-durable-task.md)
-- [Choose your hosting option](choose-orchestration-framework.md)
+- [Choose your hosting model](choose-orchestration-framework.md)
 - [Durable Functions storage providers](durable-functions-storage-providers.md)
 - [Durable Task Scheduler overview](durable-task-scheduler/durable-task-scheduler.md)
diff --git a/articles/azure-functions/durable/durable-orchestration-versioning.md b/articles/azure-functions/durable/durable-orchestration-versioning.md
@@ -437,7 +437,7 @@ Here's what to expect when you deploy your updated orchestrator function with th
 - **Old worker restrictions**: Old workers can process only the orchestrations with a version equal to or lower than the version specified in their own `defaultVersion` in `host.json`, because they aren't expected to have orchestrator code compatible with newer versions.
 
 > [!NOTE]
-> Orchestration versioning doesn't affect worker lifecycle. The Azure Functions platform manages worker setup and decommissioning based on regular rules depending on hosting options.
+> Orchestration versioning doesn't affect worker lifecycle. The Azure Functions platform manages worker setup and decommissioning based on regular rules depending on hosting models.
 
 ## Example: Replace an activity in the sequence
 
diff --git a/articles/azure-functions/durable/durable-task-scheduler/includes/function-app-integrated-creation.md b/articles/azure-functions/durable/durable-task-scheduler/includes/function-app-integrated-creation.md
@@ -7,7 +7,7 @@ ms.date: 03/19/2025
 
 1. Navigate to the Function app creation blade. 
 
-   :::image type="content" source="../media/create-durable-task-scheduler/function-app-hosted-app-service.png" alt-text="Screenshot of hosting options for Function apps.":::
+   :::image type="content" source="../media/create-durable-task-scheduler/function-app-hosted-app-service.png" alt-text="Screenshot of hosting models for Function apps.":::
 
 1. In the **Create Function App (Flex Consumption)** blade, fill in the information in the **Basics** tab. 
 
diff --git a/articles/azure-functions/durable/index.yml b/articles/azure-functions/durable/index.yml
@@ -30,7 +30,7 @@ landingContent:
             url: ./durable-task-scheduler/durable-task-overview.md
       - linkListType: concept
         links:
-          - text: Choose your hosting option
+          - text: Choose your hosting model
             url: choose-orchestration-framework.md
           - text: Programming model
             url: programming-model-overview.md
diff --git a/articles/azure-functions/durable/quickstart-mssql.md b/articles/azure-functions/durable/quickstart-mssql.md
@@ -84,7 +84,7 @@ For more information about these functions, see [Durable Functions types and fea
 > [!NOTE]
 > If you already have an MSSQL-compatible database, you can skip this section and skip the next section on setting up a Docker-based local database.
 
-Because the MSSQL backend is designed for portability, you have several options to set up your backing database. For example, you can set up an on-premises SQL Server instance, use a fully managed instance of [Azure SQL Database](/azure/azure-sql/database/sql-database-paas-overview), or use any other SQL Server-compatible hosting option.
+Because the MSSQL backend is designed for portability, you have several options to set up your backing database. For example, you can set up an on-premises SQL Server instance, use a fully managed instance of [Azure SQL Database](/azure/azure-sql/database/sql-database-paas-overview), or use any other SQL Server-compatible hosting model.
 
 You can also do local, offline development by using [SQL Server Express](https://www.microsoft.com/sql-server/sql-server-downloads) on your local Windows computer or use a [SQL Server Docker image](https://hub.docker.com/_/microsoft-mssql-server) running in a Docker container.
 
diff --git a/articles/azure-functions/durable/what-is-durable-task.md b/articles/azure-functions/durable/what-is-durable-task.md
@@ -18,7 +18,10 @@ Durable Task is Microsoft's technology for building workflows and orchestrations
 
 Workflows can run for hours, days, or even months, reliably resuming from the last completed step after any crash, restart, or redeployment. Common use cases include distributed transactions, multi-agent AI orchestration, data processing pipelines, and infrastructure management.
 
-Durable Task encompasses the **[Durable Task SDKs](./choose-orchestration-framework.md)** for self-hosted applications, **[Durable Functions](durable-functions-overview.md)** for serverless hosting on Azure Functions, and the **[Durable Task Scheduler](./durable-task-scheduler/durable-task-scheduler.md)** - a fully managed backend service purpose-built for durable workloads.
+Durable Task encompasses:
+- The **[Durable Task SDKs](./durable-task-scheduler/durable-task-overview.md)** for self-hosted applications.
+- The **[Durable Functions](durable-functions-overview.md)** for serverless hosting on Azure Functions
+- The **[Durable Task Scheduler](./durable-task-scheduler/durable-task-scheduler.md)**, a fully managed backend service purpose-built for durable workloads.
 
 > [!NOTE]
 > *Durable execution* is an industry-wide approach to making ordinary code fault-tolerant by automatically persisting its progress. Durable Task is Microsoft's implementation of durable execution.
@@ -51,7 +54,7 @@ Durable Task supports multiple programming languages across two hosting models:
 > [!NOTE]
 > [Go](https://github.com/microsoft/durabletask-go) is also available as a community-supported, open-source SDK for self-hosted scenarios, but is currently in experimental stages and not yet recommended for production use.
 
-For guidance on choosing between Azure Functions and self-hosted, see [Choose your hosting option](./choose-orchestration-framework.md).
+For guidance on choosing between Azure Functions and self-hosted, see [Choose your hosting model](./choose-orchestration-framework.md).
 
 ## Architectural components
 
@@ -61,7 +64,7 @@ Durable Task has two main layers: an **SDK** that you use in your application co
 
 The Durable Task SDK is what you use to author orchestrations, activities, and entities in your application code. It internally handles the mechanics of durable execution - replaying orchestrator functions, managing local execution context, and communicating with the state storage backend. Durable Task offers several SDK options for the different languages and hosting models mentioned previously.
 
-For guidance on choosing between these options, see [Choose your hosting option](./choose-orchestration-framework.md).
+For guidance on choosing between these options, see [Choose your hosting model](./choose-orchestration-framework.md).
 
 ### State storage backend
 
@@ -91,7 +94,9 @@ The following video highlights the benefits of Azure Durable Functions:
 ## Next steps
 
 > [!div class="nextstepaction"]
-> [Choose your hosting option](./choose-orchestration-framework.md)
+> [Choose your hosting model](./choose-orchestration-framework.md)
 
-> [!div class="nextstepaction"]
-> [Learn about the Durable Task Scheduler](./durable-task-scheduler/durable-task-scheduler.md)
+- Get started with:
+  - [The Durable Task SDKs](./durable-task-scheduler/durable-task-overview.md)
+  - [Durable Functions](./durable-functions-overview.md)
+- [The Durable Task Scheduler](./durable-task-scheduler/durable-task-scheduler.md)
