OSProvisioningTimedOut 🔷 Azure

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.

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:

🧠 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.