Get answers to the most frequently asked questions about Azure Compute Fleet.
How many virtual machines (VMs) can I deploy using Azure Compute fleet?
Compute Fleet allows you to deploy up to 10,000 VMs in a single 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.
Can I deploy both Spot VMs and Standard VMs in a single Compute Fleet request?
Yes, you can mix both Spot and Standard VM types in a single fleet request.
If Spot eviction happens, is more capacity deployed for Standard VMs to meet total fleet capacity?
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.
Which Azure regions support Compute Fleet?
Compute Fleet is available in all Azure public cloud regions. It isn't available in Azure sovereign clouds, including the Azure Government and Azure China sovereign clouds.
Which SKUs are supported for Compute Fleet?
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.
Do I have to request more quota for Standard VMs and Spot VMs to deploy Azure Compute Fleet?
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.
Can I modify my target capacity on my Compute Fleet?
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.
How many VM sizes/SKU types can I add while configuring the Compute Fleet?
You can specify between 1 and 10 VM sizes (SKUs) in a single Compute Fleet request.
How long is my Compute Fleet request active?
Compute Fleet requests are active for a year (365 days). In Launch mode, the fleet automatically deletes itself after a short period (about 5 hours) while the VMs it created persist.
Can I delete my Compute Fleet request?
Yes, you can delete your Compute Fleet request at any time. All VMs running inside the fleet are deleted. VMs created in Launch mode are standalone and continue running after the fleet object is removed; delete them separately with standard VM APIs.
What is Launch mode in Compute Fleet?
Launch mode provisions VMs in a single fleet request and then hands off control. The fleet object self-deletes after provisioning while the VMs persist and are managed by you or your orchestrator with standard VM APIs.
In Launch mode, how do I get the resource IDs of the VMs that were created?
Use the Fleet List VMs API (GET .../fleets/{fleetName}/virtualMachines) to retrieve each VM's name, resource ID, and provisioning status. This is the recommended way to discover the created VMs and monitor asynchronous provisioning. For more information, see Retrieve and monitor VMs.
Can I modify a Compute Fleet created in Launch mode?
No. You can't update the capacity or VM configuration of a Launch mode fleet after creation. Create a new fleet request to use different settings.
What happens if I don't delete the Compute Fleet with Spot VMs, after workload completion?
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.
Can I specify target capacity using VM based attribute selection like vCPU or memory?
No, target capacity is set using VM instance attribute only.
Can I mix multiple CPU architectures while configuring my Compute Fleet?
No, you can't mix multiple CPU architectures in a single Compute Fleet request.
Can I configure start and stop time for my Compute Fleet?
No, there's no start and stop time configuration available on Compute Fleet.
Can a Compute Fleet resource be moved ?
No. Compute Fleet doesn't currently support that capability. If you need to move, you can consider deleting it and using the Azure Resource Manager template to create another one in another location, subscription, or resource group.