Share via

Quota Increase issues

Neil Earlam 20 Reputation points
2026-05-01T21:55:55.2366667+00:00

I'm trying to deploy an app service plan to UK South. When I do the error I get says I have 0 quotas for provisioning.

I've went to the Quota's blade and the Request Quota bit is greyed out and a banner error says about registering Service Providers. When I go to Service Providers for Web it says its registered. I've click re-register and still getting the banner alert saying I need to register a provider.

I have tried raising a support ticket but when I get to stage 3 and fill out Request Details if I select Resource Manager as deployment model and then select UK South and Regional vCpus then fill in the rest of the form I get validation errors saying that Request Details is required. On Request Details if I change the Deployment Model to Classic the Location dropdown doesn't populate at all and the spinner just keeps spinning.This is getting a bit frustrating as I've tried everything on the Manage Quotas link and asked CoPilot for help as well which just directs me back into the manage quotas stuff. Everything I've tried (and followed on this) is either greyed out or saying validation errors.

Any help would be great thanks

Azure App Service
Azure App Service

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

Answer accepted by question author

  1. Golla Venkata Pavani 4,095 Reputation points Microsoft External Staff Moderator
    2026-05-02T01:25:08.8033333+00:00

    Hi @Neil Earlam

    Thank you for reaching us regarding the issue that you’re encountering is due to insufficient regional quota (vCPU quota = 0) in UK South, which blocks the deployment of App Service Plans. In Azure, quotas are enforced per subscription and per region, and deployments fail if the required regional quota is not available.

    Recommended Resolution Steps:

    1. Verify Resource Provider Registration
      Go to: Subscription → Resource Providers Ensure the following providers are Registered:
    • Microsoft.Web
    • Microsoft.Compute

    If already registered, allow time for propagation and refresh the portal.
    2. Request Regional vCPU Quota Increase (
    Follow the documented steps:

    • Go to: Subscriptions → Usage + quotas → Quotas
    • Select Compute
    • Filter by Region = UK South
    • Select Total Regional vCPUs
    • Click New quota request
    • User's image

    Quota limits are region-specific; increasing quota in one region does not affect others.
    New subscriptions may have low or zero default quotas, especially in certain regions.

    Reference:
    https://learn.microsoft.com/en-us/azure/quotas/per-vm-quota-requests
    https://docs.azure.cn/en-us/azure-resource-manager/templates/error-register-resource-provider

    Kindly let us know if the above helps or you need further assistance on this issue.

    Please "accept" if the information helped you. This will help us and others in the community as well.

    1 person found this answer helpful.
    0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Q&A Assist
    2026-05-01T21:56:14.0633333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The quota and support experiences are failing, so the deployment must be unblocked by focusing on two areas: fixing quota/provider issues and using alternative quota-request paths that don’t rely on the broken blade.

    1. Verify and request the correct quota type and region
    • App Service plans consume regional vCPU quota in the target region (UK South). If the quota is 0, deployments fail with insufficient quota.
    • Quotas are per region, not per subscription. For example, if 30 vCPUs are needed in UK South, the quota request must explicitly target UK South, not just “any region”.
    • The supported path is to request a quota increase for the region where deployment is needed:
      1. Sign in to the Azure portal.
      2. Go to Subscriptions → select the affected subscription → Usage + quotas.
      3. Select Request increase.
      4. Choose the quota type that corresponds to compute/App Service (regional vCPUs in UK South) and complete the form.
      If the inline quota limit edit is rejected, the portal will show a link to open a support request; use that link to create a support ticket for the quota increase. References: regional nature of quotas and the subscription → Usage + quotas → Request increase flow are described in the quota error resolution guidance.
    1. Use the Quotas blade correctly and fall back to support when inline adjustment fails
    • From the Quotas service in the portal:
      1. Search for Quotas in the portal.
      2. Select a provider such as Compute.
      3. On My quotas, select the quota to increase and ensure Adjustable is Yes.
      4. Select New Quota Request → Enter a new limit.
      5. Enter the new limit and submit.
    • If the request cannot be fulfilled, the portal will show a link to create a support request. Use that link instead of manually navigating to support; it pre-populates the correct quota type and region and avoids some validation issues.
    1. Work around broken quota UI by starting from Support + troubleshooting If the Quotas blade and the standard support flow are misbehaving, use the generic support entry point and explicitly choose the quota path:
    2. In the Azure portal, select the Support + troubleshooting (question mark) icon.
    3. In How can we help you?, enter quota limit and select Go.
    4. In Current selection, choose Service and subscription limits (quotas) and select Next.
    5. Under Service and subscription limits (quotas), select Create a support request.
    6. On the Problem description tab:
      • What is your issue related to?: Azure services
      • Issue type: Service and subscription limits (quotas)
      • Subscription: the affected subscription
      • Quota type: select the relevant compute quota (for App Service, the regional vCPU/compute quota used by the plan).
    7. On Additional details, use Enter details to choose:
      • Region: UK South
      • Quota type: the specific quota to increase
      • New total limit: the desired vCPU limit
      • Add any additional information (e.g., that the Quotas blade and standard support flow are failing validation).
    8. Complete Advanced diagnostic information, Support method, and Contact info, then review and submit.

    This path bypasses some of the validation issues seen when starting from other blades and is the documented alternative for quota increases.

    1. Handle Quota API / provider registration errors
    • If the Quota API or portal surfaces errors like ContactSupport, QuotaNotAvailableForResource, ResourceNotAvailableForSubscription, or UnableToIncreaseQuota, the documented resolution is to open a Service and subscription limits (quotas) support request in the portal or via the Azure Support REST API.
    • If the portal continues to insist that a provider must be registered even though it shows as registered, include that symptom in the support request description so support can correct subscription-level flags or provider registration state.
    1. If quota requests keep failing
    • If inline quota changes and automated requests fail or are partially fulfilled, the guidance is to:
      • Use the We were unable to adjust your quota notification (if shown) and select Generate a support ticket from the Quotas blade, or
      • Open a new support request and choose Service and subscription limits (quotas) as the issue type, explicitly describing that the quota UI and validation are blocking deployment.

    Once the regional vCPU quota for UK South is successfully increased and any provider-registration issues are resolved by support, the App Service plan deployment should succeed.

    References:

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.