This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(19.2, 4%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAK%3C/text%3E%3C/svg%3E)
I've got a VM that got stuck in state "Updating" during scaling to larger size. The agent stopped running (or wasn't reachable) and some disks were pending detachment.
I then tried to delete the VM. The current state (after several retries in the last 24 hours) is:
The datadisks (which I need to preserve) are in state "8 of 8 data disks pending detachment".
Do you have any advice?
You can update the delete behavior on an existing VM to keep os disk and try to use azure cli with force delete,
Reference: https://learn.microsoft.com/en-us/azure/virtual-machines/delete?tabs=cli2%2Cpowershell3%2Cportal4
Best Regards
try to get all background jobs started in the current session, like:
Get-Job -Command "get-process"
and try to terminate the process that is running with the VM
or try to stopping the vm with the -force parameter before using a web interface to delete the vm, just like:
Stop-AzVM -ResourceGroupName "TEMP" -Name "vm-linux" -force
Reference: https://learn.microsoft.com/en-us/azure/architecture/best-practices/background-jobs#azure-virtual-machines
Reference: https://learn.microsoft.com/en-us/powershell/azure/using-psjobs?view=azps-8.2.0
Reference: https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/get-job?view=powershell-7.2
Reference: https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/receive-job?view=powershell-7.2
Last:
web based management portal may be session broken, try using another browser and do the same process of deleting the vm via portal keeping the disks
Thanks for your feedback, @Jackson Martins . Unfortunately, I can't neither update the VM (to change the delete behaviour) nor stop-force it, because it's already marked for deletion:
PS C:\> Stop-AzVM -ResourceGroupName "<RG hidden>" -Name "<VM hidden>" -force
Stop-AzVM : Operation 'deallocate' is not allowed on VM '<VM hidden>' since the VM is marked for
deletion. You can only retry the Delete operation (or wait for an ongoing one to complete).
ErrorCode: OperationNotAllowed
There's no current deletion going on. I tried both of the following earlier
PS C:\> Remove-AzVM -ResourceGroupName "<RG hidden>" -Name "<VM hidden>"
PS C:\> Remove-AzVM -ResourceGroupName "<RG hidden>" -Name "<VM hidden>" -ForceDeletion $true
The state of the machine is "Stopped" with "The last operation performed on this VM failed."
Finally, the deletion succeeded. I used the variant with -ForceDeletion $true for the n-th time and now it worked.
Seemingly, something behind the scenes came back into place... days after the issue occured. Well.
Hi @Andreas Kerkau
great that works
--please don't forget to "[Accept the answer]" if the reply is helpful--
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(208, 35%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESM%3C/text%3E%3C/svg%3E)
Hello @Andreas Kerkau ,
Welcome to Microsoft QnA.
I came across this thread now and I see you had faced issues with deleting your VM.
To add to what Martin had suggested above (using force deletion), I am also sharing a couple of steps below which can help to resolve these kinds of issues going forward in future.
When a VM is in a "failed" state, it is reflective of the result of the last operation but it does not necessarily mean the VM is failed and not working. So, this means that the last operation (delete operation in this case) on your VM is failing, which is why the VM is in failed state.
Try to update the VM state by running the below command and see if the VM comes back to normal state. If it comes back to healthy state, then any operation on the VM should be successful.
az vm update -n <VMName> -g <ResourceGroupname>
Also, in your case, we could see that the VM had been marked for deletion, in such cases even after updating the VM (using az vm update) command, and force deleting using Powershell, you see no luck in deleting them successfully, please do get in touch with us or our Support Team, and they will be able to check the backend logs and help further in deleting the VM. Thank You.
-------------------------------
If the information is helpful, please "accept as answer" so that the relevancy of this post increases.
Hi I am having the same issue, so I have deployed with bicep three servers with image from market place, something went wrong, VMs are in failed state, and I cannot delete the VMs, error is:
An error occurred while deleting virtual machine and/or any selected resource(s) associated with it. Error: 'Operation 'Update VM' is not allowed on VM since the VM is marked for deletion. You can only retry the Delete operation (or wait for an ongoing one to complete).'
I tried with -force parameters, from powershell etc, but nothing works, how can I resolve this?
@Uros Opaka , could you please check and implement the steps on my above answer? Thanks.
What exactly this command do, I am more used to Powershell module for Azure in terms of Update-AzVM, I tried your command but it returns no resourcegroup found even though name is correct and RG exist, I have set the context with Set-AzContext, and If I use Get-AZresourcegroupname it lists the supposedly non exsisting RG..
I have three machines in this failed state, and I get different errors for them I tried to force delete another I got different error:
An error occurred while deleting virtual machine and/or any selected resource(s) associated with it. Error: 'Creating a virtual machine from Marketplace image or a custom image sourced from a Marketplace image requires Plan information in the request. VM: '/subscriptions/xxxxx/resourceGroups/xxxxx/providers/Microsoft.Compute/virtualMachines/xxxx'.'
I tried to deploy VMs with with some linux image which needed the plan in code and it was missing, and for that reason it went to this state that machines are in right now...