You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-functions/durable/durable-task-scheduler/develop-with-durable-task-scheduler.md
+20-11Lines changed: 20 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -62,11 +62,11 @@ Learn more about durable task scheduler [features](./durable-task-scheduler.md#f
62
62
docker run -itP mcr.microsoft.com/dts/dts-emulator:v0.0.5
63
63
```
64
64
65
-
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:
65
+
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:
66
66
67
-
```bash
68
-
docker run -itP -e DTS_TASK_HUB_NAMES=taskhub1,taskhub2,taskhub3 mcr.microsoft.com/dts/dts-emulator:v0.0.5
69
-
```
67
+
```bash
68
+
docker run -itP -e DTS_TASK_HUB_NAMES=taskhub1,taskhub2,taskhub3 mcr.microsoft.com/dts/dts-emulator:v0.0.5
69
+
```
70
70
71
71
## Create a scheduler and task hub
72
72
@@ -154,8 +154,8 @@ docker run -itP -e DTS_TASK_HUB_NAMES=taskhub1,taskhub2,taskhub3 mcr.microsoft.c
154
154
::: zone pivot="az-portal"
155
155
156
156
You can create a scheduler and task hub on Azure portal via two ways:
157
-
- **Function app integrated creation:** *(recommended)* automatically creates the managed identity resource and RBAC assignment needed for your app to access durable task scheduler.
158
-
- **Top-level creation:** Requires you to [manually assign RBAC](#configure-identity-based-authentication-for-app-to-access-dts) to configure scheduler access for your app.
157
+
- **Function app integrated creation:***(recommended)* automatically creates the managed identity resource and RBAC assignment, plus configures required environment variablesfor your app to access durable task scheduler.
158
+
- **Top-level creation:** Requires you to [manually assign RBAC permission](#configure-identity-based-authentication-for-app-to-access-dts) to configure scheduler access for your app.
159
159
160
160
> [!NOTE]
161
161
> 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.
@@ -216,11 +216,11 @@ You can see the list of scheduler resources created in all subscriptions you hav
216
216
217
217
::: zone pivot="az-cli"
218
218
219
-
Retrieve a list of task hubs in a specific scheduler by running:
219
+
Retrieve a list of task hubs in a specific scheduler by running:
220
220
221
-
```azurecli
222
-
az durabletask taskhub list --resource-group <RESOURCE_GROUP_NAME> --scheduler-name <SCHEDULER_NAME>
223
-
```
221
+
```azurecli
222
+
az durabletask taskhub list --resource-group <RESOURCE_GROUP_NAME> --scheduler-name <SCHEDULER_NAME>
223
+
```
224
224
225
225
::: zone-end
226
226
@@ -266,7 +266,16 @@ You can see all the task hubs created in a scheduler on the **Overview** of the
266
266
267
267
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.
268
268
269
-
The following sections demonstrate how to configure identity resources for your durable functions app to access a scheduler and its task hubs.
269
+
The following are the durable task scheduler related roles you can grant to an identity:
270
+
271
+
- **Durable Task Data Contributor**: Role for all data access operations. This role is a superset of all other roles.
272
+
- **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.
273
+
- **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.
274
+
275
+
> [!NOTE]
276
+
> Most durable functions apps would require the Durable Task Data Contributor role.
277
+
278
+
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.
270
279
271
280
### Assign RBAC (role-based access control) to managed identity resource
0 commit comments