Skip to main content

Azure Spot VM Billing, Pricing, and Eviction Behaviour

 When adopting Azure Spot Virtual Machines, one of the first challenges is understanding how billing and eviction actually work. Many people initially believe Spot VMs require a minimum runtime, such as 5 minutes. This is not correct. Spot VMs follow the same billing model as standard Pay-As-You-Go VMs: they are billed per second, with a 60-second minimum charge. If a VM runs for less than a minute, you pay for the full minute. After that, you pay only for the exact seconds it runs. The 5-minute intervals you may see on Azure pricing pages are only part of the UI graphs—they are not related to billing.

Spot pricing is based on Azure’s unused capacity. Because of this, Spot VMs often come at massive discounts—sometimes 65% to 90% off On-Demand pricing. The exact discount varies by VM family, region, availability zone, and overall demand. When provisioning a Spot VM, you can set a max price bid. Setting it to “-1” means you agree to pay up to the normal On-Demand price. Your VM will run as long as the current Spot price is equal to or below your bid. If the Spot price moves above your maximum, Azure evicts the VM. Capacity pressure can also trigger eviction, because Azure will always prioritize paying, On-Demand customers.


A critical point is that Spot VMs come with no SLA. Eviction may happen at any time. Standalone Spot VMs usually receive about 30 seconds' notice before eviction. In Virtual Machine Scale Sets, you may wait up to 2 minutes, depending on the configuration. Because of this, Spot is suited only for workloads that tolerate interruptions, such as batch processing, CI/CD agents, media rendering, GenAI model fine-tuning, big data ETL, or dev/test environments. These types of workloads must support checkpointing or quick restarts.
For workloads that must finish, it is best to use Spot as part of a resiliency strategy. A common design is to use VM Scale Sets with Spot Priority Mix mode, where Spot instances run first to save on costs and, if they are evicted, the system automatically fails over to On-Demand VMs. Another option is Azure Batch or Azure Container Instances, which can dynamically choose between Spot and On-Demand based on capacity.
Monitoring Spot's behavior is also important. You can track prices with Azure Monitor, the Pricing Calculator, or automation scripts. In regions with low contention, eviction rates may be extremely small—sometimes below 1%—which brings very high savings with low risk. Combining Spot with Capacity Reservations, Cost Management forecasting, and a solid retry/checkpoint strategy allows you to maximize both reliability and cost efficiency.
Azure Spot VMs are a strong tool for reducing cloud costs, but they require planning. When used correctly, they can deliver exceptional savings while still supporting demanding workloads.

Comments

Popular posts from this blog

Why Database Modernization Matters for AI

  When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...

Cloud Myths: Migrating to the cloud is quick and easy (Pill 2 of 5 / Cloud Pills)

The idea that migration to the cloud is simple, straightforward and rapid is a wrong assumption. It’s a common misconception of business stakeholders that generates delays, budget overruns and technical dept. A migration requires laborious planning, technical expertise and a rigorous process.  Migrations, especially cloud migrations, are not one-size-fits-all journeys. One of the most critical steps is under evaluation, under budget and under consideration. The evaluation phase, where existing infrastructure, applications, database, network and the end-to-end estate are evaluated and mapped to a cloud strategy, is crucial to ensure the success of cloud migration. Additional factors such as security, compliance, and system dependencies increase the complexity of cloud migration.  A misconception regarding lift-and-shits is that they are fast and cheap. Moving applications to the cloud without changes does not provide the capability to optimise costs and performance, leading to ...

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...