New Pay-As-You-Go subscription blocked: App Service SubscriptionIsOverQuotaForSku + PostgreSQL LocationIsOfferRestricted in East US

Question

New Pay-As-You-Go subscription blocked: App Service SubscriptionIsOverQuotaForSku + PostgreSQL LocationIsOfferRestricted in East US

Jefry Ureña Cordero 0

Hello,

I recently upgraded my Azure subscription from Free Trial to Pay-As-You-Go

(upgraded on 2026-06-25) and I'm unable to deploy two resources in East US

despite having available quota for vCPUs.

Subscription ID: d859c718-c562-4eb0-a1e4-2e611754c270

Region: East US (eastus)

Error 1 — Azure App Service Consumption Plan

When deploying an Azure Function App (Consumption plan, Linux, .NET 10

isolated worker) via Bicep, I get:

SubscriptionIsOverQuotaForSku: Operation cannot be completed without

additional quota.

Current Limit (Total VMs): 0

Current Usage: 0

Amount required: 1

The Compute quota page shows "Total Regional vCPUs: 0 of 10" (healthy),

but the Microsoft.Web internal "Total VMs" quota is stuck at 0. This

appears to be the new-subscription anti-fraud hold, not a Compute quota

issue.

Error 2 — Azure PostgreSQL Flexible Server

When deploying a PostgreSQL Flexible Server (B1ms burstable, PostgreSQL 17)

via Bicep in the same region:

LocationIsOfferRestricted: Subscriptions are restricted from provisioning

in location 'eastus'.

What I've tried

Verified Microsoft.Web and Microsoft.DBforPostgreSQL resource providers are registered ✅
Confirmed Compute vCPU quotas are healthy (0 of 10 used) ✅
Bicep template validates clean (az bicep build passes) ✅
Waited 3+ days since upgrade — hold has not auto-cleared ✅

Request

Could a Microsoft engineer please:

Remove the Microsoft.Web/serverFarms quota hold (Total VMs = 0) for East US on this subscription
Enable Azure PostgreSQL Flexible Server provisioning in East US for this subscription

This is a personal development project, no production workload.

Thank you.

SAI JAGADEESH KUDIPUDI 3,550 Reputation points Microsoft External Staff Moderator

2026-07-01T07:15:45.6666667+00:00
Hi @Jefry Ureña Cordero ,

Many popular regions have limited capacity. When there is limited capacity in the region, it restricts which subscriptions are allowed to deploy MySQL Flexible Server. The error will usually look similar to the one below:

ProvisionNotSupportedForRegion Provisioning in requested region is not supported. Your subscription might not have access to create a server in the selected region.

You should be able to deploy in a different region (for example, West US 3) or follow the instructions below to request access to your preferred region.

Please carefully follow my instructions below to create a new Service and subscription limits (quotas) request to allow access to the Azure Database for MySQL Flexible Server deployment in your preferred region.

Navigate to this link to start the process:

https://portal.azure.com/#create/Microsoft.Support

Enter quota in the box and click Go.

Select Others / Service and subscription limits (quotas) and click Next.

Click the Create a support request button as shown.

Select Issue type: Service and subscription limits (quotas), Subscription, Quota type: Azure Database for MySQL Flexible Server, and click Next.

6. Agora você deve estar na aba Additional details. Clique em Enter details.

7. Selecione Region access ou Region access with zonal dependency, selecione a Location que você precisa, informe o número de cores necessários e clique em Save and continue.

Finish filling out the Additional details tab, click Next, review, and click Create. You should receive an automated email within a few minutes.

NOTE: It is possible that your request may be denied due to capacity limit or other reason, but at least you tried.

1 answer

Your answer

SAI JAGADEESH KUDIPUDI 3,550 Reputation points Microsoft External Staff Moderator

2026-07-01T07:15:45.6666667+00:00

Hi @Jefry Ureña Cordero ,

Many popular regions have limited capacity. When there is limited capacity in the region, it restricts which subscriptions are allowed to deploy MySQL Flexible Server. The error will usually look similar to the one below:

ProvisionNotSupportedForRegion Provisioning in requested region is not supported. Your subscription might not have access to create a server in the selected region.

You should be able to deploy in a different region (for example, West US 3) or follow the instructions below to request access to your preferred region.

Please carefully follow my instructions below to create a new Service and subscription limits (quotas) request to allow access to the Azure Database for MySQL Flexible Server deployment in your preferred region.

Navigate to this link to start the process:

https://portal.azure.com/#create/Microsoft.Support

Enter quota in the box and click Go.

Select Others / Service and subscription limits (quotas) and click Next.

Click the Create a support request button as shown.

Select Issue type: Service and subscription limits (quotas), Subscription, Quota type: Azure Database for MySQL Flexible Server, and click Next.

6. Agora você deve estar na aba Additional details. Clique em Enter details.

7. Selecione Region access ou Region access with zonal dependency, selecione a Location que você precisa, informe o número de cores necessários e clique em Save and continue.

Finish filling out the Additional details tab, click Next, review, and click Create. You should receive an automated email within a few minutes.

NOTE: It is possible that your request may be denied due to capacity limit or other reason, but at least you tried.

Answer 1

hi & thx for sharing urs issue here at Q&A portal,

I guess new-subscription restriction, not a normal vCPU quota issue. SubscriptionIsOverQuotaForSku with Total VMs: 0 for App Service/Functions usually means the Microsoft.Web quota/eligibility backend hasn’t opened that SKU for the subscription yet. The Compute vCPU quota page won’t show that, bc App Service has its own internal capacity/quota checks. Same idea for PostgreSQL: LocationIsOfferRestricted means that offer/location is blocked for this subscription. If it was just PostgreSQL capacity, u’d usually see a different capacity/sku error.

Since this was upgraded from Free Trial to Pay-As-You-Go only a few days ago, it may be fraud/risk gating or regional offer eligibility still stuck. Waiting sometimes clears it, but 3+ days is already enough to ask Billing/Subscription support to review it.

https://learn.microsoft.com/en-us/azure/azure-resource-manager/troubleshooting/error-resource-quota

https://azure.microsoft.com/en-us/support/create-ticket/

Try open a billing/subscription support case and say the Pay-As-You-Go subscription is active but still blocked from provisioning Microsoft.Web serverFarms and PostgreSQL Flexible Server in East US. Include the subscription ID, region, exact errors, UTC deployment times, and note that Compute vCPU quota is healthy but Microsoft.Web Total VMs is 0. And try another region like East US 2, Central US, or West US 3. But if this is a subscription-level hold, support needs to clear it.

rgds,

Alex

&

If my answer was helpful pls mark it and additional thx if u follow me at Q&A portal

and at my blog https://ctrlaltdel.blog/