- Advertisement -
HomeCloudAzureThis request is not authorized to perform this operation - Azure-Veeam

This request is not authorized to perform this operation - Azure-Veeam

Problem

Attempting to add a new external repository (Azure blob storage container) to the Veeam Backup and Replication console throws the following error: 

This request is not authorized to perform this operation.

 I’ve been testing Veeam and some of the new features recently. This time was the turn for the new Veeam Backup for Microsoft Azure. However, there are many things I still don’t know about Azure. This is a new world for me, one that I am also excited to explore.

After you install and configure the Veeam Backup for Microsoft Azure VM and your Azure blob storage account, the next step is to add the storage repository you have configured. Here is where I am getting this error. The error is not only related to Veeam but for many products using the Azure Blob storage service.

This request is not authorized to perform this operation.

Solution

This error is due to a missing and necessary configuration in Firewall and virtual networks. The client IP address has not been added to the firewall rules for the storage account. 

- Advertisement -

The first thing to do is to access your Azure account.

@Azure Portal

  1. From Azure Home, select Storage accounts.
not authorized to perform this operation.
  1. Select the storage account you have linked with the Veeam Backup for Microsoft Azure service.
  2. On the storage account, go to Settings > Firewall and virtual networks.
  3. Click Selected networks (default).
  4. Make sure you have checked the Add your client IP address option. Or, add a new IP address in the box to allow access.
  5. Finally, click on Save.
Azure-Veeam-External-Repository
  1. Another option is to allow access from All networks.
Azure-Veeam-External-Repository

After adding IP addresses or all networks to allow access from the internet or your on-premise networks, you’ll be allowed to continue to the External Repository configuration. Or any other product that requires the connection to Azure storage accounts. 

Resources

Azure.

Veeam.

Juan Mulford
Juan Mulford
I have been active in IT for over fourteen years now. I am a solutions architect, working with storage, virtualization, and VDI solutions. For the past ten years, I have been living and working in Taiwan.

1 COMMENT

  1. we have changed the cloud endpoint from public to private in azure configuration.
    i am not able to connect to blob storage repo
    edit or create new one.
    what should i do ?

Leave a Reply

- Advertisement -

Popular Articles

mulcas.com-Raspberry-Pi

Raspberry Pi OS in a Virtual Machine with VMware

4
Although the Raspberry Pi OS is designed and optimized for the Raspberry Pi module, it is possible to test and use it without its hardware, with VMware. This solution can be useful if you are a developer (or just a curious guy) and don't have a Raspberry Pi module with you
Unable to delete inaccessible datastore

Unable to delete an "inaccessible" datastore

4
I was switching my storage array, so I migrated the VMs from that old datastore/storage to a new datastore/storage. The old datastore was shared by 3 ESXi hosts, no cluster. After migrating the VMs and unmount/delete the datastore, it was still presented in two of the ESXi hosts and was marked as inaccessible.
mulcas.com-VMware-OVF-Tool

How to export a Virtual Machine using the VMware OVF Tool

8
The VMware OVF Tool is implemented by VMware for easily importing and exporting virtual machines in Open Virtualization Format (OVF) standard format. Here, I want to show you how to download and install it, and then how to use it from a Windows machine.
This is not a valid source path / URL

This is not a valid source path / URL - SourceTree and Gitlab

0
I have been working on a project with a friend who set up a repository in Gitlab but even though I was able to view all projects on it, I couldn’t really join the repository. I was using SourceTree and Gitlab.
WinSCP VCSA

Unable to Access the VCSA 6.7 via WinSCP

8
One of the many and easiest ways to get the logs from the ESXi hosts and vCenter Server Appliance (VCSA), is accessing directly to the files directory using tools such as WinSCP, which helps to transfer the files between a local and a remote computer ( Ex. VCSA). I never have had issues with the ESXi hosts and WinSCP, however, trying to access the VCSA is a different story.
- Advertisement -

Recent Comments