Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
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.
Delete permissions from a fileStorageContainer object.
By default, this API removes access for an identity to the container and all items within the container, regardless of whether the identity has container-scoped or item-level permissions. You can add an optional Prefer: onlyRemoveContainerScopedPermission header when you call the API if only the identity's container-scoped permissions need to be removed. All item-level permissions explicitly granted to the identity (if any) are retained.
This API is available in the following national cloud deployments.
| Global service | US Government L4 | US Government L5 (DOD) | China operated by 21Vianet |
|---|---|---|---|
| ✅ | ✅ | ✅ | ✅ |
Permissions
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. For details about delegated and application permissions, see Permission types. To learn more about these permissions, see the permissions reference.
| Permission type | Least privileged permissions | Higher privileged permissions |
|---|---|---|
| Delegated (work or school account) | FileStorageContainer.Selected | FileStorageContainer.Manage.All |
| Delegated (personal Microsoft account) | FileStorageContainer.Selected | Not available. |
| Application | FileStorageContainer.Selected | Not available. |
Note
In addition to Microsoft Graph permissions, your app must have the necessary container type-level permission or permissions to call this API. For more information, see container types. To learn more about container type-level permissions, see SharePoint Embedded authorization.
HTTP request
DELETE /storage/fileStorage/containers/{containerId}/permissions/{permissionId}
DELETE /storage/fileStorage/containers/{containerId}/permissions(email='{email}')
DELETE /storage/fileStorage/containers/{containerId}/permissions(userPrincipalName='{userPrincipalName}')
Use the {email} or {userPrincipalName} alternate key only for permissions granted to a user. Use {permissionId} for other permission types. Alternate key values are strings and must be URL-encoded if they contain characters that aren't valid in a URL.
Request headers
| Name | Description |
|---|---|
| Authorization | Bearer {token}. Required. Learn more about authentication and authorization. |
Response
If successful, this method returns a 204 No Content response code.
Examples
Example 1: Delete a permission by ID
The following example shows how to delete a permission by ID.
Request
The following example shows a request.
DELETE https://graph.microsoft.com/beta/storage/fileStorage/containers/b!ISJs1WRro0y0EWgkUYcktDa0mE8zSlFEqFzqRn70Zwp1CEtDEBZgQICPkRbil_5Z/permissions/cmVhZGVyX2k6MCMuZnxtZW1iZXJzaGlwfGpobmFAY29udG9zby5jb20
Response
The following example shows the response.
HTTP/1.1 204 No Content
Example 2: Delete a permission by userPrincipalName
The following example shows how to use the userPrincipalName alternate key to delete a permission.
Request
The following example shows a request.
DELETE https://graph.microsoft.com/beta/storage/fileStorage/containers/b!ISJs1WRro0y0EWgkUYcktDa0mE8zSlFEqFzqRn70Zwp1CEtDEBZgQICPkRbil_5Z/permissions(userPrincipalName='jhan@contoso.com')
Response
The following example shows the response.
HTTP/1.1 204 No Content