Blog Post

Apps on Azure Blog
5 MIN READ

Announcing the Public Preview of the New App Service Quota Self-Service Experience

jordanselig's avatar
jordanselig
Icon for Microsoft rankMicrosoft
Sep 04, 2025

We’re excited to announce the public preview of the new App Service quota self-service experience, designed to give you more visibility, control, and flexibility when managing your App Service resources in Azure.

Update 10/30/2025: The App Service Quota Self-Service experience is back online after a short period where we were incorporating your feedback and making needed updates. As this is public preview, ...
Updated Oct 30, 2025
Version 6.0
azure app service
web apps
jg_ca's avatar
jg_ca
Copper Contributor
Jan 02, 2026

Azure App Services & Azure Functions now rendered unusable due to this quota implementation. Account is restricted to 0 quota for any region/ vm type, and requests for any quota is rejected... Needing to raise a Support Case to enable 1 F1 in North Central US is a joke - especially because F1 is so constrained to begin with... What's going on here?

 

Had to confirm my account wasn't in the rears and potentially some late invoice blocking my subscription from raising quota, but not the case as my subscription is in good standing. Fix this please! 

Steve_Henry_MSFT's avatar
Steve_Henry_MSFT
Icon for Microsoft rankMicrosoft
Jan 16, 2026

jg_ca​ sorry to hear about your panic re: account standing! Makes sense that you'd be worried by these changes. Taking your comments in order:

  1. Account is restricted to 0 quota for any region and VM type (SKU)? I take this to mean that you see individual quotas for every SKU in every region, which should not be the case based on our current restrictions.
  2. For example, did you try deploying your F1 in West Central US? As of today, I don't anticipate quota-related restrictions that would have prevented you from doing so.
  3. I want to understand more about the friction around filing a support case. In the past implementation, you would have had to file a Technical support request if able, whereas now you're able to do so automatically and with mostly prepopulated fields via the Quotas blade. Other than having to track manual response to your quota request, was there something about this experience that you wanted to work differently? While we cannot avoid having quota to begin with in some regions, the process for requesting increases should be much simpler than before. 
  • GraemeMeyer's avatar
    GraemeMeyer
    Copper Contributor
    Jan 17, 2026

    Steve_Henry_MSFT​ I am also seeing quotas of 0 for every single sku in every single region, and self-service request fails which means I cannot deploy ANYTHING. I have to assume it's a bug, but since my support tickets are locked to sev c, I cannot get any timeline answer or resolution to this? 

    • Steve_Henry_MSFT's avatar
      Steve_Henry_MSFT
      Icon for Microsoft rankMicrosoft
      Jan 20, 2026

      GraemeMeyer​ that doesn't sound like the intended experience. You're seeing individual SKUs (e.g., B1, S2, P3v2) with 0 of 0 quota in regions like West Central US and West US 2? All capacity requests are sev C by default, but that doesn't mean you should get no response. How long have you been waiting for manual increase on quota with no update?