Azure GPU quota increase rejected due to insufficient payment history on new Pay-As-You-Go subscription

Question

Azure GPU quota increase rejected due to insufficient payment history on new Pay-As-You-Go subscription

Amr Ezzat 20

Hi everyone,

I recently upgraded my Azure Free Trial subscription to Pay-As-You-Go because I want to deploy a GPU VM

I’m trying to deploy:

VM: Standard_NC4as_T4_v3
GPU: NVIDIA Tesla T4 16 GB
Region: East US
Required quota: 4 vCPUs
Quota family: Standard NCASv3_T4 Family vCPUs

The problem is that my quota is currently 0, so I cannot deploy the VM.

I submitted a quota increase request, but Microsoft Support rejected it with this message:

“Due to insufficient payment history, a previous bank decline, or an unpaid outstanding balance, Microsoft is currently unable to approve additional quota at this time.”

However, my billing account currently shows:

Amount due: $0.00
No payment needed
Pre-tax total: $0.00
I have no outstanding balance.
I have also added a new payment method that supports international online payments and set it as my primary payment method.

This is a new Azure subscription, so I understand that I may not have much payment history yet.

I’m wondering:

Is there any way to get GPU quota approved on a new Pay-As-You-Go subscription without having to build up payment history first?
Does Microsoft require a specific amount of successful payment history before approving GPU quota?
Is there another GPU VM series that a new subscription like mine may be eligible to use?
Has anyone experienced the same issue and found a way to get the quota approved?

I only need 4 vCPUs for one T4 VM, not a large GPU deployment.

Any advice would be greatly appreciated. Thanks!

0 comments

Answer accepted by question author

0 additional answers

Your answer

Answer 1

Hi Amr Ezzat & thx for join me at Q&A platform,

This is most likely an account risk/eligibility restriction, not a normal quota-capacity issue. quota value of 0 for Standard NCASv3_T4 Family vCPUs on a newly converted Pay-As-You-Go subscription can happen when GPU families are restricted until the subscription has enough billing and trust history. The rejection text is fairly explicit that Microsoft’s internal risk checks are blocking the increase. A $0.00 balance and a valid payment method don’t necessarily satisfy those checks.

There isn’t a published minimum number of successful payments or a documented spend threshold that guarantees GPU quota approval. The decision is made by Microsoft’s internal quota/risk systems, so repeatedly submitting the same request usually won’t help if the subscription is still considered too new. I also wouldn’t expect switching from NC4as_T4_v3 to another GPU family to reliably bypass this. New subscriptions can have zero quota across several GPU families, and some series have even tighter availability controls.

The practical options are to keep the subscription in good standing and build some billing history, or reply to the existing quota support case and ask for a manual review, explaining that you only need 4 vCPUs for a single T4 VM and that the payment method has been corrected. If Microsoft confirms the restriction is based on account history, there isn’t a customer-side setting that can override it.

rgds,

Alex