VM allocation failed.We do not have sufficient capacity for the requested VM size in this region

Marco Adamo 25 Reputation points

i have a Basic support plan so i cannot open tech support ticket, but my VM in East US cannot start with the error reported in title. Also the move resource in a different region is unavailable because the provisioning state is failed. someone can help me?

Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
7,515 questions
{count} votes

3 answers

Sort by: Most helpful
  1. akinbade abiola 8,215 Reputation points

    Hello Marco Adamo,

    Thanks for your question.

    This is usually a capacity issue at the moment related issue at the Availability Zone.

    I will recommend you try a different availability zone and/or different varieties of the VM.

    Resizing the VM/Redeploying the VM to a different zone can fix the issue for you.

    I checked the status page and confirmed it is currently not a service downtime issue.

    Also see: Troubleshoot allocation failures when you create or resize VMs in Azure for detailed steps.



    You can mark it 'Accept Answer' and upvote if this helped.

  2. Nikhil Duserla 805 Reputation points Microsoft Vendor

    Hi Marco Adamo ,

    Thanks for reaching out to us on the Microsoft Q&A forum.

    We understand from your query that you are experiencing a VM allocation failures because of unprecedented growth in demand for Azure services in specific regions. This problem can occur when you try to create or start VMs in a region while the VMs display the following error code and message: AllocationFailed or ZonalAllocationFailed

    Error message: "Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at https://aka.ms/allocation-guidance"

    We recommend that until your preferred VM type is available in your desired region, we advise customers who encounter deployment issues to consider this temporary workaround and create the VM in the neighboring regions within the same geographical cluster. Try to create a different size VM SKU (latest) in case you are creating the VM with an older SKU. For more details on older SKUs refer to allocation-failure .

    If you have any further queries, do let us know.

    If the answer is helpful, please click "Accept Answer" and "Upvote it"

  3. Louis Guerra 0 Reputation points

    This is a major problem right now, I have confirmed this with three other companies and they are having the same issues.