Provisioning failed RRS feed

  • Question

  • Provisioning failed. OS Provisioning for VM '' did not finish in the allotted time. However, the VM guest agent was detected running. This suggests the guest OS has not been properly prepared to be used as a VM image (with CreateOption=FromImage). To resolve this issue, either use the VHD as is with CreateOption=Attach or prepare it properly for use as an image: * Instructions for Windows: https://azure.microsoft.com/documentation/articles/virtual-machines-windows-upload-image/ * Instructions for Linux: https://azure.microsoft.com/documentation/articles/virtual-machines-linux-capture-image/. OSProvisioningTimedOut

    I've followed all the attached links above, minus sysprep as its a domain controller.

    Virtual machine is currently running, I can RDP into the VM and work as per normal. However I can initiate a password reset through Azure tools or press the start button in the overview page.

    I'm migrating 10 virtual machines in the coming week/s and need to get this fixed. 

    I followed this article too:


    Monday, June 19, 2017 7:13 AM

All replies

  • [ERROR] Failed to obtain fabric URI. ControlSystem not initialized.
    Monday, June 19, 2017 7:19 AM
  • The uploaded specialized VHD might not have provisioned correctly. This could occur due to the current state of the machine when the VHD was being prepared for upload to Azure. I suggest you retry the process and see if the provisioning completes successfully. In https://docs.microsoft.com/en-gb/azure/virtual-machines/windows/prepare-for-upload-vhd-image complete all the recommended configurations especially the VM Agent part and see if it works. "However I can initiate a password reset through Azure tools or press the start button in the overview page." I believe you meant you "cant".

    If the above still gives you the same result then we need to check on this since it might be a platform issue in relation to the uploaded VHD or it could be that the VHD has not been prepared as recommended. You will have to open a technical support ticket for us to check on it since it requires your subscription details for troubleshooting.


    Do click on "Mark as Answer" on the post that helps you, this can be beneficial to other community members.
    Monday, June 19, 2017 11:30 AM