How can we improve Azure Virtual Machines?

← Virtual Machines

Delete VM with all associated resources

Deleting a VM is a lot of click work. I have to manually delete the associated Network interface, Network security group, Public IP address. And then, from the associated storage account, I have to drill down into the VHD container in the right Blob to delete the associated .vhd and .status files.

Also, I have to do it in the right order, because there are dependencies between the various objects. If not, it fails, and I get a big fat pink error.

Also, the overview list does not refresh after the 'success' notification is posted, so I sit there guessing which of the resources I already deleted and which I didn't.

It all feels boring, not fun and tedious!

334 votes
Sign in
(thinking…)
Sign in with: Microsoft
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Joost Molenaar shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

56 comments

Sign in
(thinking…)
Sign in with: Microsoft
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Anonymous commented  ·   ·  Flag as inappropriate

    I had the same problem with this process, to complex and nothing intuitive. A simples process for deleting a VM will be very welcome.

  • Waleed Raslan commented  ·   ·  Flag as inappropriate

    While waiting for this feature to land in the Azure Portal, there is an automated solution to selectively clean up VMs and all attached resources on subscription or resource group level based on tagging.

    This can be directly imported into Azure Automation runbooks from the Azure Automation gallery:
    https://gallery.technet.microsoft.com/scriptcenter/Parallel-complete-removal-718d6dd5

    CAUTION: This solution automatically removes resources from Azure subscriptions so it is not intended to be used on production subscriptions, the author is not responsible for any misuse of this solution. You need to confirm you fully understand that this solution will remove resources from your subscription before execution

    Azure VM Resources Saver removes below VM resources from Azure subscriptions in parallel using Microsoft PowerShell Workflow technology:

    1- Any VM not tagged with one of the following tags in 'untagged' removal mode: {Keep, keep, KEEP, do not remove}Or Any VM tagged with one of the following tags in 'tagged' removal mode: {Remove, remove, REMOVE}.
    2- Boot diagnostics storage container of the removed VMs
    3- All NICs associated with the removed VMs
    4- All Public IPs associated with the removed VMs
    5- All managed and unmanaged OS disks of the removed VMs with status blobs of the unmanaged OS disks
    6- All managed and unmanaged data disks attached to the removed VMs

    VM resources preserved:
    1- Network Security Group (NSG)
    2- Virtual Network (VNET)
    3- Resource group
    4- Storage accounts of boot diagnostics and unmanaged disks

    Compatibility:

    Tested on Azure Automation with AzureRM modules updated to latest available versions as of this date 26.02.2019

  • PeppaAlly commented  ·   ·  Flag as inappropriate

    It is fun to read all the comments. Making me forget the pain of deleting the resource.

  • Numto commented  ·   ·  Flag as inappropriate

    Any news? Facing this issue and having headache.
    Please do something

  • Nicolas V. commented  ·   ·  Flag as inappropriate

    Hi,

    Can we have an update on this? This is frustrating as if you create multiple VMs for test purposes and want to use same VM name after the VM was deleted, errors occurs as all those associated resources are still here and conflict to each other.

    How Microsoft can make product like this without thinking first how this will be used?

    If some people would prefer to keep -ip or -nsg for whatever reason (mainly to deploy the same elsewhere) why there is no option when delete the VM with a big warning like:

    Would you like to delete the VM and all its associated resources?
    [Yes] [No]
    /!\ WARNING - This action cannot be undone /!\

    Or something like this?

    +1 vote !

  • Hullegård, Jimi commented  ·   ·  Flag as inappropriate

    Just a side note about static public IP. In our case, we would definitely not want an automatic deletion of the public IP just because the VM using it is deleted. We want to keep the exact same IP number for when creating a new VM. So please make this configurable (preferably with the default being not to delete a static public IP, to reduce problems for people who have no idea about this feature).

  • Steve commented  ·   ·  Flag as inappropriate

    The answer is understandable, Microsoft's business is to bill more money with support service. That is your main business.

  • Robert commented  ·   ·  Flag as inappropriate

    Any news here? It should be normal that associated devices will be removed with the VM. Normally it is not needed anymore. Why keep it?

  • Anonymous commented  ·   ·  Flag as inappropriate

    We need this feature. The cost of maintaining orphaned resources is significant. We understand that some resources may be shared with other VM's. A list showing these dependencies and the option to choose (or not) would be a valuable feature.

    Also, provide a list of orphaned resources left behind from previous clean-ups.

    Thanks!

← Previous 1 3

Virtual Machines

Categories

Feedback and Knowledge Base

(thinking…)
Hosted by UserVoice