The Virtual Machine is in a Failed State

Jonty 0 Reputation points
2026-08-28T17:38:34.3366667+00:00

The "ProvisioningState/failed/BadRequest" error on your virtual machine typically indicates that there was an issue with the provisioning process due to a bad request. This could be caused by incorrect configurations or parameters that do not meet the requirements for the VM. To resolve this, you may need to review the configurations and ensure that all parameters are correctly set according to Azure's requirements. If you need further assistance, consider reaching out to Azure Support for more detailed guidance.

Azure Virtual Machines
Azure Virtual Machines

An Azure service that is used to provision Windows and Linux virtual machines.

0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. kagiyama yutaka 5,165 Reputation points
    2026-08-29T07:10:53.3933333+00:00

    i think the vm in failed/badrequest is handled by running reapply once and checking the first failed event in activity log, this is the flow azure shows. could you add the first failed event, each resource’s provisioningstate, the last operation, the api version, and the full badrequest message so the cause can be narrowed.

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-08-28T17:38:47.41+00:00

    For an Azure VM stuck in Failed state, the supported first step is to reapply the VM state.

    1. In the Azure portal, open the affected VM.
    2. Go to Support + troubleshooting > Redeploy + reapply.
    3. Select Reapply.

    This updates the VM objects and properties. This resolution is supported only for API version 2019-07-01 or later.

    CLI option:

    az vm reapply -g MyResourceGroup -n MyVm

    PowerShell option:

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

    If VM operations continue to fail after reapply, check these in the Azure portal:

    • Provisioning State
    • Resource Health
    • Activity Log to identify the operation that first caused the VM to enter the failed state

    If the issue persists and start/stop/delete operations continue to fail, backend intervention may be required through Microsoft Support.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.