One caveat before the details. The Azure Updates page itself returned no usable text, so the specifics below come from two other places. One is a summary of Microsoft's Azure Compute blog post, as listed by the Xebia Tech Hub aggregator. The other is Microsoft Learn's New-AzVM documentation. The full announcement wasn't available, so exact runtime targets, notice windows and billing thresholds are unconfirmed.
What Spot Plus is
Standard Spot VMs sell unused Azure capacity at a deep discount. The catch is that Spot VMs can be evicted at any time if Azure needs capacity. Spot Plus is Microsoft's attempt to soften that trade-off.
The blog summary says the preview covers best-effort runtime targets, billing protection for early capacity evictions, longer eviction notices, rebalance signals, and deployment requirements for individual virtual machines and scale sets. The summary doesn't give the numbers behind any of those.
Microsoft Learn describes Spot Plus as the next generation of Azure Spot that provides higher reliability and longer running time than 'Spot' at a discounted price. That is a comparison with Spot, not a guarantee. Nothing I could verify says Spot Plus removes eviction, promises a minimum runtime or carries an availability SLA.
The standard Spot model was already clear that it has no SLA. Microsoft said in a separate Spot preview post that Spot VMs do not come with availability guarantees. That post was about standby pools, but the point applies to Spot generally. I found nothing that changes it for Spot Plus.
How you create one
The documentation includes a PowerShell example. It uses the Priority parameter, which Microsoft says supports 'Regular', 'Spot', 'SpotPlus' and 'Low'. The documented example looks like this:
New-AzVM -ResourceGroupName "MyResourceGroup" `
-Name "MySpotPlusVM" `
-Location "eastus2" `
-Credential (Get-Credential) `
-Size "Standard_D2s_v5" `
-Image "Win2022AzureEdition" `
-Priority "SpotPlus" `
-EvictionPolicy "Delete" `
-MaxPrice -1
The resource group, name, region, size and image are sample values from the documentation. They aren't requirements. The parts that matter are -Priority "SpotPlus" plus the eviction policy and max price settings. For -EvictionPolicy, Learn lists the supported values as Deallocate and Delete.
Learn also says billing and eviction work the same as Spot. -EvictionPolicy and -MaxPrice are used the same way. If you already script Spot deployments, the change is small. Learn doesn't explain what -MaxPrice -1 means in the example. For Azure Spot generally, my understanding is that -1 means you won't be evicted for price reasons, but that is general Azure knowledge and not something these sources confirm.
Prerequisites
Being able to type the parameter doesn't mean the deployment will succeed. Learn says using 'SpotPlus' requires the 'Microsoft.Compute/SpotPlus' subscription feature to be registered and a region where the feature is enabled.
A sensible first pass:
- Check whether
Microsoft.Compute/SpotPlusis registered on the subscription you plan to use. - Confirm your target region has the feature enabled. I couldn't find a published region list.
- Pick a VM size that is available in that region and subscription. Learn suggests
Get-AzComputeResourceSkufor finding available sizes. - Decide between a standalone VM and a scale set. The blog summary says the two have different deployment requirements, but it doesn't spell them out. I won't guess at them.
What preview status means
Azure's own status definitions matter here. The Azure Updates page says "In preview" means available to all Azure customers for non-production use and testing. So this isn't something to put under production workloads yet.
Spot is already an odd fit for anything fragile, and preview adds more uncertainty. Sensible habits:
- Keep checkpointing, retries and replacement capacity in place. Nothing I found suggests Spot Plus replaces them.
- Test how your application handles the rebalance signal and eviction notice. The exact format and timing are unpublished in my sources, so check them in the full announcement before you build on them.
- Don't build cost models yet. Neither source quantifies the discount, and the billing-protection rules for early evictions are unspecified.
Why it matters
Spot discounts are attractive for batch jobs, CI runners, rendering and dev/test environments. The usual objection is unpredictability. Early-eviction billing protection and rebalance signals look aimed at that objection, and the main selling point is better planning around interruptions.
Azure has been working on the Spot experience for a while. The same blog family has covered a Spot placement score for judging deployment success odds, and a Spot priority mix for scale sets that blend Spot and standard VMs. Spot Plus looks like another step in the same direction: more predictable discounted compute, without claiming to be guaranteed compute.
It's also worth being skeptical. "Best-effort" targets are not commitments, and "higher reliability" is relative to a baseline Microsoft doesn't quantify in these sources. Until the numbers are published, comparing Spot Plus to Spot or to regular VMs is guesswork.
Bottom line
Spot Plus is a preview tier of Azure Spot with longer runtime targets and better eviction handling. You select it with Priority "SpotPlus", and it needs the Microsoft.Compute/SpotPlus subscription feature and a supported region. It is a test-and-evaluate option for now. The detailed terms, including runtime targets, notice windows, billing protection and scale set requirements, are in Microsoft's full announcement, which I couldn't open. Read those before you commit any real workload.
References
- (In preview) Public Preview: Azure Compute Spot plus Azure Updates · 2026-11-17T20:00:32Z
- Announcing the general availability of Azure Spot Virtual Machines azure.microsoft.com
- Public Preview: Use Spot Instances in Standby Pools for Virtual Machine Scale Sets techcommunity.microsoft.com