`Remove-AzureRmResourceGroup -Force` should _always_ delete the specified resource group.

[twitchax]

Cmdlet(s)

Remove-AzureRmResourceGroup

PowerShell Version

4.4.1

Module Version

AzureRM.Resources 4.4.1

OS Version

N/A.

Description

Reported by @KirkMunro in this twitter thread.

Looks as though some services block the deletion of a resource group (e.g., Recovery Services Vault); though, there are some others, as well.

Debug Output

N/A.

Script/Steps for Reproduction

For a simple repro, run Remove-AzureRmResourceGroup -Force against an RG with a Recovery Services Vault resource.

[4c74356b41]

i second this

[MiYanni]

@twitchax I have an issue with Remove-AzureRmResourceGroup -Force that may/may not be related. Or may even be a bug. I have a resource group that has been 'stuck' deleting itself. It has been like this for a few hours. The only resource in the RG is a Classic Storage account. As far as I can tell, it will never succeed at deleting the RG.

We should probably 'refresh' this issue and have someone in Resources investigate.

[4c74356b41]

@MiYanni I doubt this is in anyway related to powershell, powershell just sends a request and waits for it to finish. nothing powershell can do to fix this. something wrong on the RP level. some long running operation is preventing the RP to delete the storage

[dufain]

Any updates on this? I'm running into the same problem.

[MiYanni]

@dufain No update for this at the moment. The main workaround is to determine which resource types have issues when the RG is trying to be deleted, and delete those prior to trying to delete the RG.

[KirkMunro]

@MiYanni That's not really an easy or viable workaround.

[MiYanni]

@KirkMunro If you don't want to figure out each problematic resource, you can just do the brute force method. It should just be a single line of script:

Find-AzureRmResource -ResourceGroupNameContains 'RGName' | Remove-AzureRmResource -Force

This will remove everything from the resource group. Then, remove the resource group.

[thomaslp86]

Is there a workaround to deleting a resource group that has an RSV which contains backup items which cannot be accessed because the VM was deleted? For context: I installed a Backup Agent on a VM; later deleted the VM without stoping backup. Now it cant delete the vault as it still shows that there're backup items though the VM has been deleted and there's no way I cant access the VM to stop the backup protection. I have tried the above mentioned cmdlets and the resource group is not still deleting.

[4c74356b41]

@thomaslp86 https://stackoverflow.com/questions/55187730/is-there-a-method-using-powershell-to-remove-a-backup-item-from-within-a-vault