Be able to rename a VNET (changing name only) without having to suppress all VM's and recreate them after...
Name is a unique identifier, hence not allowed to be modified, this is true for all top level resources not just VNet.
— Narayan [MSFT]
+1 , please concentrate on the paper cuts. there's so much basic functionality missing like this.
+1 from me.
And not just for VNETs, but for any resource.
Véronique Cabana commented
The name should not be the unique identifier. or add a display name that we can change.
Mike Malter commented
Even if it is a unique identifier, you can still rename it and rename it everywhere it exists within a transaction. We MUST be able to rename resources.
This is anti-Microsoft. You can rename anything including AD Domain Names. How can you suggest that the "name is a unique identifier, hence not allowed to be modified...?" It would be best to say we will eventually have this ability rather than essentially say this is how it is always going to be.
Gary Crook commented
Reorganizing resources so they can be easily viewed/managed is essential.
+1 from me (as it seems the Vote button is now disabled).
This approach is a major reason why we are likely to close our investment in Azure and move to another provider. The inability to rename resources in a company that has constant mergers and acquisitions makes Azure an endlessly frustrating experience.
Yeah, this is really disappointing.
Ernie Stavros commented
Why on earth would anyone make something like this and not allow rename. What year is this?
Um.... isn't this what UUIDs are for? Why cant we edit a display facsimile and have a never-changing uuid?
Yuval Ben-Ari commented
Did you really decline this request with this reason? Obviousely something was build very wrong from the ground. Why would the name be the unique identifier? Name must be allowed to be changed. This is a not a reasonable restriction. Networks are dynamic and change over time, renaming will always be needed. All networking infrastructure equipment allow renaming and the cloud should not be any different. There should be a system generated unique ID that the user does not care about and the name should be just a tag that should be allowed to change easily.
What should someone with exising VNet with hundered of VMs do if he needs to rename?
This is exaclty how it's done in AWS and you can rename with one click...
For ASM model downloading the confg file change and upload it will take the changes but in ARM thing much complicated
Just to confirm, if I re-importing the config file after making some changes, does it result in network downtime?
Why everything should be done through PowerShell? The only Windows I have here are on my walls. Everything here is so hard and painful. I can't wait to migrate to AWS.
Jamie Gruener commented
This kind of forward thinking is why AWS is kicking your Azure.
How do I export the XML, change it and re-import it? Are there instructions somewhere?
Why not create a new VNet then move resources to it? https://azure.microsoft.com/en-us/documentation/articles/virtual-networks-move-vm-role-to-subnet/
Igor Irić commented
If you alter configuration in XML file and import it, it will delete current and create new virtual network.
Stick it in Azure commented
This can be done by exporting your Network config XML file, altering the XML and then re-importing the configuration. This will not result in network downtime.