Edit

Share via

QuotaExceeded error when scaling virtual machine scale sets

  • Article

This article provides guidance on resolving "QuotaExceeded" errors during the deployment, migration, or scaling of Azure Virtual Machine Scale Sets.

Symptom

You receive a "QuotaExceeded" error when a virtual machine scale set is deployed, scaled, migrated between subscriptions, or migrated from the classic deployment model to the Azure Resource Manager (ARM) deployment model. For example, you might see an error such as the following example:

Error: Code=QuotaExceeded; Message=Operation could not be completed as it results in exceeding approved Total Regional Cores quota. Additional details - Deployment Model: Resource Manager,
Location: westus,
Current Limit: 100,
Current Usage: 56,
Additional Required: 56,
(Minimum) New Limit Required: 112.

Cause

The virtual machine scale set doesn't have enough quota available in the target Azure location or subscription. The Azure resources that are available to each virtual machine scale set, such as the total VM cores, are limited by subscription and by both the region and SKU family being used. For more information, see Virtual Machine Limits- Azure Resource Manager.

Resolution

Consult the following article for steps to confirm that quota limitations are causing the error message, and for information about opening a support request to increase your quota: Resolve errors for resource quotas

Contact us for help

If you have questions or need help, create a support request, or ask Azure community support. You can also submit product feedback to Azure feedback community.