How can we improve Azure Virtual Machines?

rename vm

Add the ability to rename a VM. The VM name is what appears in Azure, not the DNS name.

Changing a VM's name should not affect the VM in any way. If you need a unique identifier for a VM that does not change, I suggest using a GUID rather than the VM's name in Azure.

512 votes
Sign in
Sign in with: oidc
Signed in as (Sign out)

We’ll send you updates on this idea

Daniel Barbalace shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


Sign in
Sign in with: oidc
Signed in as (Sign out)
  • Anonymous commented  ·   ·  Flag as inappropriate

    This should be a standard feature. Please consider implementing this and/or attaching the Name field as a tag.

  • Justin King commented  ·   ·  Flag as inappropriate

    The name should be just a simple tag.

    That's how AWs does it.
    That's how GCP does it
    That's how VMware does it
    That's how Hyper-V does it ..

    Azure tried to get too clever and guess the intent of the name field. You guys guessed wrong. Use a UUID under the hood and revert this to a tag. Or at least let us add a 'name' tag that visually replaces the name in the console at least.

  • Anonymous commented  ·   ·  Flag as inappropriate

    this is crazy not to have this ability.
    in AWS it is as simple as changing the tag for 'Name' on the instance

  • David Lean commented  ·   ·  Flag as inappropriate

    I realise that it is possible to write a powershell script that identifies all resources in a VM (disk nic). Deletes the VM, Then recreates the VM with a new name. It runs in less than a minute.
    It is also possible to do something similar to rename disks. (copy to new name, delete old & reattach)

    As I could write a Rename-AzureRmVM & Rename-AzureRMManagedDisk function in a short period of time. (less than 4.5 years) Perhaps the Azure team might consider doing the same thing, while they are thinking about doing it better in the API.

  • Vivek commented  ·   ·  Flag as inappropriate

    current rename process taking too much time, its one of the key features that;s need to implicate soon.

  • tony commented  ·   ·  Flag as inappropriate

    Four years later, and it's still not a feature. Neat.

    This was so basic, I wasted probably ten minutes trying to figure out what I was missing. Didn't even consider that it was a feature that just hadn't been built yet, or worse, that developers architected themselves into a corner and did something daft like keying off of the object name instead of some unique identifier like, oh i dunno, uuid.

  • Florian Floimair commented  ·   ·  Flag as inappropriate

    I agree with what people wrote here. Not being able to rename resources is a big blocker and wastes a lot of time.
    One might think that this is a business decision so that users will have to have 2 times the same VM until everything has been ported from the old to the new (correctly named) VM.

    Renaming resources should be a basic feature unrelated to anything within the VM or other resources.

  • Ashley Johnson commented  ·   ·  Flag as inappropriate

    You have to admit.. @Microsoft you have a huge flaw here which is causing deep concern to customers migrating or setting up an azure infrastructure.. Why can't you provide one simple option?

  • PSC commented  ·   ·  Flag as inappropriate

    I believe that is why Azure is still on 2nd and AWS is on top. This is basic need.

Feedback and Knowledge Base