![]() Now try the backup again and it should complete. ![]() In my case this was TheSleepyAdmin_Backup_RG Put in the name of the resource group we create manually without the number. Go to Azure Backup center > Backup policies. In the backup policy we specify the new resource group. This needs to be RG name with 1 as this starting number in my case I used TheSleepyAdmin_Backup_RG1. Here are the steps that I did to get around this, by manually creating the resource group that will be used for the backup. I will be creating a manual resource group as I am not that familiar with creating custom policy yet and this was the quicker workaround.īelow is the link to the Microsoft document on creating a manual resource group for restore collection point. ![]() There are two option to work around this issue, either changing the policy from a Deny effect to a Modify effect, or create the resource group manually. To view the policy details we can go to Policy > assignmentsĬlick on the policy to view the parameter’s. When a initial backup is run it creates a resource group to save the restore point collection to and it is this resource group that is getting blocked by the Azure tag policy. This was being caused by a policy that one of the Azure Admins had setup to require tags be configure on resource groups. The error that showed in the reason was UserErrorRequestDisallowedByPolicy. During a recent project I have been deploying new VM to Azure, when trying to configure the Azure VM backup I was getting a failure at taking snapshot.
0 Comments
Leave a Reply. |