Update approvalStep
Namespace: microsoft.graph
Important
APIs under the /beta
version in Microsoft Graph are subject to change. Use of these APIs in production applications is not supported. To determine whether an API is available in v1.0, use the Version selector.
Apply approve or deny decision on an approvalStep object.
This API is available in the following national cloud deployments.
Global service | US Government L4 | US Government L5 (DOD) | China operated by 21Vianet |
---|---|---|---|
✅ | ✅ | ✅ | ✅ |
Permissions
The following tables show the least privileged permission or permissions required to call this API on each supported resource type. Follow best practices to request least privileged permissions. For details about delegated and application permissions, see Permission types. To learn more about these permissions, see the permissions reference.
Permissions required for calling this API for entitlement management
Permission type | Least privileged permissions | Higher privileged permissions |
---|---|---|
Delegated (work or school account) | EntitlementManagement.ReadWrite.All | Not available. |
Delegated (personal Microsoft account) | Not supported. | Not supported. |
Application | Not supported. | Not supported. |
Tip
In delegated scenarios with work or school accounts, the signed-in user must also be assigned an administrator role with supported role permissions through one of the following options:
- A user who is specified in the
specificAllowedTargets
property of the access package's policies. This is the least privileged option. - More privileged roles in the Entitlement Management system where the least privileged roles are supported for this operation:
- Access package assignment manager
- Access package manager
- Catalog owner
- More privileged Microsoft Entra roles, where the following least privileged roles are supported for this operation:
- Identity Governance Administrator
In app-only scenarios, the calling app can be assigned one of the preceding supported roles instead of the EntitlementManagement.ReadWrite.All
application permission. A user who is specified in the specificAllowedTargets
property of the access package's policies is less privileged than the EntitlementManagement.ReadWrite.All
application permission.
For more information, see Delegation and roles in entitlement management and how to delegate access governance to access package managers in entitlement management.
For PIM for Microsoft Entra roles
Permission type | Least privileged permissions | Higher privileged permissions |
---|---|---|
Delegated (work or school account) | RoleAssignmentSchedule.ReadWrite.Directory | Not available. |
Delegated (personal Microsoft account) | Not supported. | Not supported. |
Application | Not supported. | Not supported. |
Permissions required for calling this API for PIM for groups
Permission type | Least privileged permissions | Higher privileged permissions |
---|---|---|
Delegated (work or school account) | PrivilegedAssignmentSchedule.ReadWrite.AzureADGroup | Not available. |
Delegated (personal Microsoft account) | Not supported. | Not supported. |
Application | Not supported. | Not supported. |
HTTP request
To update an approval decision in entitlement management:
PATCH /identityGovernance/entitlementManagement/accessPackageAssignmentApprovals/{id}/steps/{id}
To update an approval decision in PIM for Microsoft Entra roles:
PATCH /roleManagement/directory/roleAssignmentApprovals/{id}/steps/{id}
To update an approval decision in PIM for groups:
PATCH /identityGovernance/privilegedAccess/group/assignmentApprovals/{id}/steps/{id}
Request headers
Name | Description |
---|---|
Authorization | Bearer {token}. Required. Learn more about authentication and authorization. |
Request body
The following table shows the properties that are required for this method.
Property | Type | Description |
---|---|---|
reviewResult | String | Decision of the approver. Possible values are: Approve , Deny . |
justification | String | Justification related to the approver's decision. |
Response
If successful, this method returns a 204 No Content
response code in the response body. However, if the caller doesn't have the right permissions, the method returns a 403 Forbidden
response code, or if the approval id isn't found, the method returns 404 Not found
. If the request has already been approved by another approver in the same approval stage, the method returns 409 Conflict
in the response body.
Examples
Request
The following example shows a request.
PATCH https://graph.microsoft.com/beta/identityGovernance/entitlementManagement/accessPackageAssignmentApprovals/abd306ef-f7b2-4a10-9fd1-493454322489/steps/d4fa4045-4716-436d-aec5-57b0a713f095
Response
The following example shows the response.
Note: The response object shown here might be shortened for readability.
HTTP/1.1 204 No Content
Content-Type: application/json