QuotaExceeded policy resource_error ai_generated partial

Error: Quota exceeded for quota metric: Standard DSv3 Family vCPUs. Limit: 10, Usage: 10, Requested: 2.

ID: policy/azure-resource-quota-exceeded-vm-cores

Also available as: JSON · Markdown · 中文
75%Fix Rate
87%Confidence
1Evidence
2024-01-20First Seen

Version Compatibility

VersionStatusIntroducedDeprecatedNotes
Azure Resource Manager API 2023-07-01 active
Azure CLI 2.50.0 active
Terraform azurerm 3.70.0 active

Root Cause

Azure enforces regional vCPU quotas per VM family; attempting to deploy a VM that exceeds the available quota fails.

generic

中文

Azure 对每个VM系列实施区域vCPU配额;尝试部署超出可用配额的VM会失败。

Official Documentation

https://learn.microsoft.com/en-us/azure/quotas/regional-quota-requests

Workarounds

  1. 80% success Submit a quota increase request via Azure portal: go to Subscriptions > Usage + quotas > select VM family > Request increase. Example: request 20 vCPUs for Standard DSv3 Family.
    Submit a quota increase request via Azure portal: go to Subscriptions > Usage + quotas > select VM family > Request increase. Example: request 20 vCPUs for Standard DSv3 Family.
  2. 70% success Deploy to a different region with available quota using `az vm create --location <region>`.
    Deploy to a different region with available quota using `az vm create --location <region>`.
  3. 60% success Use Azure Spot VMs which draw from a separate quota pool, if applicable.
    Use Azure Spot VMs which draw from a separate quota pool, if applicable.

中文步骤

  1. 通过Azure门户提交配额增加请求:转到订阅 > 使用量+配额 > 选择VM系列 > 请求增加。例如:为Standard DSv3系列请求20个vCPU。
  2. 使用`az vm create --location <region>`部署到有可用配额的其他区域。
  3. 如果适用,使用Azure Spot VM,它们使用独立的配额池。

Dead Ends

Common approaches that don't work:

  1. 50% fail

    Deleting VMs frees quota but may cause downtime; also, the quota limit is per region and family, so deletion only helps if you're at the cap.

  2. 70% fail

    The quota is per VM family (e.g., DSv3), not per size; all sizes in the family consume the same vCPU count as their specification.

  3. 80% fail

    You need to request an increase for the specific family and region you're deploying to, not a different one.