Unable to deploy Premium V4 Azure Service Plan

Hello @Konstantins Gusarovs

Thank you for reaching out Microsoft Q&A. This is related to quota request, will provide you detailed steps for the same.
The error you are encountering “Current Limit (PremiumV4 VMs): 0” indicates that your subscription has no available quota for Premium V4 App Service workers in the selected region, which prevents deployment.

Azure enforces service quotas per subscription and per region.

• For Azure App Service, each pricing tier/SKU uses dedicated VM instances, and deployment requires available quota for that specific SKU.
• When the limit for a SKU (such as PremiumV4) is 0, deployment is blocked until the quota is increased.

Additionally:

• Quota is tracked per App Service VM size (SKU), meaning each size (e.g., P0v4, P1v4) is treated independently.
• Quotas are also regional, so availability in one region does not apply to others.

Regarding Single vs Multiple SKU Requests

• Each App Service VM size is represented as a separate SKU, and quota is managed individually per SKU.
• You cannot request quota for multiple SKUs as a single combined SKU entry.
• You need to request quota for each SKU (e.g., P0v4 and P1v4) separately, even if submitted within the same support case description.

Resolution:

1. Submit a quota increase request for PremiumV4 VMs in the required region.
2. Ensure you specify the required capacity for each SKU you want to test (for example, at least 1 instance).
3. After the quota is approved, retry the deployment.

Reference:
https://learn.microsoft.com/en-us/azure/app-service/app-service-configure-premium-v4-tier
https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits
https://techcommunity.microsoft.com/blog/appsonazureblog/announcing-the-public-preview-of-the-new-app-service-quota-self-service-experien/4450415

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

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

Hi! Unfortunately this is not something I can - do. As you can see in my original post I already have quotas on a subscription. When I try to request change to 1 I see the following:

So in the end I have available VMs but still am unable to create one.

Regards,

Konstantins

Hello @Konstantins Gusarovs

Thank you for sharing the screenshot, that’s very helpful. I can see what’s happening here.

The key point is that the quota you’re trying to modify (“P0v4 VMs: 0 of 30”) is not the same quota that is blocking your deployment.- The error you received earlier (“Current Limit (PremiumV4 VMs): 0”) refers to a different quota entry than the one shown in your screenshot.

• Azure quotas are defined per resource type and per SKU, and each quota represents a specific capacity allocation that must be available before deployment can proceed.

Recomendations:
Since the portal is not allowing you to set this quota directly (because it is already higher than the value you entered), the correct approach is:

Submit a support request to increase the correct quota entry

1. Go to Help + support > Create a support request
2. Select:
   • Issue type: Service and subscription limits (quotas)
     • Quota type: Web App (Windows/Linux)
3. In the description, explicitly request:
   • Increase Premium V4 App Service worker quota
   • For your region (e.g., North Europe)
   • For the required SKUs (P0v4 / P1v4)

This ensures the request is routed to the correct quota backend.

Reference:
https://learn.microsoft.com/en-us/azure/quotas/quotas-overview
https://learn.microsoft.com/en-us/azure/quotas/quickstart-increase-quota-portal
https://learn.microsoft.com/en-us/azure/app-service/app-service-configure-premium-v4-tier

Hello @Konstantins Gusarovs

Please could you let us know if you had a chance to look into our associate's response. Please feel free to reach out to us in case of any queries.

Hi!

I am currently waiting for support ticket resolution, so once I have some answers I will be able to comment more.

Regards,
Konstantins