This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(124.80000000000001, 49%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGG%3C/text%3E%3C/svg%3E)
On Friday, my VM in West India would not start due to lack of capacity in the region. I kept trying for 12 hours, and finally it did start during the night in India when more resources were available.
How should I resolve so this does not occur again?
In other words, should I move it to a different region with more available capacity? There is East and Central India but I don't know if those too are nearing peak load.
The specific region is not really important - it's just used by an Indian developer so the biggest issues is just not wanting the VM to be unavailable.
Below doc has few suggestions. Please check if that helps:
Troubleshoot allocation failures when you create, restart, or resize VMs in Azure
@Vaibhav-Chaudhari Thank you, but the link does not address Azure having reached capacity and so I cannot start my VM. If it does, I do not see it.
My question is how to prevent this situation from occurring again in the future.
There is not a direct way to avoid this. If the data center has capacity issues the only real option is to wait, move to a different data center with more capacity, or keep your VM running so you don't lose the resources associated with your VM. You can also consider adding a second VM in another location and load balancing the two. That way if one VM cannot start due to capacity, you can start the other VM in the second region and traffic will be diverted to that VM instead. Whenever we have low capacity the product teams take note and work to allocate more servers in that area.