Update fileStoreContainer permission
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.
Update an existing permission on a fileStorageContainer by making a PATCH request on the permission resource. Only the roles property can be updated. One role per user is supported. A new ID is generated for the updated permissions object.
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 | Not available. |
Delegated (personal Microsoft account) | Not supported. | Not supported. |
Application | FileStorageContainer.Selected | Not available. |
HTTP request
PATCH /storage/fileStorage/containers/{containerId}/permissions/{permissionId}
Request headers
Name | Description |
---|---|
Authorization | Bearer {token}. Required. Learn more about authentication and authorization. |
Content-Type | application/json. Required. |
Request body
In the request body, supply the new value for the roles property.
Permission type | Property | Type | Description |
---|---|---|---|
User | roles | Collection of String | Supported roles are reader , writer , manager , and owner . Required. |
Response
If successful, this method returns a 200 OK
response code.
Examples
Request
The following example shows a request.
PATCH https://graph.microsoft.com/beta/storage/fileStorage/containers/{containerId}/permissions/{permissionId}
Content-Type: application/json
{
"roles": ["manager"]
}
Response
The following example shows the response.
HTTP/1.1 200 OK
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for