Azure Virtual Machine Deployment: Subscription Quota Limit — Request for Increase

The errors indicate two different issues: the P2mv4/P3mv4 App Service deployment is related to the App Service SKU/Regional VM quota, while Standard_B4ms with SkuNotAvailable/capacity restrictions indicates VM SKU availability or regional capacity rather than simply a vCPU quota issue. For the App Service Plan, first sign in to the Azure Portal, search for Quotas, select App Service (Public Preview), select the affected subscription, and filter the Region to East US. Locate the P2mv4/P3mv4 SKU and review its current usage and limit. If the SKU quota is insufficient or is 0, select the quota entry/pencil icon and submit a quota increase for the required total number of instances. The Total Regional VMs value should not be requested directly; it is updated through an eligible individual SKU quota increase. After the new limit is approved and visible in the Quotas page, retry the App Service deployment. Microsoft documents this process here: App Service quota troubleshooting For the Standard_B4ms VM, go to Azure Portal → Virtual machines → Create → Azure virtual machine, select the target subscription and region, and under Size select See all sizes. Search for Standard_B4ms; if it is unavailable or marked as restricted, the SKU is not currently available for that subscription/region/zone. You can also check Subscription → Usage + quotas to confirm that the applicable regional and VM-family vCPU quota is sufficient. Microsoft notes that SkuNotAvailable can occur when a VM SKU is unavailable for a location/zone or subscription, and recommends using another available size/region or submitting a SKU request to Azure Support if the required SKU is not available. SKU not available troubleshooting Since the same issue occurs in both East US and East US 2, I recommend checking the subscription-specific restrictions and quotas first rather than repeatedly retrying the deployment. If the P2mv4/P3mv4 quota request cannot be fulfilled, or Standard_B4ms remains unavailable in both regions, open an Azure Support request and include the subscription ID, resource group, deployment name/ID, region, exact SKU, UTC timestamp, and complete error/correlation ID. This will allow Microsoft to determine whether the remaining issue is subscription eligibility, regional capacity, or SKU restriction.

Since the same issue occurs in both East US and East US 2, this is most likely due to regional capacity constraints or SKU availability limitations, although quota verification should also be completed to rule out subscription-level restrictions.

Try this as a recommended action:

• Verify subscription quotas for P2mv4/P3mv4 App Service Plans and Standard_B4ms VM SKU.

Check SKU availability in East US and East US 2, as the SkuNotAvailable error usually indicates regional capacity constraints.

Raise an Azure Support Request to validate quota/capacity availability and obtain alternative region recommendations.

If urgent, consider deploying in another region or using an alternative SKU with similar specifications.