Fix: This Request is Not Authorized to Perform This Operation

Microsoft Azure churns out two common errors when trying to access content on storage accounts. One is: Experiencing high demand in this region.

The other is: This request is not authorized to perform this operation when accessing Azure Storage. This article looks at how you can fix this second error.

What causes this request is not authorized to perform this operation on Microsoft Azure storage?

There can be a lot of reasons users can’t read/write content on Azure storage containers and access blob objects on storage accounts. The common ones are:

• Invalid access key: Using the wrong storage name and access keys will return the error.
• Expired Azure storage container: You cannot access any resources on an expired Microsoft Azure container. 
• Incorrect role assignment: Without a contributor role, it’s impossible to read/write data on a storage account. Hence, the error.
• Restricted access by the administrator: The admin might have used Azure AD to limit your access to the storage account access keys.
• Disabled access key: Disabling storage account key access can prevent you from using even the correct access keys to authenticate your requests.

Now that we’ve identified the root of the problem, Let’s see how you can solve it.

How can I solve this request is not authorized to perform this operation on Microsoft Azure storage?

Before proceeding to the fixes in this guide, try these preliminary checks, as they could be the only solution you need:

• Verify access key: The first step is to verify that the access keys and storage account name you are using are correct.
• Check storage expiration: Make sure the Microsoft Azure storage container you are trying to access has not expired
• Confirm authorization: Confirm from the admin your access to the storage account is not restricted.
• Enable storage access key: Check to ensure you have Allow storage account key access enabled on the storage account.

If the error persists after using all these initial solutions, try the following advanced fixes.

1. Regenerate storage account access keys

1. Log in to your Azure portal and click Storage accounts.
   
2. Locate the storage account you want to access and click to open.
   
3. On the left pane, scroll down to Security + networking and select Access keys.
   
4. Click the Rotate icon next to key1 and select Yes to regenerate access key on the popup dialogue.
   
5. Click the Rotate icon next to key2 and select Yes to regenerate access key on the dialogue.
   
6. Next, update the connection strings in your code to access the new keys and try again to see if the problem is solved.

2. Change the default network access rule to allow access from all network

1. Select the storage account you want to access on your Azure dashboard.
   
2. Scroll down to Security + networking and select Networking under it.
   
3. Select Enable from all networks and click Save to apply changes.
   

3. Assign a storage contributor role

1. Open your Azure dashboard and select the storage account you are trying to access.
   
2. Click Access control (IAM) on the left pane and switch to the Role assignment tab.
   
3. Click Add at the top of the page and select Add role assignment.
   
4. Select the role you want to use, Storage Blob Data Contributor and click Next. 
   
5. Choose User, group, or service principal and click Select members.
   
6. Choose the account you want to add and click Select.
   
7. Once the account is added, click Review + assign. 
   
8. Click Review + assign again to assign the role.
   
9. Wait for the role assignment to complete and try to reaccess the storage.

Now, you should be able to solve this request is not authorized to perform this operation error on Microsoft Azure storage.

If you want extra control and flexibility over your Azure cloud storage resources, Microsoft Azure Storage Explorer is an intuitive application designed to give you just that. Check it out to see how it works.

Which of the above solutions works for you? Let us know in the comments area below.