Skip to content

Commit 4f028a9

Browse files
committed
next steps
Signed-off-by: Hannah Hunter <[email protected]>
1 parent 7626247 commit 4f028a9

File tree

2 files changed

+18
-80
lines changed

2 files changed

+18
-80
lines changed

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

Lines changed: 11 additions & 79 deletions
Original file line numberDiff line numberDiff line change
@@ -46,24 +46,24 @@ Learn more about Durable Task Scheduler [features](./durable-task-scheduler.md#f
4646
4747
::: zone-end
4848
49-
## Run Durable Task emulator
49+
## Run the Durable Task emulator
5050
5151
1. Pull the docker image containing the emulator.
5252
5353
```bash
54-
docker pull mcr.microsoft.com/dts/dts-emulator:v0.0.5
54+
docker pull mcr.microsoft.com/dts/dts-emulator:v0.0.6
5555
```
5656

5757
1. Run the emulator.
5858

5959
```bash
60-
docker run -itP mcr.microsoft.com/dts/dts-emulator:v0.0.5
60+
docker run -itP mcr.microsoft.com/dts/dts-emulator:v0.0.6
6161
```
6262

6363
This command 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 in the following command:
6464

6565
```bash
66-
docker run -itP -e DTS_TASK_HUB_NAMES=taskhub1,taskhub2,taskhub3 mcr.microsoft.com/dts/dts-emulator:v0.0.5
66+
docker run -itP -e DTS_TASK_HUB_NAMES=taskhub1,taskhub2,taskhub3 mcr.microsoft.com/dts/dts-emulator:v0.0.6
6767
```
6868

6969
## Create a scheduler and task hub
@@ -109,10 +109,10 @@ Learn more about Durable Task Scheduler [features](./durable-task-scheduler.md#f
109109
"resourceGroup": "YOUR_RESOURCE_GROUP",
110110
"systemData": {
111111
"createdAt": "2025-01-06T21:22:59Z",
112-
"createdBy": "YOUR_EMAIL@microsoft.com",
112+
"createdBy": "YOUR_EMAIL@example.com",
113113
"createdByType": "User",
114114
"lastModifiedAt": "2025-01-06T21:22:59Z",
115-
"lastModifiedBy": "YOUR_EMAIL@microsoft.com",
115+
"lastModifiedBy": "YOUR_EMAIL@example.com",
116116
"lastModifiedByType": "User"
117117
},
118118
"tags": {}
@@ -266,80 +266,13 @@ Durable Task Scheduler **only** supports either *user-assigned* or *system-assig
266266
267267
If you haven't already, [configure managed identity for your Durable Functions app](./durable-task-scheduler-identity.md).
268268

269-
## Accessing the Durable Task Scheduler dashboard
269+
## Access the Durable Task Scheduler dashboard
270270

271-
Assign the required role to your *developer identity (email)* to gain access to the [Durable Task Scheduler dashboard](./durable-task-scheduler-dashboard.md).
272-
273-
::: zone pivot="az-cli"
274-
275-
1. Set the assignee to your developer identity.
276-
277-
```azurecli
278-
assignee=$(az ad user show --id "[email protected]" --query "id" --output tsv)
279-
```
280-
281-
1. Set the scope. Granting access on the scheduler scope gives access to *all* task hubs in that scheduler.
282-
283-
**Task Hub**
284-
285-
```bash
286-
scope="/subscriptions/SUBSCRIPTION_ID/resourceGroups/RESOURCE_GROUP/providers/Microsoft.DurableTask/schedulers/SCHEDULER_NAME/taskHubs/TASK_HUB_NAME"
287-
```
288-
289-
**Scheduler**
290-
```bash
291-
scope="/subscriptions/SUBSCRIPTION_ID/resourceGroups/RESOURCE_GROUP/providers/Microsoft.DurableTask/schedulers/SCHEDULER_NAME"
292-
```
293-
294-
1. Grant access. Run the following command to create the role assignment and grant access.
295-
296-
```azurecli
297-
az role assignment create \
298-
--assignee "$assignee" \
299-
--role "Durable Task Data Contributor" \
300-
--scope "$scope"
301-
```
302-
303-
*Expected output*
304-
305-
The following output example shows a developer identity assigned with the Durable Task Data Contributor role on the *scheduler* level:
306-
307-
```json
308-
{
309-
"condition": null,
310-
"conditionVersion": null,
311-
"createdBy": "YOUR_DEVELOPER_CREDENTIAL_ID",
312-
"createdOn": "2024-12-20T01:36:45.022356+00:00",
313-
"delegatedManagedIdentityResourceId": null,
314-
"description": null,
315-
"id": "/subscriptions/YOUR_SUBSCRIPTION_ID/resourceGroups/YOUR_RESOURCE_GROUP/providers/Microsoft.DurableTask/schedulers/YOUR_DTS_NAME/providers/Microsoft.Authorization/roleAssignments/ROLE_ASSIGNMENT_ID",
316-
"name": "ROLE_ASSIGNMENT_ID",
317-
"principalId": "YOUR_DEVELOPER_CREDENTIAL_ID",
318-
"principalName": "YOUR_EMAIL",
319-
"principalType": "User",
320-
"resourceGroup": "YOUR_RESOURCE_GROUP",
321-
"roleDefinitionId": "/subscriptions/YOUR_SUBSCRIPTION/providers/Microsoft.Authorization/roleDefinitions/ROLE_DEFINITION_ID",
322-
"roleDefinitionName": "Durable Task Data Contributor",
323-
"scope": "/subscriptions/YOUR_SUBSCRIPTION/resourceGroups/YOUR_RESOURCE_GROUP/providers/Microsoft.DurableTask/schedulers/YOUR_DTS_NAME",
324-
"type": "Microsoft.Authorization/roleAssignments",
325-
"updatedBy": "YOUR_DEVELOPER_CREDENTIAL_ID",
326-
"updatedOn": "2024-12-20T01:36:45.022356+00:00"
327-
}
328-
```
329-
330-
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.
331-
332-
::: zone-end
333-
334-
::: zone pivot="az-portal"
335-
336-
[!INCLUDE [assign-dev-identity-role-based-access-control-portal](./includes/assign-dev-identity-role-based-access-control-portal.md)]
337-
338-
::: zone-end
271+
[Assign the required role to your *developer identity (email)*](./durable-task-scheduler-dashboard.md#access-the-durable-task-scheduler-dashboard) to gain access to the Durable Task Scheduler dashboard.
339272

340273
## Auto scaling in Functions Premium plan
341274

342-
For Durable Task Scheduler apps on the Functions Premium plan, enable the *Runtime Scale Monitoring* setting to get auto scaling of the app.
275+
For Durable Functions apps on the Functions Premium plan, you can enable autoscaling using the *Runtime Scale Monitoring* setting.
343276

344277
::: zone pivot="az-portal"
345278

@@ -353,8 +286,6 @@ For Durable Task Scheduler apps on the Functions Premium plan, enable the *Runti
353286

354287
::: zone pivot="az-cli"
355288

356-
Run the following command:
357-
358289
```azurecli
359290
az resource update -g <resource_group> -n <function_app_name>/config/web --set properties.functionsRuntimeScaleMonitoringEnabled=1 --resource-type Microsoft.Web/sites
360291
```
@@ -363,4 +294,5 @@ az resource update -g <resource_group> -n <function_app_name>/config/web --set p
363294

364295
## Next steps
365296

366-
Try out the [Durable Functions quickstart sample](quickstart-durable-task-scheduler.md).
297+
> [!div class="nextstepaction"]
298+
> [Run and deploy your Durable Functions app using the Durable Task Scheduler](./quickstart-durable-task-scheduler.md)

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

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -143,4 +143,10 @@ The dashboard includes features for managing orchestrations on demand, such as s
143143
144144
## Next steps
145145
146-
[Try out the quickstart to see the Durable Task Scheduler dashboard in action](./quickstart-durable-task-scheduler.md)
146+
For Durable Task Scheduler for Durable Functions:
147+
- [Quickstart: Configure a Durable Functions app to use the Durable Task Scheduler](./quickstart-durable-task-scheduler.md)
148+
- [Create Durable Task Scheduler resources and view them in the dashboard](./develop-with-durable-task-scheduler.md)
149+
150+
For Durable Task Scheduler for the Durable Task SDKs:
151+
- [Quickstart: Create an app with Durable Task SDKs and Durable Task Scheduler](./quickstart-portable-durable-task-sdks.md)
152+
- [Quickstart: Configure Durable Task SDKs in your container app](./quickstart-container-apps-durable-task-sdk.md)

0 commit comments

Comments
 (0)