Merge pull request #299376 from hhunter-ms/copyedit

Copyedit for all DTS docs

Author: v-ccolin

articles/azure-functions/durable/TOC.yml

@@ -116,6 +116,8 @@
     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 

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

@@ -1,17 +1,107 @@
 ---
-title: Debug and manage orchestrations using the Azure Functions durable task scheduler dashboard (preview)
-description: Learn how to debug and manage your orchestrations using the Azure Functions durable task scheduler.
-ms.topic: conceptual
-ms.date: 03/17/2025
+title: Debug and manage orchestrations using the Azure Functions Durable Task Scheduler dashboard (preview)
+description: Learn how to debug and manage your orchestrations using the Azure Functions Durable Task Scheduler.
+ms.topic: how-to
+ms.date: 05/05/2025
+zone_pivot_groups: dts-devexp
 ---
 
-# Debug and manage orchestrations using the Azure Functions durable task scheduler dashboard (preview)
+# Debug and manage orchestrations using the Azure Functions Durable Task Scheduler dashboard (preview)
 
-Observe, manage, and debug your task hub or scheduler's orchestrations 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/` combined with your task hub endpoint.  
+Observe, manage, and debug your task hub or scheduler's orchestrations 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 the emulator locally doesn't require authentication. 
+
+Creating a scheduler resource on Azure requires [assigning the *Durable Task Data Contributor* role to your identity](./durable-task-scheduler-identity.md). 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/` combined with your task hub endpoint.  
+
+In this article, you learn how to:
+
+> [!div class="checklist"]
+>
+> - Assign one of the Durable Task roles to your developer identity. 
+> - Access the Durable Task Scheduler dashboard.
+> - View orchestration status and history via the Durable Task Scheduler dashboard.
+
+## Prerequisites
+
+Before you begin:
+
+- [Install the latest Azure CLI](/cli/azure/install-azure-cli) 
+- [Create a scheduler and task hub resource](./develop-with-durable-task-scheduler.md)
+- [Configure managed identity for your Durable Task Scheduler resource](./durable-task-scheduler-identity.md)
+
+## Access the Durable Task Scheduler dashboard
+
+Assign the required role to your *developer identity (email)* to gain access to the [Durable Task Scheduler dashboard](./durable-task-scheduler-dashboard.md). 
+
+::: zone pivot="az-cli" 
+
+1. Set the assignee to your developer identity.
+
+    ```azurecli
+    assignee=$(az ad user show --id "[email protected]" --query "id" --output tsv)
+    ```
+
+1. Set the scope. Granting access on the scheduler scope gives access to *all* task hubs in that scheduler.
+
+    **Task Hub**
+
+    ```bash
+    scope="/subscriptions/SUBSCRIPTION_ID/resourceGroups/RESOURCE_GROUP/providers/Microsoft.DurableTask/schedulers/SCHEDULER_NAME/taskHubs/TASK_HUB_NAME"
+    ```
+   
+    **Scheduler**
+    ```bash
+    scope="/subscriptions/SUBSCRIPTION_ID/resourceGroups/RESOURCE_GROUP/providers/Microsoft.DurableTask/schedulers/SCHEDULER_NAME"
+    ```
+
+1. Grant access. Run the following command to create the role assignment and grant access.
+
+    ```azurecli
+    az role assignment create \
+      --assignee "$assignee" \
+      --role "Durable Task Data Contributor" \
+      --scope "$scope"
+    ```
+   
+    *Expected output*
+   
+    The following output example shows a developer identity assigned with the Durable Task Data Contributor role on the *scheduler* level:
+   
+    ```json
+    {
+      "condition": null,
+      "conditionVersion": null,
+      "createdBy": "YOUR_DEVELOPER_CREDENTIAL_ID",
+      "createdOn": "2024-12-20T01:36:45.022356+00:00",
+      "delegatedManagedIdentityResourceId": null,
+      "description": null,
+      "id": "/subscriptions/YOUR_SUBSCRIPTION_ID/resourceGroups/YOUR_RESOURCE_GROUP/providers/Microsoft.DurableTask/schedulers/YOUR_DTS_NAME/providers/Microsoft.Authorization/roleAssignments/ROLE_ASSIGNMENT_ID",
+      "name": "ROLE_ASSIGNMENT_ID",
+      "principalId": "YOUR_DEVELOPER_CREDENTIAL_ID",
+      "principalName": "YOUR_EMAIL",
+      "principalType": "User",
+      "resourceGroup": "YOUR_RESOURCE_GROUP",
+      "roleDefinitionId": "/subscriptions/YOUR_SUBSCRIPTION/providers/Microsoft.Authorization/roleDefinitions/ROLE_DEFINITION_ID",
+      "roleDefinitionName": "Durable Task Data Contributor",
+      "scope": "/subscriptions/YOUR_SUBSCRIPTION/resourceGroups/YOUR_RESOURCE_GROUP/providers/Microsoft.DurableTask/schedulers/YOUR_DTS_NAME",
+      "type": "Microsoft.Authorization/roleAssignments",
+      "updatedBy": "YOUR_DEVELOPER_CREDENTIAL_ID",
+      "updatedOn": "2024-12-20T01:36:45.022356+00:00"
+    }
+    ```
+
+1. After granting access, go to `https://dashboard.durabletask.io/` and fill out the required information about your scheduler and task hub to see the dashboard. 
+ 
+::: zone-end 
+
+::: zone pivot="az-portal" 
+
+[!INCLUDE [assign-dev-identity-role-based-access-control-portal](./includes/assign-dev-identity-role-based-access-control-portal.md)]
+
+::: zone-end 
 
 ## Monitor orchestration progress and execution history
 
@@ -51,10 +141,12 @@ The dashboard includes features for managing orchestrations on demand, such as s
 
 :::image type="content" source="media/durable-task-scheduler-dashboard/manage-orchestration.png" alt-text="Screenshot of the dashboard showing the buttons you use to manage the orchestration.":::
 
-## Security 
-
-Dashboard access is secured through [integration with Azure Role-Based Access Control (RBAC)](./develop-with-durable-task-scheduler.md#accessing-durable-task-scheduler-dashboard).
-
 ## Next steps
 
-[Try out the quickstart to see the durable task scheduler dashboard in action](./quickstart-durable-task-scheduler.md)
+For Durable Task Scheduler for Durable Functions:
+- [Quickstart: Configure a Durable Functions app to use the Durable Task Scheduler](./quickstart-durable-task-scheduler.md)
+- [Create Durable Task Scheduler resources and view them in the dashboard](./develop-with-durable-task-scheduler.md)
+
+For Durable Task Scheduler for the Durable Task SDKs:
+- [Quickstart: Create an app with Durable Task SDKs and Durable Task Scheduler](./quickstart-portable-durable-task-sdks.md)
+- [Quickstart: Configure Durable Task SDKs in your container app](./quickstart-container-apps-durable-task-sdk.md)

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

@@ -1,23 +1,23 @@
 ---
-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.
+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/17/2025
 ---
 
-# Use the Dedicated SKU for Azure Functions durable task scheduler (preview)
+# Use the Dedicated SKU for Azure Functions Durable Task Scheduler (preview)
 
-Durable task scheduler currently offers the Dedicated SKU only. In this article, you'll learn:
+Durable Task Scheduler currently offers the Dedicated SKU only. In this article, you'll learn:
 - What the Dedicated SKU provides
 - How you're billed
 - Relevant concepts such as *capacity unit* and *work item*
 
 ## Dedicated SKU concepts 
 
-You're billed based on the number of "Capacity Units (CUs)" purchased. In the durable task scheduler context:
+You're billed based on the number of "Capacity Units (CUs)" purchased. In the Durable Task Scheduler context:
 
 - **A Capacity Unit (CU)** is a measure of the resources allocated to your scheduler resource. Each CU represents a preallocated amount of CPU, memory, and storage resources. A single CU guarantees the dispatch of a number of *work items* and provides a defined amount of storage. If extra performance and/or storage is needed, more CUs can be purchased.
-- **Work item** is a message dispatched by the durable task scheduler to an application, triggering the execution of orchestrator, activity, or entity functions. The number of work items that can be dispatched per second is determined by the CUs allocated to the scheduler.
+- **Work item** is a message dispatched by the Durable Task Scheduler to an application, triggering the execution of orchestrator, activity, or entity functions. The number of work items that can be dispatched per second is determined by the CUs allocated to the scheduler.
 
 The following table explains the minimum cost and features provided with each CU.
 
@@ -32,14 +32,14 @@ Find the price of a capacity unit in a given region on the [Azure Functions pric
 ## Determine the number of Capacity Units needed
 
 > [!NOTE]
-> Durable task scheduler supports purchasing only **one capacity unit** at the moment.  
+> Durable Task Scheduler supports purchasing only **one capacity unit** at the moment.  
 
 To determine whether one unit is sufficient for your workload, follow these steps:
 
 1. **Understand how to identify the number of work items per orchestration**
    - Starting an orchestration consumes a single work item.
    - Each schedule of an activity run consumes another work item.
-   - Each response sent back to the durable task scheduler consumes another work item.
+   - Each response sent back to the Durable Task Scheduler consumes another work item.
 
 1. **Estimate monthly orchestrations**  
     Calculate the total number of orchestrations you need to run per month. 
@@ -57,4 +57,4 @@ For example, if you run 100 million orchestrations per month and each orchestrat
 
 ## Next steps
 
-Try out the [durable functions quickstart sample](quickstart-durable-task-scheduler.md).
+Try out the [Durable Functions quickstart sample](quickstart-durable-task-scheduler.md).