An Azure service that provides a general-purpose, serverless container platform.
Hi @sw Thank you for reaching out to Microsoft Q&A.
It looks like your subscription-level quota for General Purpose Cores is in place (201 cores in Japan East), but your Container Apps environment itself still has a zero-core limit for the D4 workload profile. That’s why you’re hitting:
WorkloadProfileMaximumCoresConstraint: The maximum cores for workload profile d4 cannot be more than 0.
Quotas in Azure Container Apps are scoped in four layers subscription, region, environment, and application and the D4 profile cores limit is an environment-scoped quota. Environment-scoped quotas don’t show up on the generic Quota blade in the portal. Here’s how to diagnose and fix:
View your environment quotas via the CLI
az containerapp env list-usages \
--resource-group xxx \
--name xx
Look for the entry with name “d4” or “WorkloadProfileMaximumCoresConstraint” and you’ll see currentValue: 0.
Request an increase on that environment-scoped quota • In the Azure portal, open Help + support → New support request • Under Issue type, pick Quota • Service: Azure Container Apps, Scope: Environment • Specify your subscription, resource group, environment name, region, and request the number of cores you need for the D4 profile (for example, 16) • Fill in a quick justification (e.g. “Need D4 profile cores to deploy internal apps at scale”) and submit
Because environment-scoped Container Apps quotas are considered manual requests, this will automatically generate a support ticket and usually completes in a few days.
After approval, re-run your Terraform apply and the ACAE will create successfully.
Hope that helps!