Share via

Can't create an appservice due to quota limitations , but my quotas seem to be unused

EAS 0 Reputation points
2025-10-24T20:56:50.89+00:00

I am trying to deploy a basic web app. When I try to create an appservice plan whether via az cli or via portal I am getting an error saying that I do not have enough quota:

az appservice plan create --name asp-receipt-webapp-dev --resource-group ReceiptAnalyzerRG --location eastus --sku F1

Operation cannot be completed without additional quota.

Additional details - Location:

Current Limit (Free VMs): 0

Current Usage: 0

Amount required for this deployment (Free VMs): 1

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

Note that if you experience multiple scaling operations failing (in addition to this one) and need to accommodate the aggregate quota requirements of these operations, you will need to request a higher quota limit than the one currently displayed.

When I try to create the app service via portal i get:

{

"code": "InvalidTemplateDeployment",

"message": "The template deployment 'Microsoft.Web-ASP-Portal-21e8444e-8bd8' is not valid according to the validation procedure. The tracking id is '686889fa-ac7b-4786-aae4-81902f43383a'. See inner errors for details.",

"details": [

{

  "code": "ValidationForResourceFailed",

  "message": "Validation failed for a resource. Check 'Error.Details[0]' for more information.",

  "details": [

    {

      "code": "SubscriptionIsOverQuotaForSku",

      "message": "Operation cannot be completed without additional quota. \r\nAdditional details - Location: East US \r\nCurrent Limit (Standard VMs): 0 \r\nCurrent Usage: 0\r\nAmount required for this deployment (Standard VMs): 1 \r\n(Minimum) New Limit that you should request to enable this deployment: 1. \r\nNote that if you experience multiple scaling operations failing (in addition to this one) and need to accommodate the aggregate quota requirements of these operations, you will need to request a higher quota limit than the one currently displayed."

    }

  ]

}

]

}

but I do not have any other web apps or any apps (beside an azure function). Furthermore, when I try to look up my quotas in the portal I see:

User's image

so, it looks like I do have two "classic" quotas unused

What am I doing wrong?

Azure App Service
Azure App Service

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

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2025-10-25T01:29:57.2266667+00:00

    Hi @EAS ,

    Thank you for submitting your question on Microsoft Q&A.

    You’re not doing anything wrong the problem is that you’re looking at the wrong quota provider in the portal. What’s really happening

    • The error (SubscriptionIsOverQuotaForSku … Current Limit (Free/Standard VMs): 0) is coming from App Service (Microsoft.Web) regional quotas. These are not the same as the “Compute (classic)” quotas you’re seeing in your screenshot (those are for legacy Cloud Services and classic cores). App Service keeps its own per‑region, per‑SKU “worker” quotas (Free/Shared, Small/Medium/Large, PremiumV3, etc.). If your subscription’s quota for a given region/SKU bucket is 0, the platform returns SubscriptionIsOverQuotaForSku.

    On new or certain subscription types, these Microsoft.Web quotas can default to 0 until you request an increase, or the region may be temporarily constrained—both produce the exact error you’re seeing. In such cases, trying another region often works immediately.How to see the correct quotas

    1. In the Azure portal, go to Quotas.
    2. At the top, change Provider to Microsoft.Web (not Compute/classic).
    3. Filter Region to East US.
    4. Expand the App Service group; you’ll see entries like Free VMs, Shared VMs, Small/Medium/Large worker VMs, PremiumV3 VMs, etc., with Current usage and Limit. For non‑Compute providers, the blade shows a Request increase action that opens a support request for the selected quota.

    Ways to fix this issue

    A) Request a quota increase for Microsoft.Web

    • From Quotas -> Provider: Microsoft.Web -> (Your quota item) -> Request increase, submit new limit = 1 in East US for the SKU you need (e.g., Free VMs for F1 or Standard/Small workers for S1/B1 style SKUs). Most requests are auto‑approved within minutes; otherwise support follows up.
    • Alternatively (same result), open Help + support -> New support request -> Issue type: Service and subscription limits (quotas) -> Quota type: Web App (Windows and Linux), then specify Region and App Service plan SKU and request the new VM limit.

    B) Try another region

    A zero limit can also reflect capacity constraints for that SKU in that region. Switching regions (for example, East US 2, Central US, or another nearby region) often succeeds immediately. Many users report success by simply changing the region when they hit …quota of 0 instances

    Double‑check the basics

    • Make sure you’re using the intended subscription
    az account show -o table
az account set --subscription "<SUBSCRIPTION NAME OR ID>"

    Azure CLI commonly surfaces the same quota error if you create resources in the wrong subscription by accident. This is a general hygiene check; the root cause here is still Microsoft.Web quotas.

    Why the “Compute (classic)” blade misled you

    The “Cores (Classic)” and “Cloud Services (Classic)” quotas you saw are for the older classic compute stack and don’t govern App Service. App Service plans are their own construct (shared or dedicated workers) under the Microsoft.Web provider, with separate limits and behaviors.

    Reference:

    https://learn.microsoft.com/en-us/azure/app-service/overview-hosting-plans

    https://learn.microsoft.com/en-us/azure/quotas/view-quotas

    https://learn.microsoft.com/en-us/azure/quotas/quickstart-increase-quota-portal

    https://learn.microsoft.com/en-us/rest/api/appservice/get-usages-in-location/list?view=rest-appservice-2024-11-01&tabs=HTTP

    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.