Cannot create App Service Plan in UK South — "Total VMs: 0" quota error, Microsoft.Web registered

Sayan Dutta 75 Reputation points
2026-07-21T13:13:18.63+00:00

I have been unable to create an App Service Plan in UK South.

The deployment fails during preflight validation with the following error:

Code: SubscriptionIsOverQuotaForSku
Operation cannot be completed without additional quota.
Current Limit (Total VMs): 0
Current Usage: 0
Amount required for this deployment (Total VMs): 1
Minimum new limit required: 1

The Azure Quotas page for App Service in UK South currently shows:

Y1 VMs: 0 of 0
Total Regional VMs: 0 of 0

The same ARM template and Y1 configuration deployed successfully in other Azure subscriptions and regions (Australia East, Canada Central, South Africa North etc). Only this UK subscription is experiencing the quota validation failure.

I have few questions like:

  1. Do we need to request an increase for both Y1 VMs and Total Regional VMs, or is increasing the Y1 VM quota sufficient?
  2. What quota values should be requested to deploy one Azure Functions Y1 Consumption App Service Plan?
  3. Is it expected for a subscription to have a default Y1 and total regional App Service VM quota of zero in UK South?
  4. Will increasing these quotas create any additional cost, or will charges apply only after the Function App is deployed and used?
  5. After the quota is approved, can we simply rerun the same ARM template, or are any additional subscription or Microsoft.Web configuration changes required?
Azure Functions
Azure Functions

An Azure service that provides an event-driven serverless compute platform.


Answer accepted by question author

Rakesh Mishra 11,100 Reputation points Microsoft External Staff Moderator
2026-07-21T14:52:07.4+00:00

Hi @Sayan Dutta ,

Welcome to Microsoft Q&A portal. Thank you for posting your question here.

The SubscriptionIsOverQuotaForSku error you're hitting is the standard App Service regional quota check. Your subscription in UK South currently has 0 App Service worker VMs available for the Y1 (Consumption) SKU, so every Y1 plan deployment fails preflight with Current Limit (Total VMs): 0. The same ARM template works in Australia East / Canada Central / South Africa North because those subscriptions already have non-zero App Service capacity in those regions.

Answering your questions one by one:

1. Y1 VMs vs. Total Regional VMs — do you need to raise both?

Raise the Y1 VMs (per-SKU) quota first. When Azure approves a SKU-level App Service quota increase, the Total Regional VMs aggregate is normally bumped by the same amount automatically, so you usually don't need a separate request. If after approval you see the SKU counter go up but Total Regional VMs is still 0, reply on the same support case and ask for the regional aggregate to be raised as well.

2. What value should you request?

The error states the minimum is 1: Amount required for this deployment (Total VMs): 1 Minimum new limit required: 1

1 will unblock this single deployment. However, Y1 Consumption plans can scale out to 200 instances, so if you expect real traffic, request headroom now (e.g. 10, 50, or 200) to avoid raising another ticket later.

3. Is a default of 0 in UK South expected?

Yes, this is expected. Default App Service quotas depend on subscription age, offer type (PAYG, EA, CSP, MSDN), and prior usage in the region. UK South is currently under noticeable capacity pressure, so new or previously unused subscriptions are frequently created with 0 App Service capacity in this region until a quota request is filed and reviewed.

4. Does raising the quota cost anything?

No. Requesting or being granted an App Service quota increase is free quotas are a limit, not a reservation. You're billed only when the Function App on a Y1 Consumption plan actually executes, based on executions, execution time (GB-s), and memory used. If the plan sits idle, there is no charge.

5. After approval, can you just rerun the ARM template?

Yes. Once the support engineer confirms the new limit is applied (verify on the Quotas → App Service (Public Preview) blade for UK South), redeploy the same ARM / Bicep template with no changes. No additional Microsoft.Web re-registration or subscription-level settings are needed — you've already confirmed the resource provider is registered, which is the other common cause of this error.

How to file the request
  1. Azure portal → Quotas
  2. Select App Service (Public Preview) from the service list.
  3. Use the Region filter at the top → select UK South.
  4. Locate the Y1 VMs row → click the edit (pencil) icon → enter your New Limit (1 for a single plan, higher for headroom) → Submit.
  5. Wait for approval (typically minutes to a few hours).
  6. If it fails, Create Support Request button will appear. Click on it and fill the details to create a request.

Steps to create support request: recommended for UK South right now, since the self-service flow is often routed to manual review in capacity-constrained regions:

  1. Azure portal → Help + support → Create a support request.
  2. Issue type: Service and subscription limits (quotas)
  3. Quota type: Web App (Windows and Linux), this is the correct type for Function Consumption plans too.
  4. Provide:
    • Region: UK South
    • SKU: Y1 (Dynamic)
    • New limit: your desired number of worker VMs
  5. Paste the exact error message in the description.
Recommendation

Y1 Consumption is now the legacy hosting model for Azure Functions (Linux Consumption has already been retired). Microsoft's current recommendation for new Function Apps is the Flex Consumption (FC1) plan, and it has its own quota surface (often easier to approve in capacity-constrained regions), better cold-start / scale characteristics, and full VNet integration. If your workload allows, consider deploying on Flex Consumption in UK South (or UK West as a nearby alternative).

References

Please let me know if you have any other questions.

Was this answer helpful?

1 person found this answer helpful.

Answer accepted by question author

TP 161K Reputation points Volunteer Moderator
2026-07-21T13:37:30.2366667+00:00

Hi,

For UK South, request Y1 VMs quota by clicking on pencil icon. The quantity you request depends on how many instances you think your function may need to scale out. Total Regional VMs will increase automatically.

Assuming the automated mechanism approves your request you should have no issues deploying Y1 to UK South. You may re-run the same template.

Please click Accept Answer and upvote if the above was helpful.

Thanks.

-TP

Was this answer helpful?

1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
  1. AI answer

    2026-07-21T13:13:56.17+00:00

    For this error, the blocking quota is the App Service quota in the target region. The accepted Microsoft guidance for the same SubscriptionIsOverQuotaForSku / Total VMs: 0 scenario is to go to Quotas in the Azure portal, select App Service (Public Preview), filter to UK South, and request an increase for the specific App Service quota shown for the SKU being deployed. For App Service and Functions quota requests, the support flow also uses Quota type: Function or Web App (Windows and Linux) and asks for Region, App Service plan SKU, and New limit of worker VMs.

    Based on that:

    1. Y1 VMs vs Total Regional VMs Request the App Service quota increase for the specific SKU being deployed in UK South. In the quota/support flows, the request is made against the App Service/Function or Web App quota for the plan SKU and worker VMs. The context does not state that a separate manual request for both values is always required.
    2. Quota value to request for one Y1 deployment The deployment error states:
      • Current Limit (Total VMs): 0
      • Amount required for this deployment: 1
      • Minimum new limit required: 1
      So the minimum supported request to deploy one plan is 1.
    3. Is zero default quota expected? Yes, this can occur. The context states that default quotas depend on factors such as the age and type of the subscription and service usage. Microsoft Q&A examples for App Service also show subscriptions with 0 App Service quota in a region and recommend requesting a quota increase.
    4. Does increasing quota create cost? The context does not state that requesting or approving a quota increase itself creates charges. It does state that App Service plans define resource limits and that pricing applies to plans such as Dedicated/App Service plans at standard rates. No supported statement is available here that quota approval alone incurs cost.
    5. After approval, can the same ARM template be rerun? Yes. The accepted Microsoft guidance for this scenario is that once the quota request is approved, the deployment can be tried again. No additional Microsoft.Web registration change is indicated when Microsoft.Web is already registered.

    If the quota blade does not allow the request directly, use Support + Troubleshooting in the Azure portal:

    1. Search for quota limit.
    2. Select Service and subscription limits (quotas).
    3. Select Create a support request.
    4. Set What is your issue related to? = Azure services.
    5. Set Issue type = Service and subscription limits (quotas).
    6. Select the subscription.
    7. For App Service/Functions quota requests, provide Region, App Service plan SKU, and New limit of worker VMs.

    References:

    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.