Skip to content

Commit a618994

Browse files
authored
Merge pull request #115672 from shashishailaj/patch-91
(Azure CXP) Add technical note.
2 parents 8a05a7e + 7d23951 commit a618994

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

articles/active-directory/users-groups-roles/roles-create-custom.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -135,6 +135,9 @@ $roleAssignment = New-AzureADMSRoleAssignment -ResourceScope $resourceScope -Rol
135135
}
136136
```
137137
138+
> [!Note]
139+
> The "templateId": "GUID" is an optional parameter being sent in the body depending on requirement. If you have a requirement for creating multiple different custom role with common parameters , it is best to create a template and define a templateId . You can generate a templateId beforehand using the powershell cmdlet (New-Guid).Guid .
140+
138141
1. Create the role assignment.
139142
140143
HTTP request to create a custom role definition.
@@ -155,6 +158,7 @@ $roleAssignment = New-AzureADMSRoleAssignment -ResourceScope $resourceScope -Rol
155158
}
156159
```
157160
161+
158162
## Assign a custom role scoped to a resource
159163
160164
Like built-in roles, custom roles are assigned by default at the default organization-wide scope to grant access permissions over all app registrations in your organization. But unlike built-in roles, custom roles can also be assigned at the scope of a single Azure AD resource. This allows you to give the user the permission to update credentials and basic properties of a single app without having to create a second custom role.

0 commit comments

Comments
 (0)