Get answers to the most frequently asked questions about Azure Compute Fleet.
Compute Fleet allows you to deploy up to 10,000 VMs in a singe request, as long as you have enough quota of Spot VMs and Standard VMs.
Can I specify target capacity at a Compute Fleet level without specifying Spot and Standard capacity?
No, target capacity is set individually for Spot and Standard, even if you're using a combination of both virtual machine (VM) types.
Yes, you can mix both Spot and Standard VM types in a single fleet request.
No, capacity is managed at a VM type level for Spot VMs and Standard VMs. Spot eviction doesn't trigger to deploy extra capacity on Standard VMs, nor are Spot VMs converted to Standard VMs.
East US, East US2, West US, and West US2.
Most SKUs are supported. However, B-series and promo versions of any VM size (example: Dv2, NV, NC, H promo sizes) aren't supported for Azure Spot VMs.
No. Before deploying, check if you have enough quota on Spot and Standard based on the target capacity requested. Compute Fleet rejects requests if a subscription doesn't have enough quota.
Yes, you're allowed to modify target capacity for Standard VMs. However, for Spot VMs, your Compute Fleet has to be configured for capacity preference maintain capacity.
You can add a minimum of 3 and maximum of 15 VM sizes to deploy Compute Fleet for Spot using the capacity preference Maintain. However, there's no minimum number for Standard VMs. The maximum you can add is 15.
Compute Fleet requests are active for a year (365 days).
Yes, you can delete your Compute Fleet request at any time. All VMs running inside the fleet are deleted.
Your Spot VMs continue to run until evicted and you incur billing charges. Your Standard VMs continue to run and you incur billing charges until you delete.
No, target capacity is set using VM instance attribute only.
No, you can't mix multiple CPU architectures in a single Compute Fleet request.
No, there's no start and stop time configuration available on Compute Fleet.