Discrepancy in Azure Function App Deployment Between Portal and PowerShell

Question

I encountered an issue while deploying a Function App in the East US region:

Issue with Azure Portal: Deployment failed with the error:

"The template deployment 'Microsoft.Web-FunctionApp-Portal-XXXXXXXX' is not valid according to the validation procedure. Code: ValidationForResourceFailed. This region has a quota of 0 instances for your subscription."

PowerShell Deployment: The same Function App deployment succeeded without any errors when using PowerShell. Both deployments used identical configurations, including:

• Runtime Stack: Java 11.0
  • Hosting Plan: Consumption (Dynamic SKU)
    • Region: East US
    Steps to Reproduce:

    1. Attempt to deploy a Function App in **East US** using the Azure Portal.
    
       1. Use the same settings to deploy the Function App using PowerShell (`New-AzFunctionApp`).
    
       **Expected Behavior**: The deployment should either succeed or fail consistently across both the Azure Portal and PowerShell.
    

---

Request:

Please investigate the following:

1. Why the Azure Portal fails the deployment with a quota error, but PowerShell succeeds?
2. Is this a bug in the Portal validation process, or is there a hidden quota difference in how these tools operate?

Awaiting response

Answer 1

@Tiwari, Jyoti Thanks for the update! I am able to reproduce the same at my end even i noticed that deploying from portal fails with below error

whereas I am able to deploy the same successfully using below PowerShell command

https://learn.microsoft.com/en-us/powershell/module/az.functions/new-azfunctionapp?view=azps-13.0.0&tryIt=true&source=docs#examples

as mentioned above it should be the same quota regardless of how it is deployed will check internally on this and will update you shortly.

Appreciate your patience on this topic!