An Azure service that is used to provision Windows and Linux virtual machines.
Hello Matt,
Thank you for your question. You’re not doing anything wrong.
Adding to Sunoj Response.
When Azure shows F‑series VM sizes as unavailable, it is typically due to subscription‑level vCPU quotas or regional capacity constraints, rather than a configuration issue with your VM deployment.
Cause of the issue.
vCPU quota limits (most common) :
Azure enforces vCPU quotas per subscription and per region, including limits for specific VM families such as the Standard F‑series. If either the Total Regional vCPU quota or the F‑series family quota is set to zero (or already consumed), Azure will mark all F‑series sizes as unavailable during VM creation.
Regional capacity availability :
Even when quota exists, Azure may temporarily restrict certain VM sizes if physical capacity is unavailable in the selected region. In this case, the size is hidden or disabled until capacity becomes available.
Subscription or region restrictions :
VM size availability varies by region and subscription type. Not all VM families are enabled in all regions by default.
Workaround for the issue.
- Check your current quota for Standard F‑family vCPUs in the target region via Subscriptions → Usage + quotas, or by using
az vm list-usage. - If the F‑series quota is zero or insufficient, submit a quota increase request for the required region.
- If quota is available but the size is still unavailable, try deploying in an alternate region where F‑series capacity is available.
Alternative's
- Closest F‑series replacement: Dv5 / Dv4
- CPU‑heavy with flexible memory: E‑series
- Low‑cost / Dev‑Test workloads: B‑series
- Cost‑efficient compute: Dasv5 (AMD)
- Next‑gen compute‑optimized: Fx‑series
Links :
https://learn.microsoft.com/en-us/azure/virtual-machines/quotas?tabs=cli
https://learn.microsoft.com/en-us/azure/quotas/quickstart-increase-quota-portal
Thanks,
Manish.