How It Works
When Azure has unused compute capacity in a region, it makes that capacity available as Spot VMs at a discount off the standard pay-as-you-go price. You set a maximum price you are willing to pay per hour. If the current Spot price stays below your maximum, your VM runs. If Azure needs the capacity back, or if the market price exceeds your maximum, Azure sends an eviction notice and terminates the VM within 30 seconds. Because of this, Spot VMs are suited to workloads that can tolerate interruption: batch processing, rendering, CI/CD pipelines, stateless web servers, and data analytics jobs that can checkpoint and resume. On AWS, the equivalent is Spot Instances. On GCP, the equivalent is Preemptible VMs or Spot VMs.
Why It Matters for Cloud Cost
Spot VMs can meaningfully reduce compute costs for the right workloads. The discount off on-demand pricing varies by VM size, region, and current demand. The risk is eviction: if your architecture is not designed to handle sudden termination, Spot VMs introduce reliability problems that outweigh the savings. Teams that over-rely on Spot without fault-tolerant design can face failed jobs, data loss, or service disruptions. For predictable, always-on workloads, Azure Reservations or Azure Savings Plans are a better fit because they provide guaranteed capacity with no eviction risk. Spot VMs are best used as a cost layer on top of a committed baseline, not as a replacement for it.
For predictable Azure workloads that are a poor fit for Spot, Usage AI’s CoPilot surfaces projected savings from Azure Savings Plans commitments for customer review before any purchase is executed.