OSProvisioningTimedOut Azure Origin: Platform & cloud Last updated 15 Oct 2026

Azure VM: OSProvisioningTimedOut — OS Provisioning for VM did not finish in the allotted time

The VM booted but its guest agent didn’t report provisioning success in time — usually a generalisation problem with a custom image, or the agent can’t reach Azure.

Exact message you may see OS Provisioning for VM did not finish in the allotted timeVM agent not ready
Explore the map of this error Full error map →
Seen on: Azure

Meaning

Custom images must be generalised (sysprep / waagent -deprovision). Missing/broken guest agents, cloud-init errors or network rules blocking the WireServer (168.63.129.16) also cause the timeout.

Common causes

  • Custom image not generalised (or generalised image used as specialized)
  • VM agent/cloud-init missing or failing
  • NSG/firewall blocking 168.63.129.16
  • Slow first boot (large image)

⚡ Quick fix

  1. Generalise the source image correctly and recapture
  2. Check boot diagnostics/serial console
  3. Ensure the guest agent is installed and the WireServer reachable

Detailed fix by platform

Azure CLI

  1. az vm boot-diagnostics get-boot-log -g rg -n vm1 | tail -50

How to diagnose

  1. Image — Generalized vs specialized
  2. Boot log — Agent/cloud-init errors
  3. Network — Access to 168.63.129.16

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):

1011 — Cloudflare Error 1011: Access denied (Hotlinking denied) (Cloudflare)1011AllocationFailed — Azure VM: AllocationFailed / ZonalAllocationFailed — Allocation failed. We do not have sufficient capacity for the requested VM size (Azure)AllocationFailedconflict: unable to remove repository reference — conflict: unable to remove repository reference (must force) - container is using its referenced image (Docker)conflict: unable to r…exec format error — exec /usr/local/bin/docker-entrypoint.sh: exec format error (Docker)exec format errorGD missing — Fatal error: Uncaught Error: Call to undefined function imagecreatefromjpeg() (PHP)GD missingimage has dependent child images — conflict: unable to delete image (cannot be forced) - image has dependent child images (Docker)image has dependent c…ImagePullBackOff — Kubernetes: ImagePullBackOff / ErrImagePull (Kubernetes)ImagePullBackOffInstance reachability check failed — EC2 status check failed: Instance reachability check failed (1/2 checks passed) (AWS)Instance reachability…OSProvisi…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.