In our network we have several access points of Brand Ubiquity. Microsoft Azure joins Collectives on Stack Overflow. The default gateway and DNS server couldn't be reached from the guest VM. Do not just run a "Set" command unless resetting settings is intentional. Navigate to the VM that's stuck in the Failed state. Error message: The VM is in failed provisioning state. Will extension.log help us in this case ? To verify that the default gateway and DNS server can be reached from the VM, do the following steps: To find out the IP addresses for the default gateway and DNS servers, go to the local UI for your device. An Azure service that is used to provision Windows and Linux virtual machines. Most error codes contain a detailed description of what the problem might be and offer hints to solve it. If any extension is in a failed state, then it can interfere with the backup. If your scheduled backup still fails, then try manually deleting the restore point collection using the steps listed here. Error description: cloud init did not run, or there were issues while cloud init was running. This article describes these states and highlights when customers are billed for instance usage. Most Virtual WAN related resources such as vpnGateways leverage the "Update" cmdlet and not the "Set" for write operations. If you delete the Resource Group of the VM, or the VM itself, the instant restore snapshots of managed disks remain active and expire according to the retention set. Please check that the system either has Internet access, or that a valid HTTP proxy has been configured for the agent. Suggested solution: Make sure the Provisioning flags in the /etc/waagent.conf file have the following values: This section provides guidance for issues that cause network interface creation to fail during a VM deployment. If the VM provisioning state is in an updating state, it can interfere with the backup. For more information, see cloud-init support for virtual machines in Azure. Also, backup of encrypted disks greater than 4 TB in size isn't currently supported. Seen when migrating from Azure Service Manager to Azure Resource Manager. Browse other questions tagged, Where developers & technologists share private knowledge with coworkers, Reach developers & technologists worldwide. If the resource (RP Collection) has a large number of Restore Points, then deleting them from the portal may timeout and fail. When VM provisioning times out, you see the following error: The following issues are the top causes of VM provisioning timeouts: Error description: The VM was assigned a static IP address that is already in use, and VM provisioning failed. Cause 3: The agent installed in the VM is out of date (for Linux VMs), Error code: BackUpOperationFailed / BackUpOperationFailedV2 Expect this on-demand operation to fail the first time. In addition, it seems that you may encounter this kind of issue when you create the VM with an image which is not syspreped. "This occurs when one of the extension failures leads VM state to be in failed provisioning state. In the VM InstanceView, there's an element within the status array in the form of ProvisioningState/