App Service P1v3 creation fails with "Current Limit: 0" but Quota API shows limit of 30

Bansal Patel 0 Reputation points
2026-11-15T05:27:21.2466667+00:00

Hi,

I'm trying to create a Windows Web App on a new P1v3 App Service plan (1 instance, zone redundancy disabled) in Central US. The creation fails with this error:

"Operation cannot be completed without additional quota.

Current Limit (P1v3 App Service instances): 0

Current Usage: 0

Amount required for this deployment (P1v3 App Service instances): 1

(Minimum) New Limit that you should request to enable this deployment: 1."

Note that the "Location:" field in the error is empty.

However, both the Azure portal (Subscription > Usage + quotas) and the Microsoft.Quota API show quota available for the same subscription and region:

az quota show --resource-name P1v3 --scope "/subscriptions/<subscription-id>/providers/Microsoft.Web/locations/centralus"

Result:

  • P1v3: limit 30, usage 0
  • P1v3_AZ (Zone Redundant): limit 30
  • Total Regional VMs (*): limit 30

The subscription is provisioned through a CSP partner.

My questions:

  1. Why would the enforced App Service limit (0) differ from the value returned by the Quota API and shown in the portal (30)?
  2. Is there a separate backend or regional restriction for App Service (for example, region access restrictions for new subscriptions in capacity-constrained regions) that isn't shown in the Quota API?
  3. Is there any API or CLI command that returns the limit actually enforced at deployment time?

Thanks!

Azure App Service
Azure App Service

Azure App Service is a service used to create and deploy scalable, mission-critical web apps.

0 comments No comments

1 answer

Sort by: Oldest
  1. AI answer

    2026-11-15T05:28:29.78+00:00

    Because the App Service quota blade already reports P1v3 = 30 and Total Regional VMs = 30, do not submit another increase to 1; open an App Service quota support request for Microsoft to reconcile the quota state used by the Microsoft.Web deployment preflight.

    What the discrepancy means

    App Service evaluates quota by subscription, region, deployment type, and SKU, and requires sufficient capacity under both the individual SKU counter and Total Regional VMs. Normally, the lower available counter determines admission. Your reported values satisfy both documented checks, so the deployment result conflicts with the exposed quota state rather than showing an ordinary exhausted quota. ^1^

    The empty Location field strengthens the need to inspect the complete provider error, but it does not establish a particular cause.

    The error also does not match the documented regional-capacity errors, which use messages such as:

    • No available instances to satisfy this request
    • Not enough available reserved instance servers to satisfy this request

    Current Limit: 0 or SubscriptionIsOverQuotaForSku is classified as quota admission instead. Quota and physical regional capacity are separate controls. ^1^

    Nothing in the documented behavior establishes that CSP subscriptions have a separate restriction. Do not attribute the discrepancy to CSP until Microsoft or the CSP partner confirms an offer-level restriction on this subscription.

    Escalate the mismatched state

    In the Azure portal:

    1. Go to Help + support → Create a support request.
    2. Select:
      • Issue type: Service and subscription limits (quotas)
      • Quota type: Function or Web App (Windows and Linux)
      • Region: Central US
      • SKU: P1v3
    3. State that this is a quota-state mismatch, not a normal increase:
      • Portal/App Service Quotas: P1v3 30, usage 0
      • Microsoft.Quota result: P1v3 30, usage 0
      • Total Regional VMs: 30
      • Deployment preflight: P1v3 Current Limit 0
      • Deployment type: non-zone-redundant
    4. Include:
      • Complete deployment error JSON
      • Timestamp and correlation/tracking ID
      • Subscription and resource-group details
      • The CLI output showing the 30-instance limit
      • A screenshot/export from Quotas → App Service (Public Preview)
      • Confirmation that the subscription is supplied through CSP

    Microsoft’s guidance says to open a support request when a valid self-service quota request cannot be fulfilled or the portal directs you to support. The same path is appropriate when the exposed quota and provider admission state disagree. ^1^

    If direct Azure support creation is unavailable for the CSP subscription, provide the same evidence to the CSP partner and ask them to escalate an App Service/Microsoft.Web regional quota stamp mismatch.

    Is there an API for the deployment-enforced limit?

    No public App Service API or CLI command is documented as returning a second, authoritative “effective deployment limit” behind the value shown in the App Service quota experience.

    az quota show only shows the quota resource returned for the specified resource provider and scope. ^2^ The general Azure Quota Service documentation lists supported services but does not document Microsoft.Web as an authoritative deployment-admission endpoint. ^3^

    The closest public deployment-time test is resource-provider preflight validation. For a Bicep or ARM deployment:

    az deployment group validate \
      --resource-group <resource-group> \
      --template-file main.bicep
    

    This invokes the relevant resource provider without creating resources. A preflight failure appears in the Activity Log rather than deployment history because deployment never starts. ^4^

    However, validation returns the provider’s admission decision and error details; it is not a separate quota-query API. Your failed portal Review + create operation has effectively already exercised this validation path.

    Temporary workaround

    If deployment is urgent, test P1v3 in another acceptable region where the subscription’s App Service quota is nonzero. Microsoft documents another region or an additional App Service quota request as the available responses when a subscription has zero regional quota. ^5^


    References

    1. Troubleshoot non-zone-redundant quota requests for Azure App Service ...
    2. az quota show
    3. Azure Quota Service API
    4. Preflight: Server validation before deployment
    5. Frequently asked questions (FAQ) - Creating or deleting resources in Azure App Service
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.