Explanation Required for RBAC Privilages

[Ananduascdlm]

I am looking for an explanation We need explanation on why below access types are required by Veeam when using existing Azure Compute account?

"Microsoft.Network/virtualNetworks/read",
"Microsoft.Network/virtualNetworks/subnets/join/action",
"Microsoft.Network/publicIPAddresses/read",
"Microsoft.Network/publicIPAddresses/write",
"Microsoft.Network/publicIPAddresses/delete",
"Microsoft.Network/publicIPAddresses/join/action",
"Microsoft.Network/networkInterfaces/read",
"Microsoft.Network/networkInterfaces/write",
"Microsoft.Network/networkInterfaces/delete",
"Microsoft.Network/networkInterfaces/join/action",
"Microsoft.Network/networkSecurityGroups/read",
"Microsoft.Network/networkSecurityGroups/write",
"Microsoft.Network/networkSecurityGroups/delete",
"Microsoft.Network/networkSecurityGroups/join/action",

Case ID - 07567759

[Mildur]

Hello Anandu

I assume you mean permissions for our Archive Tier? When we archive backups from Azure Blob to Azure Archive Storage, we will deploy a archiver appliance in Azure. After the archival session, we will delete the VM.

To be able to create a virtual machine and to configure the network, the compute account requires these permissions.
Same goes if you have a performance tier on Azure Blob and you want to run a health check. In that case we will deploy a helper appliance.

Is there a specific challenge by granting this permissions in your tenant?

Best,
Fabian