I'm having major capacity issues with the NVads_A10_v5 series VMs. We have a pool of 25 VMs, and none of them will start up; they just switch to our secondary options instead. We're located in East US 2, and I'm getting really frustrated because I need these VMs up and running. Is anyone else experiencing this?
1 Answer
They're actually working on a new placement API to help with this. It tells you if a VM size can be deployed in a certain region and availability zone, but it's still in private preview. It might be worth reaching out to their Support or Engineering team to see if they can get it activated for you. We've dealt with similar problems in the Northeast, but this API has helped us know in advance if we can deploy a certain size.
Thanks for the info! While it's aggravating, I’ll definitely ask. But seriously, is there a fee for using that? It feels ridiculous that we have to check if we can deploy something after paying so much to use Azure. We had 25 VMs running just fine, and all of a sudden, at 8:30 AM today, they all hit capacity errors. It’s like, how is that acceptable from Microsoft?