Only 19 of the VMs on my VMSS are running. I want to run 80 instances for a university course

CS5285 CS5285 0 Reputation points
2025-08-15T10:53:17.9233333+00:00

I am having difficulty starting all the Virtual Machines in my VMSS. I want to run 80 instances for a university course, but only 19 of the 80 VM instances are able to run. I have a developer account, and I have an accepted quota of running 80 instances of "B2s configuration". I really need help to resolve this issue. The server location is east Asia.

Attached are some screenshots. Any help with this issue will be appreciated.screenshot_2

Regards,

Raphael

Azure Virtual Machine Scale Sets
Azure Virtual Machine Scale Sets
Azure compute resources that are used to create and manage groups of heterogeneous load-balanced virtual machines.
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Vinodh247 39,376 Reputation points MVP Volunteer Moderator
    2025-08-15T13:50:55.84+00:00

    Hi ,

    Thanks for reaching out to Microsoft Q&A.

    The issue you are facing, where only 19 out of the 80 intended Virtual Machine instances in your VMSS are running while the rest show a “Failed” status, is most likely due to regional capacity constraints in the East Asia datacenter rather than a quota problem. Even though you have an approved quota for 80 instances of the Standard_B2s size, Azure still needs available physical capacity in the chosen region to fulfill the allocation request. When demand is high, smaller VM sizes like B-series can be particularly constrained in certain regions. To resolve this, you should either redeploy the VMSS to a different region with better availability (such as Southeast Asia or Japan East) or switch to a VM size with more available capacity in East Asia. Additionally, verify that your VMSS upgrade policy, OS image reference, and any startup extensions are not causing provisioning failures. You can confirm the exact reason by checking the Activity Log or using the Azure CLI to view the instance provisioning state, which will indicate if the error is due to allocation failure. If capacity shortage is confirmed, moving to another region or changing the VM size is the fastest way to run all 80 instances successfully for your course.

    Please 'Upvote'(Thumbs-up) and 'Accept' as answer if the reply was helpful. This will be benefitting other community members who face the same issue.

    0 comments No comments

  2. Rashmika Inagadapa 1,090 Reputation points Microsoft External Staff Moderator
    2025-08-19T10:05:14.3433333+00:00

    Hi CS5285 CS5285,

    The reason only 19 out of 80 VMSS instances are provisioned is most likely due to regional capacity constraints in the East Asia datacenter, rather than a quota problem.

    Even if your subscription quota is approved for 80 Standard_B2s vCPUs, Azure still requires sufficient physical capacity in the chosen region or zone. When demand is high, certain VM sizes (especially popular ones like the B-series) may not be available in large quantities. In such cases, deployments beyond a certain threshold fail with errors such as Allocation Failed or Insufficient capacity.

    For more information, refer here: Troubleshooting Azure VM allocation failures - Virtual Machines | Microsoft Learn

    Follow the steps below to troubleshoot the issue:

    1. Check provisioning errors:
    • In the Azure Portal, go to your Virtual Machine Scale Set (VMSS)→ Activity Log.
    • Check the Activity Log for failed instances.
    • Errors like AllocationFailed or Insufficient capacity confirm the problem is a lack of available hardware(capacity) in the region.
    1. Verify quota limits
    • In the Azure Portal, go to Subscriptions > Usage + quotas.
    • Filter by Location = East Asia.
    • Verify both the B-series vCPU quota and the Total regional vCPU quota.
    • If your quota is less than the required 160 vCPUs (80 instances × 2 vCPUs), submit a request to increase it.

    For more information, refer here: Increase regional vCPU quotas - Azure Quotas | Microsoft Learn

    1. Try scaling in smaller increments: Instead of a single scale-out to 80, try provisioning in smaller batches (e.g., 25-30 at a time) to take advantage of newly freed-up capacity.
    2. Change region: Try Southeast Asia or Japan East, which may have better availability.
    3. Change VM size: Use B2ms or a small D-series SKU if East Asia must be used.
    4. Use capacity reservation: For predictable and long-term deployments, reserve the necessary capacity upfront to guarantee resource availability. For more information refer here: On-demand capacity reservation in Azure - Azure Virtual Machines | Microsoft Learn

     By confirming the error details, reviewing your quota limits, and adjusting either the region or VM size, you should be able to scale your VMSS to the desired 80 instances.If you still continue to see this AllocationFailed errors ,the best approach is to open a support request with Microsoft so the backend regional capacity can be reviewed and guidance can be provided on this issue.

    Let me know if you require any additional information from my end. I happy to help you with the queries. If the information is helpful, please click on Upvote and Accept Answer on it so that it can help other community members.

    Thank you,

    Rashmika


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.