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/batch/batch-aad-auth.md
+62-1Lines changed: 62 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ ms.service: batch
13
13
ms.topic: article
14
14
ms.tgt_pltfrm:
15
15
ms.workload: big-compute
16
-
ms.date: 08/15/2019
16
+
ms.date: 01/28/2020
17
17
ms.author: jushiman
18
18
---
19
19
@@ -140,6 +140,67 @@ Your application should now appear in your access control settings with an RBAC
140
140
141
141

142
142
143
+
### Assign a custom role
144
+
145
+
A custom role grants granular permission to a user for submitting jobs, tasks, and more. This provides the ability to prevent users from performing operations that affect cost, such as creating pools or modifying nodes.
146
+
147
+
You can use a custom role to grant permissions to an Azure AD user, group, or service principal for the following RBAC operations:
- Microsoft.Batch/batchAccounts/read (for any read operation)
162
+
- Microsoft.Batch/batchAccounts/listKeys/action (for any operation)
163
+
164
+
Custom roles are for users authenticated by Azure AD, not the Batch account credentials (shared key). Note that the Batch account credentials give full permission to the Batch account. Also note that jobs using autopool require pool-level permissions.
165
+
166
+
Here's an example of a custom role definition:
167
+
168
+
```json
169
+
{
170
+
"properties":{
171
+
"roleName":"Azure Batch Custom Job Submitter",
172
+
"type":"CustomRole",
173
+
"description":"Allows a user to submit jobs to Azure Batch but not manage pools",
0 commit comments