You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
title: "List inherited app role assignments for an agent identity"
3
+
description: "Retrieve the application role assignments (appRoleAssignment objects) that an agent identity inherits from its parent agent identity blueprint principal."
4
+
author: "mvoznyarskiy"
5
+
ms.date: 04/13/2026
6
+
ms.localizationpriority: medium
7
+
ms.subservice: "entra-agent-id"
8
+
doc_type: apiPageType
9
+
---
10
+
11
+
# List inherited app role assignments for an agent identity
Retrieve the application role assignments ([appRoleAssignment](../resources/approleassignment.md) objects) that an [agent identity](../resources/agentidentity.md) inherits from its parent agent identity blueprint principal. These inherited assignments represent the effective application-level permissions applied at token issuance time.
18
+
19
+
The inherited collection is strictly read-only. POST, PATCH, and DELETE requests return `405 Method Not Allowed`. To modify the permissions that agent identities inherit, update the parent agent identity blueprint principal's `appRoleAssignments` instead.
20
+
21
+
Pagination is not supported. All results are returned in a single response. `$top`, `$skip`, and `$skiptoken` are not supported.
22
+
23
+
Calling this endpoint on a service principal that is not an agent identity returns `404 Not Found`.
24
+
25
+
## Permissions
26
+
27
+
Choose the permission or permissions marked as least privileged for this API. Use a higher privileged permission or permissions [only if your app requires it](/graph/permissions-overview#best-practices-for-using-microsoft-graph-permissions). For details about delegated and application permissions, see [Permission types](/graph/permissions-overview#permission-types). To learn more about these permissions, see the [permissions reference](/graph/permissions-reference).
GET /servicePrincipals/microsoft.graph.agentIdentity/{agentIdentity-id}/inheritedAppRoleAssignments
46
+
```
47
+
48
+
## Optional query parameters
49
+
50
+
This method does not support OData query parameters.
51
+
52
+
## Request headers
53
+
54
+
|Name|Description|
55
+
|:---|:---|
56
+
|Authorization|Bearer {token}. Required. Learn more about [authentication and authorization](/graph/auth/auth-concepts).|
57
+
58
+
## Request body
59
+
60
+
Don't supply a request body for this method.
61
+
62
+
## Response
63
+
64
+
If successful, this method returns a `200 OK` response code and a collection of [appRoleAssignment](../resources/approleassignment.md) objects in the response body.
65
+
66
+
## Examples
67
+
68
+
### Request
69
+
70
+
The following example shows a request.
71
+
<!-- {
72
+
"blockType": "request",
73
+
"name": "list_inheritedapproleassignment"
74
+
}
75
+
-->
76
+
```http
77
+
GET https://graph.microsoft.com/beta/servicePrincipals/microsoft.graph.agentIdentity/b3f37624-8113-471c-9de3-0234828e3ca2/inheritedAppRoleAssignments
78
+
```
79
+
80
+
81
+
### Response
82
+
83
+
The following example shows the response.
84
+
>**Note:** The response object shown here might be shortened for readability.
title: "List inherited OAuth2 permission grants for an agent identity"
3
+
description: "Retrieve the delegated permission grants (oAuth2PermissionGrant objects) that an agent identity inherits from its parent agent identity blueprint principal."
4
+
author: "mvoznyarskiy"
5
+
ms.date: 04/13/2026
6
+
ms.localizationpriority: medium
7
+
ms.subservice: "entra-agent-id"
8
+
doc_type: apiPageType
9
+
---
10
+
11
+
# List inherited OAuth2 permission grants for an agent identity
Retrieve the delegated permission grants ([oAuth2PermissionGrant](../resources/oauth2permissiongrant.md) objects) that an [agent identity](../resources/agentidentity.md) inherits from its parent agent identity blueprint principal. These inherited grants represent the effective delegated permissions applied at token issuance time.
18
+
19
+
This endpoint returns only inherited grants where `consentType` is `AllPrincipals` (admin-consented, tenant-wide grants). Grants where `consentType` is `Principal` (user-specific grants) are not returned by this endpoint.
20
+
21
+
The inherited collection is strictly read-only. POST, PATCH, and DELETE requests return `405 Method Not Allowed`. To modify the permissions that agent identities inherit, update the parent agent identity blueprint principal's `oauth2PermissionGrants` instead.
22
+
23
+
Pagination is not supported. All results are returned in a single response. `$top`, `$skip`, and `$skiptoken` are not supported.
24
+
25
+
Calling this endpoint on a service principal that is not an agent identity returns `404 Not Found`.
26
+
27
+
## Permissions
28
+
29
+
Choose the permission or permissions marked as least privileged for this API. Use a higher privileged permission or permissions [only if your app requires it](/graph/permissions-overview#best-practices-for-using-microsoft-graph-permissions). For details about delegated and application permissions, see [Permission types](/graph/permissions-overview#permission-types). To learn more about these permissions, see the [permissions reference](/graph/permissions-reference).
GET /servicePrincipals/microsoft.graph.agentIdentity/{agentIdentity-id}/inheritedOauth2PermissionGrants
48
+
```
49
+
50
+
## Optional query parameters
51
+
52
+
This method does not support OData query parameters.
53
+
54
+
## Request headers
55
+
56
+
|Name|Description|
57
+
|:---|:---|
58
+
|Authorization|Bearer {token}. Required. Learn more about [authentication and authorization](/graph/auth/auth-concepts).|
59
+
60
+
## Request body
61
+
62
+
Don't supply a request body for this method.
63
+
64
+
## Response
65
+
66
+
If successful, this method returns a `200 OK` response code and a collection of [oAuth2PermissionGrant](../resources/oauth2permissiongrant.md) objects in the response body.
67
+
68
+
## Examples
69
+
70
+
### Request
71
+
72
+
The following example shows a request.
73
+
<!-- {
74
+
"blockType": "request",
75
+
"name": "list_inheritedoauth2permissiongrant"
76
+
}
77
+
-->
78
+
```http
79
+
GET https://graph.microsoft.com/beta/servicePrincipals/microsoft.graph.agentIdentity/b3f37624-8113-471c-9de3-0234828e3ca2/inheritedOauth2PermissionGrants
80
+
```
81
+
82
+
83
+
### Response
84
+
85
+
The following example shows the response.
86
+
>**Note:** The response object shown here might be shortened for readability.
Copy file name to clipboardExpand all lines: api-reference/beta/api/driveitem-post-permissions.md
+74-5Lines changed: 74 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ Create a new [permission](../resources/permission.md) object on a [driveItem](..
19
19
> [!IMPORTANT]
20
20
> This API has the following restrictions:
21
21
>
22
-
> - For OneDrive for work or school and SharePoint Online, you can only use this method to create a new application permission. If you want to create a new user permission in a **driveItem**, see [invite](./driveitem-invite.md). For more information on application permissions, see [Overview of Selected permissions in OneDrive and SharePoint](/graph/permissions-selected-overview).
22
+
> - For OneDrive for work or school and SharePoint Online, you can only use this method to create a new application permission. If you want to create a new user permission in a **driveItem**, see [invite](./driveitem-invite.md). For more information on application permissions, see [Overview of selected permissions in OneDrive and SharePoint](/graph/permissions-selected-overview).
23
23
> - For SharePoint Embedded, you can only use this method to create a new [sharePointGroup](../resources/sharepointgroup.md) permission with app-only access. You can't create a permission on the root item of a container.
@@ -57,8 +57,8 @@ In the request body, supply a JSON representation of the [permission](../resourc
57
57
58
58
> [!IMPORTANT]
59
59
>
60
-
> - This API only accepts `grantedToV2` as input for the **permission** object. Other properties such as `grantedToIdentitiesV2` or the deprecated `grantedTo` and `grantedToIdentities` are not accepted.
61
-
> - For SharePoint Embedded, when creating a new [sharePointGroup](../resources/sharepointgroup.md) permission, the request body must include both the `id` and `displayName` of the **sharePointGroup** referenced in the `grantedToV2.siteGroup` property. See [Example 2](#example-2-add-a-sharepoint-group-permission-to-a-driveitem-in-a-sharepoint-embedded-container).
60
+
> - This API only accepts **grantedToV2** as input for the **permission** object. Other properties such as **grantedToIdentitiesV2** or the deprecated **grantedTo** and **grantedToIdentities** aren't accepted.
61
+
> - For SharePoint Embedded, when you create a new [sharePointGroup](../resources/sharepointgroup.md) permission, we recommend that you reference the **sharePointGroup** using the **grantedToV2.sharePointGroup.id** property in the request body. This **id** should map to the **id** of the **sharePointGroup** property. For more information, see [Example 2](#example-2-add-a-sharepoint-group-permission-to-a-driveitem-in-a-sharepoint-embedded-container-using-its-id). We don't recommend that you reference a **sharePointGroup** using its **principalId** because the **principalId** is only unique within the site, unlike the **id** of the **sharePointGroup**, which is globally unique. In that case, the request body must include both **id** and **displayName** in the **grantedToV2.siteGroup** property. The **id** must point to the **principalId** of the **sharePointGroup** and the **displayName** must point to the **title** of the **sharePointGroup**. For more information, see [Example 3](#example-3-add-a-sharepoint-group-permission-to-a-driveitem-in-a-sharepoint-embedded-container-using-the-principalid).
### Example 2: Add a SharePoint group permission to a driveItem in a SharePoint Embedded container
162
+
### Example 2: Add a SharePoint group permission to a driveItem in a SharePoint Embedded container using its ID
163
163
164
-
The following example shows how to add a `write`[permission](../resources/permission.md) for the `Internal Collaborators`[sharePointGroup](../resources/sharepointgroup.md) on a [driveItem](../resources/driveitem.md) identified by `01V4EPHZNV2OJQJNBPWNCKDTXCQ5TSVBJU` in a SharePoint Embedded [fileStorageContainer](../resources/filestoragecontainer.md) identified by `b!s8RqPCGh0ESQS2EYnKM0IKS3lM7GxjdAviiob7oc5pXv_0LiL-62Qq3IXyrXnEop`.
164
+
The following example shows how to add a `write`[permission](../resources/permission.md) for the `internal collaborators`[sharePointGroup](../resources/sharepointgroup.md) on a [driveItem](../resources/driveitem.md) identified by `01V4EPHZNV2OJQJNBPWNCKDTXCQ5TSVBJU` in a SharePoint Embedded [fileStorageContainer](../resources/filestoragecontainer.md) identified by `b!s8RqPCGh0ESQS2EYnKM0IKS3lM7GxjdAviiob7oc5pXv_0LiL-62Qq3IXyrXnEop`.
165
+
166
+
#### Request
167
+
168
+
The following example shows a request.
169
+
170
+
<!-- {
171
+
"blockType": "request",
172
+
"name": "driveitem-post-permissions-3",
173
+
"scopes": "filestoragecontainer.selected",
174
+
"target": "action"
175
+
} -->
176
+
```http
177
+
POST https://graph.microsoft.com/beta/drives/b!s8RqPCGh0ESQS2EYnKM0IKS3lM7GxjdAviiob7oc5pXv_0LiL-62Qq3IXyrXnEop/items/01V4EPHZNV2OJQJNBPWNCKDTXCQ5TSVBJU/permissions
### Example 3: Add a SharePoint group permission to a driveItem in a SharePoint Embedded container using the principalId
232
+
233
+
The following example shows how to add a `write`[permission](../resources/permission.md) for the `internal collaborators`[sharePointGroup](../resources/sharepointgroup.md) on a [driveItem](../resources/driveitem.md) identified by `01V4EPHZNV2OJQJNBPWNCKDTXCQ5TSVBJU` in a SharePoint Embedded [fileStorageContainer](../resources/filestoragecontainer.md) identified by `b!s8RqPCGh0ESQS2EYnKM0IKS3lM7GxjdAviiob7oc5pXv_0LiL-62Qq3IXyrXnEop`.
Copy file name to clipboardExpand all lines: api-reference/beta/api/filestoragecontainer-delete-sharepointgroups.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: "Delete sharePointGroup"
3
-
description: "Delete a sharePointGroup object."
3
+
description: "Delete a sharePointGroup object that is local to a fileStorageContainer."
4
4
author: "tmarwendo-microsoft"
5
5
ms.localizationpriority: medium
6
6
ms.subservice: "onedrive"
@@ -56,7 +56,7 @@ If successful, this method returns a `204 No Content` response code.
56
56
57
57
### Example 1: Delete a SharePoint group
58
58
59
-
The following example deletes a **sharePointGroup** identified by the ID `10` from the **fileStorageContainer** identified by the container ID `b!ISJs1WRro0y0EWgkUYcktDa0mE8zSlFEqFzqRn70Zwp1CEtDEBZgQICPkRbil_5Z`.
59
+
The following example deletes a **sharePointGroup** identified by the ID `ZGYwZTEzYTgtOTExOS00MjdmLWEzNjktOTdjOWM3YjNlYjcyXzE0` from the **fileStorageContainer** identified by the container ID `b!ISJs1WRro0y0EWgkUYcktDa0mE8zSlFEqFzqRn70Zwp1CEtDEBZgQICPkRbil_5Z`.
60
60
61
61
#### Request
62
62
@@ -68,7 +68,7 @@ The following example shows a request.
### Example 2: Attempt to delete a SharePoint group that doesn't exist
114
114
115
-
The following example attempts to delete a **sharePointGroup** identified by the ID `11` from the **fileStorageContainer** identified by the container ID `b!ISJs1WRro0y0EWgkUYcktDa0mE8zSlFEqFzqRn70Zwp1CEtDEBZgQICPkRbil_5Z`; however, the group doesn't exist in the container.
115
+
The following example attempts to delete a **sharePointGroup** identified by the ID `ZGYwZTEzYTgtOTExOS00MjdmLWEzNjktOTdjOWM3YjNlYjcyXzE1` from the **fileStorageContainer** identified by the container ID `b!ISJs1WRro0y0EWgkUYcktDa0mE8zSlFEqFzqRn70Zwp1CEtDEBZgQICPkRbil_5Z`; however, the group doesn't exist in the container.
116
116
117
117
#### Request
118
118
@@ -122,7 +122,7 @@ The following example attempts to delete a **sharePointGroup** identified by the
0 commit comments