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 commentAnonymous commented
It's okay for you guys who know your way round the object model of Azure and understand the whys and wherefores of the names things have but for those of us new or part-time users it's demoralising that the wrong decisions we make - like names - as we set things up can't be changed (easily). When our portal starts to look a mess it's easier to make more mistakes and eventually we turn away with a negative impression.
Similarly locations - a different issue I know but as you bring new locations online we want to be able to take advantage without having to rip everything apart and rebuild.