Connections to storage account endpoint were blocked due to insufficient permission in the oAuth token presented

Question

Hi,

Connections to storage account endpoint were blocked due to insufficient permission in the oAuth token presented

Some requests to the storage account fidroxamsdocument were blocked as the permissions presented in oAuth bearer token were not sufficient for the operation performed between 12/13/2024 11:34:41 AM (UTC) and 12/13/2024 11:41:51 AM (UTC). Error Detail    OAuthAuthorizationErrorDetail:[RBAC] Access denied - no role assignment that permits Data Action Microsoft.Storage/storageAccounts/blobServices/containers/blobs/add/action, reason DeniedWithNoValidRBAC.

Can you please give me a solution ASAP.

Thanks

Answer 1

Hi @salman

Welcome to Microsoft Q&A Forum. Thanks for posting your query here!

As per the error message it seems that you are facing an issue related to insufficient permissions in the OAuth token presented when trying to connect to a storage account endpoint. The error message indicates that some requests to the storage account were blocked because the permissions presented in the OAuth bearer token were not sufficient for the operation performed.

Specifically, it mentions that there is no role assignment that permits the Data Action Microsoft.Storage/storageAccounts/blobServices/containers/blobs/add/action.

To resolve this issue, you should make sure that the user or service principal associated with the OAuth token has the appropriate role assigned that includes permissions for the required action. Ensure that the user or service principal should have Storage Blob Data Contributor or another role such as Storage Blob Data Owner, Storage Blob Data Reader that grants the required permissions.

Check for the proper role assignments, Navigate to Storage account through Portal>> In the left-hand menu, select Access Control (IAM) and then check for the Role assignments tab to see if the user or service principal has the necessary permissions.

If the user or service principal does not have the required permissions, you will need to assign a role that includes the necessary data actions.

Once the roles have been assigned, verify that the role assignment appears in the list and that it is correctly configured.

For more information, please refer the Azure built-in roles.

I hope this helps in resolving this issue. Please let us know if there are any further questions or issue still persists. we will be glad to assist you closely.

---

Please do consider to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.