Skip to content

Commit e66fbad

Browse files
committedMay 23, 2022
Add Microsoft Graph section for role settings in PIM
1 parent 4a84b02 commit e66fbad

File tree

1 file changed

+46
-1
lines changed

1 file changed

+46
-1
lines changed
 

‎articles/active-directory/privileged-identity-management/pim-how-to-change-default-settings.md

Lines changed: 46 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -90,7 +90,7 @@ You can require that users enter a business justification when they activate. To
9090

9191
## Require ticket information on activation
9292

93-
If your organization uses a ticketing system to track help desk items or change requests for your enviornment, you can select the **Require ticket information on activation** box to require the elevation request to contain the name of the ticketing system (optional, if your organization uses multiple systems) and the ticket number that prompted the need for role activation.
93+
If your organization uses a ticketing system to track help desk items or change requests for your environment, you can select the **Require ticket information on activation** box to require the elevation request to contain the name of the ticketing system (optional, if your organization uses multiple systems) and the ticket number that prompted the need for role activation.
9494

9595
## Require approval to activate
9696

@@ -106,6 +106,51 @@ If setting multiple approvers, approval completes as soon as one of them approve
106106

107107
1. Select **Update** to save your changes.
108108

109+
## Manage role settings through Microsoft Graph
110+
111+
To manage settings for Azure AD roles through Microsoft Graph, use the [unifiedRoleManagementPolicy resource type and related methods](/graph/api/resources/unifiedrolemanagementpolicy).
112+
113+
In Microsoft Graph, role settings are referred to as rules and they're assigned to Azure AD roles through container policies. Each Azure AD role is assigned a specific policy object. You can retrieve all policies that are scoped to Azure AD roles and for each policy, retrieve the associated collection of rules through an `$expand` query parameter. The syntax for the request is as follows:
114+
115+
```http
116+
GET https://graph.microsoft.com/v1.0/policies/roleManagementPolicies?$filter=scopeId eq '/' and scopeType eq 'DirectoryRole'&$expand=rules
117+
```
118+
119+
Rules are grouped into containers. The containers are further broken down into rule definitions that are identified by unique IDs for easier management. For example, a **unifiedRoleManagementPolicyEnablementRule** container exposes three rule definitions identified by the following unique IDs.
120+
121+
+ `Enablement_Admin_Eligibility` - Rules that apply for admins to carry out operations on role eligibilities. For example, whether justification is required, and whether for all operations (for example, renewal, activation, or deactivation) or only for specific operations.
122+
+ `Enablement_Admin_Assignment` - Rules that apply for admins to carry out operations on role assignments. For example, whether justification is required, and whether for all operations (for example, renewal, deactivation, or extension) or only for specific operations.
123+
+ `Enablement_EndUser_Assignment` - Rules that apply for principals to enable their assignments. For example, whether multifactor authentication is required.
124+
125+
126+
To update these rule definitions, use the [update rules API](/graph/api/unifiedrolemanagementpolicyrule-update). For example, the following request specifies an empty **enabledRules** collection, therefore deactivating the enabled rules for a policy, such as multifactor authentication, ticketing information and justification.
127+
128+
```http
129+
PATCH https://graph.microsoft.com/v1.0/policies/roleManagementPolicies/DirectoryRole_cab01047-8ad9-4792-8e42-569340767f1b_70c808b5-0d35-4863-a0ba-07888e99d448/rules/Enablement_EndUser_Assignment
130+
{
131+
"@odata.type": "#microsoft.graph.unifiedRoleManagementPolicyEnablementRule",
132+
"id": "Enablement_EndUser_Assignment",
133+
"enabledRules": [],
134+
"target": {
135+
"caller": "EndUser",
136+
"operations": [
137+
"all"
138+
],
139+
"level": "Assignment",
140+
"inheritableSettings": [],
141+
"enforcedSettings": []
142+
}
143+
}
144+
```
145+
146+
You can retrieve the collection of rules that are applied to all Azure AD roles or a specific Azure AD role through the [unifiedroleManagementPolicyAssignment resource type and related methods](/graph/api/resources/unifiedrolemanagementpolicyassignment). For example, the following request uses the `$expand` query parameter to retrieve the rules that are applied to an Azure AD role identified by **roleDefinitionId** or **templateId** `62e90394-69f5-4237-9190-012177145e10`.
147+
148+
```http
149+
GET https://graph.microsoft.com/v1.0/policies/roleManagementPolicyAssignments?$filter=scopeId eq '/' and scopeType eq 'DirectoryRole' and roleDefinitionId eq '62e90394-69f5-4237-9190-012177145e10'&$expand=policy($expand=rules)
150+
```
151+
152+
For more information about managing role settings through PIM, see [Role settings and PIM](/graph/api/resources/privilegedidentitymanagementv3-overview#role-settings-and-pim).
153+
109154
## Next steps
110155

111156
- [Assign Azure AD roles in Privileged Identity Management](pim-how-to-add-role-to-user.md)

0 commit comments

Comments
 (0)