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:
An error occurred while saving the commentMike Toupin commented
I am also stuck with MS recommendation. I recreating our Vnet peering to reflect a Hub and Spoke and I can't simply moving a Gateway, ActiveDirectory Domain Service and Domain Service on another RG. Those cannot be moved and will require to be recreated. This is nuts, do you imagine the impact to recreate your main source of identity/authentication for your entire Cloud?
The RG name should be considered as a simple Label and should not even affect the Resource ID on the back plane...Mike Toupin supported this idea ·