We have zero limits on creating VMs with A100. We can't work! Support isn't helping.

Question

I have a new account, and I haven't used Azure before (I used Google Cloud in the Europe West region). I received $100,000 in startup credits from Microsoft for Startups. I can't use them because I can't create the instances I need, and I can't create storage in the region I need to migrate my datasets from Google Cloud. Support can’t help at all, saying that I’m a new account with no payment history. How am I supposed to build a payment history if I can’t create resources? It’s a dead end.

Answer 1

Hello @Andrei Ushakov

I understand how frustrating this is, especially when you've been granted Microsoft for Startups credits but can't provision the resources required for your workload.

Based on your description, there are actually two separate issues that may be affecting you:

• Subscription quotas – A new Azure subscription often starts with conservative vCPU quotas, particularly for GPU VM families such as A100 (NC A100 v4 / ND A100 v4). A quota of 0 prevents deployment even if capacity exists.
• Regional capacity – Even if your quota is increased, GPU SKUs can still be unavailable in a region if there is insufficient capacity at the time of deployment.

A few questions that will help determine which is blocking you:

• Which VM family are you trying to deploy (for example, NC A100 v4, ND A100 v4, or another SKU)?
• Which Azure region are you targeting?
• Is the deployment failing with a QuotaExceeded error, or does it indicate insufficient capacity?
• Have you submitted a quota increase request for the specific GPU VM family from Help + support > Quotas, and if so, what was the response?

If the quota request has already been denied because the subscription is new, and you have a Microsoft for Startups subscription with approved credits, I'd recommend that a Microsoft moderator help route this to the Azure Capacity/Quota team or the Microsoft for Startups support team. They can review whether your subscription qualifies for a quota exception or whether another region with available capacity should be recommended.

If you can share the exact VM SKU, Azure region, and the full deployment error message, we can help determine whether you're hitting a quota restriction, a regional capacity issue, or both.

Please "Accept the Answer" if this information helped you. This will help us and others in the community as well.