Prevent deleting resource group by mistake

[dingmeng-xue]

Remove-AzResourceGroup asks user's confirmation before deleting the resource group. User may confirm deletion operation by mistake because they may not have chance to go through all resources in console or just forget it. However, resources under resource group may be critical to business and they do not support soft-delete yet. It will lead to big problem to user's business.

In Azure, customer has couple approach to avoid that mis-operation such as controlling the permission, or applying the lock on resource group to prevent deleting.

Azure PowerShell team is considering another approach from client side to prevent mistakes. We are learning other CLI tools' practice. rmdir doesn't allow user to delete non-empty folder on Unix. rmdir on Windows requires \s option. Remove-Item in PowerShell checks content of target folder as well. It shows below message if folder is not empty and -Recurse is not specified

PS C:\test> Remove-Item foo

Confirm
The item at C:\test\foo has children and the Recurse parameter was not specified. If you continue, all children will be removed with the item. Are you sure you want to
continue?
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "Y"): 

Similarly, we are proposing to check the content under resource group before executing deletion. If resource group is not empty and -Force is not specified, Remove-AzResourceGroup will print out all sub-resources as alert and stop cmdlet execution. If -Force is specified, cmdlet will delete resource group and all its sub resources as it is now.

We also thinking to introduce an environment variable to turn on/off this additional check.

Looking forward to your thoughts

[dcaro]

Due to no comments on this new feature, we are closing this conversation for now. Feel free to add comments or reopen a new feature request in the future if this capability is needed.