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!
This is still coming. The work is being completed now and we will be able to expose it in a few months.
Any news? Facing this issue and having headache.
Please do something
Nicolas V. commented
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?
/!\ WARNING - This action cannot be undone /!\
Or something like this?
+1 vote !
Thomas Odell Balkeståhl commented
Dougla Morris commented
Any update on this, we are double your few months at this point.
Few months = ?
"a few months" ....... it has been nearly 6 months, wtf is happening?! 😒
Hullegård, Jimi commented
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).
The answer is understandable, Microsoft's business is to bill more money with support service. That is your main business.
Bachmann, Robert commented
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?
Sanjay Sharma commented
Any update on the work status please.
This is a necessary feature. Please make it up asap.
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.
A must have feature. please expedite.
how tf does this take 4 years to implement
A critical capability to have indeed.
Amit Bhardwaj commented
How long will it take to implement this? This option should be available ASAP. Give your users the flexibility to choose what they want to do with their resources.
Hi! What is the status on this please?
Tons of extra work, suggest additional confirmations for deletions of each associated components in the specific order, if you want it deleted you have to check the box for each component
Can we at least hide the resources that we deleted? I just tried to delete all my environment, besides the network configs and they are all still there.
I was trying to clean this up. But now it's all screwed up with items that don't even exist?
Tim Smith commented
Still waiting on this! How ridiculous! Add an "Are You Sure?" prompt and move on. This issue has gone on long enough.