copyedit

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

Author: hhunter-ms

articles/container-apps/workflows-overview.md

@@ -2,7 +2,7 @@
 title: Workflows in Azure Container Apps
 description: Learn about your workflow options for Azure Container Apps.
 services: container-apps, azure-functions
-author: hhunter-ms
+author: lilyjma
 ms.service: azure-container-apps
 ms.topic: overview
 ms.date: 04/29/2025
@@ -11,42 +11,58 @@ ms.reviewer: cshoe, hannahhunter
 ---
 
 # Workflows in Azure Container Apps
-Workflows are multi-step operations that may need to happen in a certain order and/or involve long-running tasks. Some real-world scenarios that require workflows include:
+
+> [!NOTE]
+> You might see workflows referred to as *orchestrations*, especially in the context of Durable Functions. To avoid confusion with container orchestrations, this article uses the term *workflows* instead. 
+
+Workflows are multi-step operations that usually occur in a specific order or involve long-running tasks. Real-world scenarios requiring workflows include:
 - Order processing
-- AI agents 
-- Infrastructure management 
-- Data processing pipeline 
+- AI agents
+- Infrastructure management
+- Data processing pipelines 
 
-Because workflows involve multiple steps and could be long-running, execution may be interrupted by events such as temporary infrastructure failures or dependency downtime. As such, it's important to have *durable execution*, i.e. execution continues from the point of failure instead of restarting in the event of temporary failures.
+Execution may be interrupted by events such as temporary infrastructure failures or dependency downtime. To prevent interruptions, you can leverage durable execution, which continues from the point of failure instead of restarting.
 
-Azure provides two code-oriented workflow frameworks you can use to build apps that run on Azure Container Apps: **Durable Task SDKs** (currently in public preview) and **Durable Functions**. These frameworks continuously checkpoint workflow state as the app runs and automatically handle retries to ensure durable execution. 
+Azure provides two code-oriented workflow frameworks you can use to build apps that run on Azure Container Apps: 
+- **Durable Task SDKs** (preview)
+- **Durable Functions** 
 
-> [!NOTE]
-> You might see workflows referred to as *orchestrations*, especially in the context of Durable Functions. To avoid creating confusion with container orchestrations, this article refrains from using orchestrations to refer to workflows. 
+These frameworks continuously checkpoint workflow state as the app runs and automatically handles retries to ensure durable execution. 
 
 ## Workflow frameworks for developers in Azure
-The workflow frameworks described in this section are designed for developers and are available in multiple programming languages. 
 
-### Durable Task SDKs (public preview)
-The Durable Task SDKs are lightweight client SDKs that provide a relatively un-opinionated programming model for authoring workflows. They allow your app to connect to a workflow engine called the [Durable Task Scheduler](/articles/azure-functions/durable/durable-task-scheduler/durable-task-scheduler.md) hosted in Azure. 
+The Durable Task SDKs and Durable Functions workflow frameworks are designed for developers and available in multiple programming languages. 
+
+### Durable Task SDKs (preview)
+
+The Durable Task SDKs are lightweight client SDKs that provide an un-opinionated programming model for authoring workflows. They allow your app to connect to a workflow engine hosted in Azure called the [Durable Task Scheduler](../azure-functions/durable/durable-task-scheduler/durable-task-scheduler.md). 
 
-To ensure durable execution, the Durable Task SDKs require a storage backend to persist workflow state as the app runs. In this case, the Durable Task Scheduler also plays the role of the backend for apps leveraging the Durable Task SDKs. 
+To ensure durable execution, the Durable Task SDKs require a storage backend to persist workflow state as the app runs. The Durable Task Scheduler works as the backend for apps using the Durable Task SDKs. 
 
 #### Quickstarts
-- [.NET](/articles/azure-functions/durable/durable-task-scheduler/quickstart-portable-durable-task-sdks.md) 
-- [Python](/articles/azure-functions/durable/durable-task-scheduler/quickstart-portable-durable-task-sdks.md) 
-- [Java](/articles/azure-functions/durable/durable-task-scheduler/quickstart-portable-durable-task-sdks.md)  
+
+Try out configuring the Durable Task SDKs for your container app using the following quickstarts.
+
+| Quickstart | Description | 
+| ---------- | ----------- |
+| [Configure a Durable Task SDK in your application](../azure-functions/durable/durable-task-scheduler/quickstart-portable-durable-task-sdks.md) | Learn how to create workflows that use the fan-out/fan-in Durable Functions application pattern. Currently available with the .NET, Python, and Java Durable Task SDKs. |
+| [Configure a Durable Task SDK in your container app][TODO] | Use the Azure Developer CLI to create Durable Task Scheduler resources and deploy them to Azure with two container apps running workflow tasks. Currently available with the .NET, Python, and Java Durable Task SDKs. |
 
 ### Durable Functions 
-[Durable Functions](/articles/azure-functions/durable/durable-functions-overview.md) is the other code-oriented workflow framework in Azure. As part of Azure Functions, Durable Functions inherits many of its characteristics. Examples include:
-- Integrations with other Azure services through Azure Functions [triggers and bindings](/articles/azure-functions/functions-triggers-bindings.md)
+
+As a feature of Azure Functions, [Durable Functions](../azure-functions/durable/durable-functions-overview.md) inherits many of its characteristics as a code-oriented workflow framework offering in Azure. For example, with Durable Functions, you benefit from:
+- Integrations with other Azure services through Azure Functions [triggers and bindings](../azure-functions/functions-triggers-bindings.md)
 - Local development experience
 - Serverless pricing model
 
-If you want to host a Durable Functions app in Azure Container Apps, you must use the [Microsoft SQL backend](/articles/azure-functions/durable/durable-functions-storage-providers.md#microsoft-sql-server-mssql) today for state persistence. 
+> [!NOTE]
+> Durable Functions with Durable Task Scheduler currently only runs in App Service and Elastic Premium SKUs. Until it's available in other SKUs (like Flex Consumption), you need to use the [Microsoft SQL backend](../azure-functions/durable/durable-functions-storage-providers.md#microsoft-sql-server-mssql) for state persistence when hosting a Durable Functions app in Azure Container Apps. 
 
 ## How to choose 
-You can host apps built using either the Durable Task SDKs or Durable Functions in Azure Container Apps. See [guidance for choosing the framework](/articles/azure-functions/durable/durable-task-scheduler/choose-orchestration-framework.md) you need. 
+
+Applications built using either the Durable Task SDKs or Durable Functions can be hosted in Azure Container Apps. [Learn which framework works best for your scenario](../azure-functions/durable/durable-task-scheduler/choose-orchestration-framework.md). 
 
 ## Next steps
-- Learn more about the [Durable Task Scheduler](/articles/azure-functions/durable/durable-task-scheduler/durable-task-scheduler.md) 
+
+> [!div class="nextstepaction"]
+> [Learn more about the Durable Task Scheduler](../azure-functions/durable/durable-task-scheduler/durable-task-scheduler.md)