Skip to content

Latest commit

 

History

History
157 lines (109 loc) · 5.73 KB

File metadata and controls

157 lines (109 loc) · 5.73 KB
title Update approvalStep
description Apply approve or deny decision on an approvalStep object.
ms.localizationpriority medium
author markwahl-msft
ms.subservice entra-id-governance
doc_type apiPageType
ms.date 04/04/2024

Update approvalStep

Namespace: microsoft.graph

[!INCLUDE beta-disclaimer]

Apply approve or deny decision on an approvalStep object.

[!INCLUDE national-cloud-support]

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

[!INCLUDE permissions-table]

[!INCLUDE rbac-entitlement-end-user-apis-write]

For PIM for Microsoft Entra roles

[!INCLUDE permissions-table]

Permissions required for calling this API for PIM for Groups

[!INCLUDE permissions-table]

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. The 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

[!INCLUDE sample-code] [!INCLUDE sdk-documentation]

[!INCLUDE sample-code] [!INCLUDE sdk-documentation]

[!INCLUDE sample-code] [!INCLUDE sdk-documentation]

[!INCLUDE sample-code] [!INCLUDE sdk-documentation]

[!INCLUDE sample-code] [!INCLUDE sdk-documentation]

[!INCLUDE sample-code] [!INCLUDE sdk-documentation]


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