fix links and quick sweep for any other dts instead of full name

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

Author: hhunter-ms

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

@@ -3,7 +3,7 @@ title: Durable Functions storage providers - Azure
 description: Learn about the different storage providers for Durable Functions and how they compare
 author: cgillum
 ms.topic: conceptual
-ms.date: 03/05/2025
+ms.date: 03/17/2025
 ms.author: azfuncdf
 #Customer intent: As a developer, I want to understand what storage providers are available Durable Functions and which one I should choose.
 ---

articles/azure-functions/durable/durable-task-scheduler/develop-with-durable-task-scheduler.md

@@ -3,7 +3,7 @@ title: Develop with the Azure Functions durable task scheduler (preview)
 description: Learn how to develop with the Azure Functions durable task scheduler and task hub resources
 author: lilyjma
 ms.topic: how-to
-ms.date: 02/27/2025
+ms.date: 03/17/2025
 ms.author: jiayma
 ms.reviewer: azfuncdf
 zone_pivot_groups: dts-devexp
@@ -62,11 +62,11 @@ Learn more about durable task scheduler [features](./durable-task-scheduler.md#f
    docker run -itP mcr.microsoft.com/dts/dts-emulator:v0.0.5
    ```
 
-The command above exposes a single task hub named `default`. If you need more than one task hub, you can set the environment variable `DTS_TASK_HUB_NAMES` on the container to a comma-delimited list of task hub names like below:
+    The command above exposes a single task hub named `default`. If you need more than one task hub, you can set the environment variable `DTS_TASK_HUB_NAMES` on the container to a comma-delimited list of task hub names like below:
 
-```bash
-docker run -itP -e DTS_TASK_HUB_NAMES=taskhub1,taskhub2,taskhub3 mcr.microsoft.com/dts/dts-emulator:v0.0.5
-```
+    ```bash
+    docker run -itP -e DTS_TASK_HUB_NAMES=taskhub1,taskhub2,taskhub3 mcr.microsoft.com/dts/dts-emulator:v0.0.5
+    ```
 
 ## Create a scheduler and task hub
 
@@ -154,8 +154,8 @@ docker run -itP -e DTS_TASK_HUB_NAMES=taskhub1,taskhub2,taskhub3 mcr.microsoft.c
 ::: zone pivot="az-portal" 
 
 You can create a scheduler and task hub on Azure portal via two ways: 
-- **Function app integrated creation:** *(recommended)* automatically creates the managed identity resource and RBAC assignment needed for your app to access durable task scheduler.
-- **Top-level creation:** Requires you to [manually assign RBAC](#configure-identity-based-authentication-for-app-to-access-durable-task-scheduler) to configure scheduler access for your app.
+- **Function app integrated creation:** *(recommended)* automatically creates the managed identity resource and RBAC assignment, plus configures required environment variables for your app to access durable task scheduler.
+- **Top-level creation:** Requires you to [manually assign RBAC permission](#configure-identity-based-authentication-for-app-to-access-durable-task-scheduler) to configure scheduler access for your app.
 
 > [!NOTE]
 > Durable task scheduler currently supports apps hosted in the **App Service** and **Functions Premium** plans, so this experience is available only when either of these plan types is picked. 
@@ -266,7 +266,16 @@ You can see all the task hubs created in a scheduler on the **Overview** of the
 
 Durable task scheduler **only** supports either *user-assigned* or *system-assigned* managed identity authentication. **User-assigned identities are recommended,** as they aren't tied to the lifecycle of the app and can be reused after the app is de-provisioned.
 
-The following sections demonstrate how to configure identity resources for your durable functions app to access a scheduler and its task hubs. 
+The following are the durable task scheduler related roles you can grant to an identity:
+
+ - **Durable Task Data Contributor**: Role for all data access operations. This role is a superset of all other roles. 
+ - **Durable Task Worker**: Role used by worker applications to interact with the durable task scheduler. Assign this role if your app is used *only* for processing orchestrations, activities, and entities. 
+ - **Durable Task Data Reader**: Role to read all durable task scheduler data. Assign this role if you only need listing of orchestrations and entities payloads. 
+
+> [!NOTE]
+> Most durable functions apps would require the Durable Task Data Contributor role. 
+
+The sections below demonstrate how to grant permissions to an identity resource and configure your durable functions app to use the identity for access to schedulers and task hubs. 
 
 ### Assign RBAC (role-based access control) to managed identity resource 
 

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

@@ -2,7 +2,7 @@
 title: Use the Dedicated SKU for Azure Functions durable task scheduler (preview)
 description: Learn about how the Dedicated SKU in Azure Functions durable task scheduler.
 ms.topic: conceptual
-ms.date: 03/14/2025
+ms.date: 03/17/2025
 ms.author: azfuncdf
 author: lilyjma
 ms.subservice: durable

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

@@ -7,12 +7,11 @@ ms.date: 03/17/2025
 
 # Debug and manage orchestrations using the Azure Functions durable task scheduler dashboard (preview)
 
-Observe, manage, and debug your task hub or scheduler's orchestations effectively using the durable task scheduler dashboard. Once you [assign the *Durable Task Data Contributor* role to your developer identity](./develop-with-durable-task-scheduler.md#accessing-durable-task-scheduler-dashboard), you can access the dashboard via either:
-- The task hub's dashboard endpoint URL in the Azure portal
-- Navigate to `https://dashboard.durabletask.io/` and your task endpoint to connect to it.  
-
-> [!NOTE]
-> Ensure [your developer identity (email) has the **Durable Task Data Contributor** role assigned to it](./develop-with-durable-task-scheduler.md#accessing-durable-task-scheduler-dashboard) before accessing the dashboard. 
+Observe, manage, and debug your task hub or scheduler's orchestations effectively using the durable task scheduler dashboard. The dashboard is available when you run the [durable task scheduler emulator](./durable-task-scheduler.md#emulator-for-local-development) locally or create a scheduler resource on Azure. 
+- **Running locally** doesn't require authentication. 
+- **Creating a scheduler resource on Azure** requires that you [assign the *Durable Task Data Contributor* role to your identity](./develop-with-durable-task-scheduler.md#accessing-durable-task-scheduler-dashboard). You can then access the dashboard via either:
+  - The task hub's dashboard endpoint URL in the Azure portal
+  - Navigate to `https://dashboard.durabletask.io/` and your task hub endpoint to connect to it.  
 
 ## Monitor orchestration progress and execution history
 

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

@@ -2,7 +2,7 @@
 title: Azure Functions durable task scheduler backend for durable functions (preview)
 description: Learn about the characteristics of the Azure Functions durable task scheduler backend.
 ms.topic: conceptual
-ms.date: 03/05/2025
+ms.date: 03/17/2025
 ms.author: azfuncdf
 author: hhunter-ms
 ms.subservice: durable
@@ -32,13 +32,13 @@ The following diagram shows the architecture of the durable task scheduler backe
 
 The durable task scheduler runs in Azure as a separate resource from the app. This separation allows the scheduler to scale independently of the app and provides better isolation between the two components. This isolation is important for several reasons:
 
-- **Reduced resource consumption**: BYO storage providers can consume a significant amount of CPU and memory resources. This resource consumption is due to the overhead of managing partitions and other complex state store interactions. By using a managed scheduler instead of a BYO storage provider, your app instances can run more efficiently and with less resource contention.
+- **Reduced resource consumption:** BYO storage providers can consume a significant amount of CPU and memory resources. This resource consumption is due to the overhead of managing partitions and other complex state store interactions. By using a managed scheduler instead of a BYO storage provider, your app instances can run more efficiently and with less resource contention.
 
-- **Fault isolation**: Stability or availability issues in the durable task scheduler will not affect the stability or availability of your connected apps. With BYO storage providers, instability in the backend provider (which is a complex component) can create instability in the app logic. By separating the scheduler from the app, you can reduce the risk of cascading failures and improve overall reliability.
+- **Fault isolation:** Stability or availability issues in the durable task scheduler will not affect the stability or availability of your connected apps. With BYO storage providers, instability in the backend provider (which is a complex component) can create instability in the app logic. By separating the scheduler from the app, you can reduce the risk of cascading failures and improve overall reliability.
 
-- **Independent scaling**: The scheduler resource can be scaled independently of the app, allowing for better infrastructure resource management and cost optimization. For example, multiple apps can share the same scheduler resource, improving overall resource utilization. This capability is especially useful for organizations with multiple teams or projects that require durable functions.
+- **Independent scaling:** The scheduler resource can be scaled independently of the app, allowing for better infrastructure resource management and cost optimization. For example, multiple apps can share the same scheduler resource, improving overall resource utilization. This capability is especially useful for organizations with multiple teams or projects that require durable functions.
 
-- **Improved support experience**: The durable task scheduler is a managed service, which means that Azure can provide better support and diagnostics for issues related to the scheduler. When using a BYO storage provider, you might need to troubleshoot issues related to the backend provider, which can be complex and time-consuming. A managed service allows Azure to take care of the underlying infrastructure and provide a more streamlined support experience.
+- **Improved support experience:** The durable task scheduler is a managed service, which means that Azure can provide better support and diagnostics for issues related to the scheduler. When using a BYO storage provider, you might need to troubleshoot issues related to the backend provider, which can be complex and time-consuming. A managed service allows Azure to take care of the underlying infrastructure and provide a more streamlined support experience.
 
 ### App connectivity
 
@@ -126,17 +126,17 @@ This benchmark showed that the durable task scheduler is roughly **five times fa
 
   The *Consumption*, *Flex Consumption*, and *Azure Container App* hosting plans aren't yet supported when using the durable task scheduler.
 
-- **Available regions**: Durable task scheduler resources can be created in a subset of Azure regions today. You can run the following command to get a list of the supported regions:  
+- **Available regions:** Durable task scheduler resources can be created in a subset of Azure regions today. You can run the following command to get a list of the supported regions:  
 
     ```bash
     az provider show --namespace Microsoft.DurableTask --query "resourceTypes[?resourceType=='schedulers'].locations | [0]" --out table
     ```
 
     Consider using the same region for your durable functions app and the durable task scheduler resources. Having these resources in different regions might impact performance and limit certain network-related functionality.
 
-- **Scheduler quota**: You can currently create up to **five schedulers per region** per subscription.
+- **Scheduler quota:** You can currently create up to **five schedulers per region** per subscription.
 
-- **Max payload size**: The durable task scheduler has a maximum payload size restrictions for the following JSON-serialized data types:
+- **Max payload size:** The durable task scheduler has a maximum payload size restrictions for the following JSON-serialized data types:
 
     | Data type | Max size |
     | --------- | -------- |
@@ -146,7 +146,7 @@ This benchmark showed that the durable task scheduler is roughly **five times fa
     | Orchestration custom status | 1 MB |
     | Entity state | 1 MB |
 
-- **Feature parity**: Some features might not be available in the durable task scheduler backend yet. For example, at the time of writing, the durable task scheduler doesn't support the following features:
+- **Feature parity:** Some features might not be available in the durable task scheduler backend yet. For example, at the time of writing, the durable task scheduler doesn't support the following features:
 
     - [Orchestration rewind](../durable-functions-instance-management.md#rewind-instances-preview)
     - [Extended sessions](../durable-functions-azure-storage-provider.md#extended-sessions)

articles/azure-functions/durable/durable-task-scheduler/includes/assign-dev-identity-rbac-portal.md

@@ -1,7 +1,7 @@
 ---
 ms.service: azure-functions
 ms.topic: include
-ms.date: 01/30/2025
+ms.date: 03/17/2025
 ms.author: jiayma
 ms.reviewer: azfuncdf
 author: lilyjma

articles/azure-functions/durable/durable-task-scheduler/includes/assign-rbac-portal.md

@@ -1,7 +1,7 @@
 ---
 ms.service: azure-functions
 ms.topic: include
-ms.date: 01/30/2025
+ms.date: 03/17/2025
 ---
 
 > [!NOTE] 

articles/azure-functions/durable/durable-task-scheduler/includes/function-app-integrated-creation.md

@@ -23,28 +23,28 @@ author: lilyjma
    | Do you want to deploy code or container image? | Keep the **Code** option selected. | 
    | Runtime stack | Select the runtime you're using for this quickstart. | 
    | Version | Select your runtimei stack version. | 
-   | Region | Select [one of the supported regions](../durable-task-scheduler.md). | 
+   | Region | Select [one of the supported regions](../durable-task-scheduler.md#limitations-and-considerations). | 
    | Operating System | Select your operating system. | 
 
 1. Select the **Durable Functions** tab. 
 
 1. Choose **Durable Task Scheduler** as the backend provider for your durable functions. 
 
-1. Create a scheduler resource. This action automatically creates a task hub.
+1. Create a scheduler resource. This action will automatically create a task hub.
 
    :::image type="content" source="../media/create-durable-task-scheduler/durable-func-tab.png" alt-text="Screenshot of creating an App Service plan Function app.":::
 
    | Field | Description | 
    | ----- | ----------- | 
    | Storage backend | Select **Durable Task Scheduler**. | 
-   | Region | Select the same region you selected in the Basics tab for your function app. | 
+   | Region | It is recommended that the scheduler and function app regions should be the same. | 
    | Durable task scheduler | Use the scheduler name offered, or click **Create new** to create a custom name. | 
-   | Plan | Select the **Dedicated** plan. | 
+   | Plan | Only **Dedicated** is available at the moment. | 
    | Capacity units | Currently, you can only choose one Capacity Unit as an option. | 
 
 1. Click **Review + create** to review the resource creation. 
 
-   A user-assigned managed identity with the required RBAC role has been created automatically so that the Function app can access durable task scheduler. You can find in the summary view information related to the managed identity resource, such as:
+   A user-assigned managed identity with the required RBAC permission will be created automatically so that the Function app can access durable task scheduler. You can find in the summary view information related to the managed identity resource, such as:
    - The RBAC assigned to it (*Durable Task Data Contributor*) 
    - The assignment scope (the scheduler or task hub name)
 

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

@@ -3,7 +3,7 @@ title: "Quickstart: Set a durable functions app to use Azure Functions durable t
 description: Learn how to configure an existing durable functions app to use Azure Functions durable task scheduler.
 author: lilyjma
 ms.topic: how-to
-ms.date: 03/05/2025
+ms.date: 03/17/2025
 ms.author: jiayma
 ms.reviewer: azfuncdf
 zone_pivot_groups: dts-runtime
@@ -28,7 +28,7 @@ In this quickstart, you configure a durable functions app to use the [durable ta
 ## Prerequisites
 
 This quickstart assumes you alredy have an Azure Functions project on your local computer with:
-- Durable functions added to your project include:
+- Durable functions added to your project including:
   - An [orchestrator function](../durable-functions-bindings.md#orchestration-trigger). 
   - A [client function](../durable-functions-bindings.md#orchestration-client) that triggers the durable functions app.
 - The project configured for local debugging.
@@ -180,7 +180,7 @@ Get the durable task scheduler emulator port number in [the next step](#set-up-d
 
 1. Run the application.
 
-   ```sh
+   ```bash
    func start
    ```
 
@@ -216,6 +216,8 @@ Get the durable task scheduler emulator port number in [the next step](#set-up-d
 1. Click on the *default* task hub to see its dashboard. 
 
 > [!NOTE] 
+> Learn more about the [durable task scheduler dashboard](./durable-task-scheduler-dashboard.md). 
+>
 > The [durable task scheduler emulator](./durable-task-scheduler.md#emulator-for-local-development) stores orchestration data in memory, which means all data is lost when it shuts down. 
 >
 > Running into issues testing? [See the troubleshooting guide.](./troubleshoot-durable-task-scheduler.md)
@@ -228,6 +230,8 @@ Create a durable task scheduler instance and Azure Functions app on Azure follow
 
 [!INCLUDE [function-app-integrated-creation](./includes/function-app-integrated-creation.md)]
 
+Resource deployment could take around 15 to 20 minutes. Once that is finished, you can deploy your app to Azure. 
+
 ### Deploy your function app to Azure
 
 [!INCLUDE [functions-publish-project-vscode](../../../../includes/functions-deploy-project-vs-code.md)]
@@ -244,17 +248,17 @@ If your app is running on the Functions Premium plan, turn on the *Runtime Scale
 
 Run the following command to get your function's URL: 
 
-```bash
-az functionapp function list --resource-group <RESOURCE_GROUP_NAME> --name <FUNCTION_APP_NAME>  --query '[].{Function:name, URL:invokeUrlTemplate}' --output table
+```azurecli
+az functionapp function list --resource-group <RESOURCE_GROUP_NAME> --name <FUNCTION_APP_NAME>  --query '[].{Function:name, URL:invokeUrlTemplate}' --output json
 ```
 
 ### Check orchestration status
 
-Check the status of the orchestration instance and activity details on the durable task scheduler dashboard. Accessing the dashboard requires you to login. Follow the instructions below to assign the required role to your identity. 
+Check the status of the orchestration instance and activity details on the durable task scheduler dashboard. Accessing the dashboard requires you to login. Follow the instructions below to assign the required role-based access control (RBAC) permission to your identity. 
 
 [!INCLUDE [assign-dev-identity-rbac-portal](./includes/assign-dev-identity-rbac-portal.md)]
 
-Finally, navigate to `https://dashboard.durabletask.io/` and click on **Add Endpoint**. Fill out the required fields to connect the task hub. 
+Finally, click **Overview** on the left menu of the task hub resource and navigate to the dashboard URL located at the top *Essentials* section. 
 
 ## Clean up resources