Share via

I cannot provision Azure Container Apps in West Europe

Nikolaj Larsen 0 Reputation points
2026-03-11T10:24:01.32+00:00

I'm attempting to provision a Container App, with a Container App Environment connected to an existing Virtual Network, in West Europe.

I keep getting this error:

{
  "code": "ManagedEnvironmentProvisioningError",
  "message": "Creating a free tier cluster is unavailable at this time in region westeurope. To create a new cluster, we recommend using an alternate region, or create a paid tier cluster. For a list of all the Azure regions, visit https://aka.ms/aks/regions. For more details on this error, visit https://aka.ms/akscapacityheavyusage.\r\nStatus: 400 (Bad Request)\r\nErrorCode: AKSCapacityHeavyUsage\r\n\r\nContent:\r\n{\n  \"code\": \"AKSCapacityHeavyUsage\",\n  \"details\": null,\n  \"message\": \"Creating a free tier cluster is unavailable at this time in region westeurope. To create a new cluster, we recommend using an alternate region, or create a paid tier cluster. For a list of all the Azure regions, visit https://aka.ms/aks/regions. For more details on this error, visit https://aka.ms/akscapacityheavyusage.\",\n  \"subcode\": \"\"\n }\r\n\r\nHeaders:\r\nCache-Control: no-cache\r\nPragma: no-cache\r\nx-ms-operation-identifier: REDACTED\r\nx-ms-correlation-request-id: REDACTED\r\nx-ms-request-id: REDACTED\r\nStrict-Transport-Security: REDACTED\r\nx-ms-throttling-version: REDACTED\r\nx-ms-ratelimit-remaining-subscription-writes: REDACTED\r\nx-ms-routing-request-id: REDACTED\r\nX-Content-Type-Options: REDACTED\r\nX-Cache: REDACTED\r\nX-MSEdge-Ref: REDACTED\r\nDate: REDACTED\r\nContent-Length: 412\r\nContent-Type: application/json\r\nExpires: -1\r\n"
}

The error message claims that I cannot create a Free Tier cluster, but I'm not attempting to create a Free Tier cluster. I've added a Dedicated workprofile to the CAE, and configured the Container App to be deployed to that workprofile. But the Azure Portal UI doesn't allow me to delete the default Consumption workprofile. So I'm unable to provision a cluster, since the non-removable Consumption workprofile, causes the cluster to be considered "Free Tier". This is simply just plain dumb.

It does create the Container App Environment though - but in a failed state. So for every time I try, I have to manually delete the failed resources. And deletion - of the failed resource - takes anywhere from 15-50 minutes!

I would use a different region, if it weren't for our usage of a SaaS database (Tiger Cloud), that only supports provisioning in West Europe. So if I were to deploy the Container Apps in a different region, we'd increase the latency between the database and the application, and incur an addition bandwidth cost for the inter-region data transfer.

This is really unprofessional Microsoft.

Azure Container Apps
Azure Container Apps

An Azure service that provides a general-purpose, serverless container platform.

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Rakesh Mishra 7,065 Reputation points Microsoft External Staff Moderator
    2026-03-13T14:51:24.5+00:00

    Hi Nikolaj,

    Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

    Please find the response below and let me know if it works and you have any questions in comments.

    Root Cause of the Error

    The error you are encountering is due to a known, ongoing capacity restriction in the West Europe region (which has been affecting compute and app services since late February 2026). Azure Container Apps runs on top of Azure Kubernetes Service (AKS) under the hood. The AKSCapacityHeavyUsage error is surfacing because the West Europe region currently lacks the capacity to provision new "Free tier" AKS control planes, which Container Apps attempts to use by default for the managed environment's backend.

    Why the Dedicated Workprofile Doesn't Bypass This

    Your observation about the Consumption profile is entirely correct. According to the official Azure Container Apps documentation on Compute and billing structures, "Every Workload profiles (v2) environment automatically comes with a consumption profile." Furthermore, the documentation on Managing workload profiles explicitly states: "Note: The Consumption workload profile can't be deleted." Because the ACA architecture mandatorily includes this consumption profile alongside any dedicated profiles you add, the Azure Resource Manager continuously attempts to provision the default underlying infrastructure (the free-tier AKS cluster) during environment creation. Since you cannot delete the consumption profile, there is currently no way to force Azure Container Apps to use a "paid tier" control plane to bypass this specific capacity error.

    Recommended Workarounds

    Since Microsoft abstracts the AKS control plane tier in Container Apps, you are unfortunately blocked by the region's hardware availability. Here are your best options:

    1. Deploy to a nearby paired region (Temporary): While you mentioned concerns about latency and bandwidth costs with your SaaS database (Tiger Cloud), deploying the Container App in northeurope or francecentral is currently the fastest way to get unblocked. You can migrate it back once West Europe capacity frees up.
    2. Try again later: Capacity in West Europe dynamically frees up as resources are shifted or expanded, but Microsoft Support does not provide a guaranteed timeline for when the "Free tier" cluster constraints will be fully lifted.
    3. Alternative - Native AKS: If remaining in West Europe is an absolute hard requirement and you cannot wait, you might consider deploying a native Azure Kubernetes Service (AKS) cluster instead of Container Apps. With native AKS, you have direct control over the cluster and can explicitly select the Standard or Premium paid tier for the control plane. This will bypass the "Free tier cluster is unavailable" error completely and allow you to deploy your application in West Europe today.
    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.