The Azure Resource Manager team is actively investigating the scenarios around renaming resource groups. To help us better understand the use-cases and to determine which implementations may be viable to address the problem, we would appreciate if you could fill out this 3-minute survey:
https://aka.ms/RgRenamingScenariosCasey Meijer supported this idea ·
An error occurred while saving the commentCasey Meijer commented
Renaming resource groups is treated like a resource move behind the scenes. We will address this feature request once resource move is broadly supported across the various services. We would not want to release a rename feature where some resources ended up in the “renamed” resource group, while others were left behind.
This is not the right way to do this. The correct way is to introduce surrogate keys for your resource groups. Your proposed solution does not spare the pain of moving resources. In fact, it doesn't substantially change the process at all.