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(230.39999999999998, 59%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERT%3C/text%3E%3C/svg%3E)
I've been trying to delete this VM for 3 / 4 days now. Each time I receive the following error message: Error details tts-vm-dev-migrate-cus-datadisk-1: Disk tts-vm-dev-migrate-cus-datadisk-1 is attached to VM /subscriptions/e50032d2-fb91-4661-9999-0c325f390855/resourceGroups/tts-rg-dev-machines-cus/providers/Microsoft.Compute/virtualMachines/tts-vm-dev-migrate-cus. (Code: OperationNotAllowed) tts-vm-dev-migrate-cus-datadisk-2: Disk tts-vm-dev-migrate-cus-datadisk-2 is attached to VM /subscriptions/e50032d2-fb91-4661-9999-0c325f390855/resourceGroups/tts-rg-dev-machines-cus/providers/Microsoft.Compute/virtualMachines/tts-vm-dev-migrate-cus. (Code: OperationNotAllowed) tts-vm-dev-migrate-cus-nic01: Network Interface /subscriptions/e50032d2-fb91-4661-9999-0c325f390855/resourceGroups/tts-rg-dev-machines-cus/providers/Microsoft.Network/networkInterfaces/tts-vm-dev-migrate-cus-nic01 is used by existing resource /subscriptions/e50032d2-fb91-4661-9999-0c325f390855/resourceGroups/tts-rg-dev-machines-cus/providers/Microsoft.Compute/virtualMachines/tts-vm-dev-migrate-cus. In order to delete the network interface, it must be dissociated from the resource. To learn more, see aka.ms/deletenic. (Code: NicInUse) tts-vm-dev-migrate-cus-original-osdisk-delete: Disk tts-vm-dev-migrate-cus-original-osdisk-delete is attached to VM /subscriptions/e50032d2-fb91-4661-9999-0c325f390855/resourceGroups/tts-rg-dev-machines-cus/providers/Microsoft.Compute/virtualMachines/tts-vm-dev-migrate-cus. (Code: OperationNotAllowed) tts-vm-dev-migrate-cus: An internal execution error occurred. Please retry later. (Code: InternalExecutionError)
![](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(118.4, 98%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKM%3C/text%3E%3C/svg%3E)
@Randy Toler The error message says that there are resources associated with the VM you are trying to delete. Please follow the instructions here on Delete a VM and attached resources. You can use Portal, CLI or PowerShell.
To delete the NIC:
You can delete a NIC if it's not attached to a VM. If the NIC is attached to a VM, you must first stop and deallocate the VM, then detach the NIC.
To detach the NIC from the VM, complete the steps in Remove a network interface from a VM. A VM must always have at least one NIC attached to it, so you can't delete the only NIC from a VM.
Force Delete: For VMs that don't require graceful shutdown, Force Delete will delete the VM as fast as possible while relieving the logical resources from the VM, bypassing the graceful shutdown and some of the cleanup operations.
Ensure that you have the required backups before trying the force delete.
Let me know the results after trying the suggestions above.
If I issue the following:
$VirtualMachine = Get-AzVM -ResourceGroupName 'rg' -Name 'vmname'
Remove-AzVM -Name $VirtualMachine.Name -ResourceGroupName $VirtualMachine.ResourceGroupName -ForceDeletion:$true -Confirm:$false
$DataDisks = $VirtualMachine.StorageProfile.DataDisks
foreach ( $Disk in $DataDisks ){
Get-AzDisk -DiskName $Disk.Name | Remove-AzDisk -Force
}
I get the following:
Remove-AzVM:
Line |
2 | Remove-AzVM -Name $VirtualMachine.Name -ResourceGroupName $VirtualMac …
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| Long running operation failed with status 'Failed'. Additional Info:'An internal execution error occurred. Please retry later.'
ErrorCode: InternalExecutionError
ErrorMessage: An internal execution error occurred. Please retry later.
ErrorTarget:
StartTime: 2/12/2024 12:25:07 PM
EndTime: 2/12/2024 12:25:07 PM
OperationID: a5273422-f5f4-4d7a-9071-4b296697e67b
Status: Failed
Remove-AzDisk:
Line |
5 | Get-AzDisk -DiskName $Disk.Name | Remove-AzDisk -Force
| ~~~~~~~~~~~~~~~~~~~~
ErrorCode: OperationNotAllowed
ErrorMessage: Disk is attached to VM /subscriptions/<sub>/resourceGroups/tts-rg-dev-machines-cus/providers/Microsoft.Compute/virtualMachines/tts-vm-dev-migrate-cus.
ErrorTarget:
StatusCode: 409
ReasonPhrase: Conflict
OperationID : 39a73968-3207-48ff-8fb9-a2f77fc71f98
If you already have a VM, you can change its behavior when deleted. For example, you can detach disks for reuse:
az resource update --resource-group myResourceGroup --name myVM --resource-type virtualMachines --namespace Microsoft.Compute --set properties.storageProfile.osDisk.deleteOption=detach.Force Delete for VMs:
(OperationNotAllowed) 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). Code: OperationNotAllowed Message: 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).
@Randy Toler Did you try the force delete option as described here: https://learn.microsoft.com/en-us/azure/virtual-machines/delete?tabs=portal2%2Ccli3%2Ccli4%2Cportal5#force-delete-for-vms
For VMs that don't require graceful shutdown, Force Delete will delete the VM as fast as possible while relieving the logical resources from the VM, bypassing the graceful shutdown and some of the cleanup operations.
Ensure that you have the required backups before trying the force delete.
Let me know if you are still stuck after trying force delete and we will get a support request enabled for you. Thanks.
In the end, I had to open a case with MSFT. They to perform an ARM Sync from backend, released the lease, and remove the disked 'marked for deletion'. I was then able to remove the VM and the remaining resources / Resource Group.
@Randy Toler Thanks for sharing the update.
@Randy Toler I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this!
Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to "Accept " the answer. Accepted answers show up at the top, resulting in improved discoverability for others.
Issue: Unable to delete Azure Virtual Machine & Associated Resources
Solution: Customer shared - "In the end, I had to open a case with MSFT. They performed an ARM Sync from backend, released the lease, and removed the disked 'marked for deletion'. I was then able to remove the VM and the remaining resources / Resource Group."
If your issue remains unresolved or have further questions, please let us know in the comments how we can assist. We are here to help you and strive to make your experience better and greatly value your feedback.
![](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(166.4, 72%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAD%3C/text%3E%3C/svg%3E)
Simple solution:
In the deallocated state of the VM, go to size menu and change the size of the machine temporary to a different size that allows more than 2 NIC`s like D8ls_V5
After that you will be able to delete it from Azure portal