Skip to content

Latest commit

 

History

History
278 lines (194 loc) · 9.8 KB

File metadata and controls

278 lines (194 loc) · 9.8 KB
title Delete unifiedRoleAssignmentMultiple
description Delete a unifiedRoleAssignmentMultiple object.
ms.localizationpriority medium
author DougKirschner
ms.reviewer msodsrbac
ms.subservice entra-directory-management
doc_type apiPageType
ms.date 04/05/2024

Delete unifiedRoleAssignmentMultiple

Namespace: microsoft.graph

[!INCLUDE beta-disclaimer]

Delete a unifiedRoleAssignmentMultiple object of an RBAC provider.

This is applicable for a RBAC application that supports multiple principals and scopes. The following RBAC providers are currently supported:

  • Cloud PC
  • device management (Intune)
  • Defender (Microsoft Defender XDR Unified RBAC)

[!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.

For Cloud PC provider

[!INCLUDE permissions-table]

For Device management (Intune) provider

[!INCLUDE permissions-table]

For Defender provider

[!INCLUDE permissions-table]

HTTP request

To delete a unifiedRoleAssignmentMultiple for a Cloud PC provider:

DELETE /roleManagement/cloudPC/roleAssignments/{id}

To delete a unifiedRoleAssignmentMultiple for an Intune provider:

DELETE /roleManagement/deviceManagement/roleAssignments/{id}

To delete a unifiedRoleAssignmentMultiple for a Defender provider:

DELETE /roleManagement/defender/roleAssignments/{id}

Request headers

Name Description
Authorization Bearer {token}. Required. Learn more about authentication and authorization.

Request body

Don't supply a request body for this method.

Response

If successful, this method returns a 204 No Content response code. It doesn't return anything in the response body.

Example

Example 1: Delete a unifiedRoleAssignmentMultiple in an Intune provider

The following example shows how to delete a unifiedRoleAssignmentMultiple in an Intune provider.

Request

The following example shows a request.

DELETE https://graph.microsoft.com/beta/roleManagement/deviceManagement/roleAssignments/lAPpYvVpN0KRkAEhdxReEJC2sEqbR_9Hr48lds9SGHI-1

[!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]

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


Response

The following example shows the response.

HTTP/1.1 204 No Content

Example 2: Delete a unifiedRoleAssignmentMultiple in a Cloud PC provider

The following example shows how to delete a unifiedRoleAssignmentMultiple in a Cloud PC provider.

Request

The following example shows a request.

DELETE https://graph.microsoft.com/beta/roleManagement/cloudPC/roleAssignments/{id}

[!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]

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


Response

The following example shows the response.

HTTP/1.1 204 No Content

Example 3: Delete a unifiedRoleAssignmentMultiple in a Defender provider

The following example shows how to delete a unifiedRoleAssignmentMultiple in a Defender provider.

Request

The following example shows a request.

DELETE https://graph.microsoft.com/beta/roleManagement/defender/roleAssignments/{id}

[!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 snippet-not-available] [!INCLUDE sdk-documentation]

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


Response

The following example shows the response.

HTTP/1.1 204 No Content