Rename Resource Groups
Need the ability to rename resource groups either via PowerShell or the new portal.
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:
Matt Woodcock commented
Come on MS, all we want is a rename option!
Stefan Koell commented
Can't believe that this is not possible...
Same issue, wow, who in MS signed this design off! Change in business functions, departments, company mergers - so many reasons to rename resources.
Trond Haugmo commented
Since moving resources from one RG to another cannot be done with certain objects (for example when certs have been assigned to web apps) it is very frustrating that a resource group cannot be renamed.
Robert Caretta commented
So when will this be worked on?
Fayez Mohammed commented
I was surprised when I went back to rename my resources and could not, Opened a support case requesting they do it (assuming that feature was locked for us), and I was quite shocked to hear that its by design that you cannot rename resources. It would take a lot of additional hours to go in and redeploy all those resources with the correct name now. This is quite a flaw in my opinion, not sure what security constraints are attached to it that Microsoft has locked the renaming feature on the resources. Please get this addressed ASAP. Thanks
Kevin Strong-Holte commented
Wow. Just, wow.
Brian Seekford commented
Did they really use the Name field as a primary key? WTF?????
Claus Nielsen commented
Seriously? You can't rename resources?
I would like to add my .02 and vote this gets added as a "feature" or just a normal development standard moving forward. ;)
David Nemeth commented
"Renaming resource groups is treated like a resource move behind the scenes" <- Please tell me, it's not how you plan to solve this!
I might miss the point, but using the display name as ID doesn't sound to be a best practice for me.
Almiro Alves commented
I really miss that a lot. I think this is the basics and should have Azure for all services. It is not possible for Azure to use the services name as a key not to allow its change. Something terrible to believe!
Susantha Silva commented
Highly requested feature. Azure team can keep the GUID unique and allow name to be changed.
Thomas Schmidt commented
Absolutely agree with the comments below, the name is a human readable descriptive reference and needs to be editable, the GUID should be the unique resource thread!
Any Updates on when this will be available, its been a year
Mike Malter commented
Yes please. Resource groups have been implemented and now we have a list of resource groups with the the tag CloudServices imbedded in the name. Yesterday I opened a case because I could not understand why all of our Cloud Services were appearing in the Resource Group display on the portal. Seems that when Resource Groups were implemented, the exact name used for Cloud Services was used for Resource Groups. Only thing is that our naming convention requires the type of resource to be the suffix of the name - so it looked like the portal was broken and it confused everyone including the Microsoft tech. We got it worked out, but we really need a rename function so we can get the embedded Cloud Service suffix replaced. At this point you guys should really know better and always give the ability to rename something. Thank you.
PRISMA Computer GmbH commented
I'm completely shocked to hear that resources are really identified and related by their names and not by their GUID or whatever other kind of resource ID!!! Otherwise it's not explainable why a simple rename of a resource means moving the resource instead of just giving an unique identifier another human readable name... ridiculous!!
Paul Martin commented
Yes- we need this too! I agree that it is ridiculous that we can't change a the display name.
I only wish that I could move all resources to a new group, but with app services, and SendGrid, moving ain't so simple!
I understand that the API paths are built on resource group names, so they are imbedded in the infrastructure more deeply than just a visual display, but if we could provide a friendly display name for each resource, it would certainly make my life much easier!
I'd like to see this apply to ALL resource names, not just resource group names.
Yeah terrible design decisions that this is apparently so hard that it takes more than 3 years to implement...