Can't start, can't stop, can't delete the Azure VM

Question

Can't start, can't stop, can't delete the Azure VM

Abrar Adil S 476

Unable to start the VM, which went in to failed state, unable to detach the existing OS disks, can't update the NIC of the Azure VM.
Have tried to redeploy and reapply as well, nothing is working.

Tried to delete the VM and create a new one, but unable to delete it as well, receiving the error as below

*"An error occurred while deleting virtual machine 'APIManager-M2' and/or any selected resource(s) associated with it. Error: 'An unexpected error occured while processing the network profile of the VM. Please retry later.'"

*looking for suggestions on how to resolve this error.

0 comments

Answer accepted by question author

Jose Benjamin Solis Nolasco 9,621 Volunteer Moderator

Welcome to Microsoft Q&A

Hello @Abrar Adil S I hope you are doing well.

I have been in the same situation before follow this oficial guide from MS https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/windows/restart-resize-error-troubleshooting

Please check the following:

Verify the VM Provisioning State and Resource Health in the Azure portal.
Review the Activity Log to identify the operation that first caused the VM to enter the failed state.
Retry the operation after a few minutes, as transient platform issues can occasionally cause this behavior.
If the issue persists and all VM operations continue to fail, I recommend opening a Microsoft Support request, as backend intervention may be required to recover or remove the VM.

References

Troubleshoot Azure VM provisioning issues: https://learn.microsoft.com/azure/virtual-machines/troubleshooting/
Create an Azure support request: https://learn.microsoft.com/azure/azure-portal/supportability/how-to-create-azure-support-request

If my answer helped you resolve your issue, please consider marking it as the correct answer. This helps others in the community find solutions more easily.

Prasad Chaganti 775 Reputation points Microsoft External Staff Moderator

2026-07-07T22:15:25.6433333+00:00

Hi Abrar Adil S,

Just checking in to if you had a chance to see the response provide by Jose to your question. Please let us know if they were helpful and don't hesitate to reach out to us if you face any issue.

Thank you
Jose Benjamin Solis Nolasco 9,621 Reputation points Volunteer Moderator

2026-07-10T04:18:29.15+00:00

@Abrar Adil S Just following up, Do you need more guidance or assistance ?
Abrar Adil S 476 Reputation points

2026-07-10T04:21:27.0966667+00:00

the issue is related to the Outage presently going on in the Central India region, we have deleted the vm and recreated it after 48 hrs of the VM being unresponsive.
Jose Benjamin Solis Nolasco 9,621 Reputation points Volunteer Moderator

2026-07-10T04:29:32.0533333+00:00

@Abrar Adil S thanks for let us know,

If my answer helped you resolve your issue, please consider marking it as the correct answer. This helps others in the community find solutions more easily.

1 additional answer

Your answer

Prasad Chaganti 775 Reputation points Microsoft External Staff Moderator

2026-07-07T22:15:25.6433333+00:00

Hi Abrar Adil S,

Just checking in to if you had a chance to see the response provide by Jose to your question. Please let us know if they were helpful and don't hesitate to reach out to us if you face any issue.

Thank you
Jose Benjamin Solis Nolasco 9,621 Reputation points Volunteer Moderator

2026-07-10T04:18:29.15+00:00

@Abrar Adil S Just following up, Do you need more guidance or assistance ?
Abrar Adil S 476 Reputation points

2026-07-10T04:21:27.0966667+00:00

the issue is related to the Outage presently going on in the Central India region, we have deleted the vm and recreated it after 48 hrs of the VM being unresponsive.
Jose Benjamin Solis Nolasco 9,621 Reputation points Volunteer Moderator

2026-07-10T04:29:32.0533333+00:00

@Abrar Adil S thanks for let us know,

If my answer helped you resolve your issue, please consider marking it as the correct answer. This helps others in the community find solutions more easily.

Answer 1

The VM is stuck in a failed state and its network profile is preventing delete/start/stop operations. Use the supported "reapply" operation to refresh the VM’s properties, then retry delete or reconfigure.

Follow one of these paths:

Use Azure portal (recommended)
1. In the Azure portal, go to Virtual Machines.
2. Open the VM that shows Failed status.
3. Under Support + troubleshooting, select Redeploy + reapply.
4. Choose Reapply and wait for the operation to complete.
5. After reapply succeeds, try again to:
  - Delete the VM, or
  - Start/stop the VM, or
  - Update NIC / detach OS disk as needed.
Use Azure CLI
1. Make sure the correct subscription is selected:
```
      az account set --subscription "<SubscriptionIDName>"
```
2. Run reapply on the VM:
```
      az vm reapply -g MyResourceGroup -n APIManager-M2
```
3. When the command completes, retry the delete or other operations on the VM.

Use Azure PowerShell

Set the context to the correct subscription:

      Set-AzContext -Subscription "<Subid>"

Reapply the VM configuration and update it:

      Get-AzVM -ResourceGroupName <ResourceGroup> -Name APIManager-M2
      Set-AzVM -ResourceGroupName <ResourceGroup> -Name APIManager-M2 -Reapply
      Update-AzVM -VM <PSVirtualMachine> -ResourceGroupName <ResourceGroupName>

After this completes, attempt to delete or modify the VM again.

If delete still fails due to network profile issues after reapply, check and clean up dependent resources (NICs, IPs, peerings, etc.) in the recommended order before retrying deletion.

References: