Unable to create container app environment in region west-europe due to AKS capacity issues

KataSle-2013 0 Reputation points

Azure is experiencing problems with AKS capacity in the west-europe region. Because of this I cannot create a container app environment in my paid subscription. The recommended solution is to create resources in other regions. However, I need to create this resource inside a VNet that is already in west-europe, therefore the container app environment also needs to be created in west-europe.

what can I do? also, when is this problem expected to be resolved?

see below for the detailed error message:

"error":{"code":"ManagedEnvironmentCapacityHeavyUsageError","message":"AKS is experiencing heavy usage in region westeurope. We are working on adding new capacity. In the meantime, please consider creating new AKS clusters in a different region. 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."

  1. Pravallika KV 17,025 Reputation points • Microsoft External Staff • Moderator

    @KataSle-2013 , Following up to see if the provided answer was helpful. If this answers your query, do click Accept Answer =>Yes, and upvote it. If you have any further queries do let us know.

Sign in to comment

3 answers

  1. SUNOJ KUMAR YELURU 18,336 Reputation points • MVP • Volunteer Moderator

    Hello @KataSle-2013,

    Thank you for reaching out Q&A forum.

    Capacity in West Europe fluctuates throughout the day as other customers release resources. Many users have reported success simply by retrying at different times:

    • Try during off-peak hours (early morning UTC, weekends)
    • Retry every few hours via CLI to avoid portal timeout delays:

    az containerapp env create \

    --name <env-name> \

    --resource-group <rg> \

    --location westeurope \

    --infrastructure-subnet-resource-id <your-subnet-id>

    • The GitHub issue tracking this (Azure/AKS #4185) has been open with sporadic capacity relief but no permanent fix
    • Raise an Azure Support Ticket (Recommended for Production)

    If this answers your query, do click Accept Answer and Up-Vote for the same. And, if you have any further query do let us know.

    0 comments No comments
    Sign in to comment
  2. Pravallika KV 17,025 Reputation points • Microsoft External Staff • Moderator

    Hi @KataSle-2013 ,

    Azure Container Apps environments in a VNet still depend on underlying AKS capacity in the chosen region, so when you hit the AKS capacity issue, the environment deployment can fail even if your subscription is paid.

    • Error code: ManagedEnvironmentCapacityHeavyUsageError
    • Underlying cause: “AKS is experiencing heavy usage in region west/europe…”

    This is consistent with an AKS regional capacity constraint: when demand is high, Azure can’t allocate the compute needed to provision the AKS components used by the Container Apps environment.

    1. Try creating the environment again later

    Capacity constraints like this are often emporaryMicrosoft notes they are working to add capacity, and resources may become available after other deployments complete or are deallocated. So a simple retry after some time is a valid mitigation.

    1. Consider adjusting AKS-related deployment settings (if applicable)

    For the same class of AKS capacity errors (AKSCapacityHeavyUsage), guidance suggests that different AKS configurations can sometimes land on different capacity pools, such as:

    • trying public vs. private cluster configuration (or the reverse), depending on what you can change for your scenario.

    (Whether this applies directly to Container Apps Environment depends on how your environment is configured, but it’s the closest relevant mitigation we have for “capacity heavy usage.”)

    1. Use an Azure region with AKS capacity (but you said you can’t)

    The recommended workaround for AKS capacity heavy usage is typically to deploy in another region. However, since you need the Container Apps environment to be in west-europe because your VNet is already there, that may not be feasible for you.

    1. If available, use an Enterprise Agreement (EA) subscription

    For AKS capacity heavy usage, guidance indicates that EA subscriptions can be prioritized during high-demand periods. If your organization has an EA subscription option, it may help.

    • wait and retry, and track whether the deployment begins succeeding after capacity increases.

    Hope this helps!

    If the resolution was helpful, kindly take a moment to click on 👁 User's image
    and click on Yes for was this answer helpful. And, if you have any further query do let us know.

    0 comments No comments
    Sign in to comment

  3. AI answer

    The error indicates regional capacity constraints similar to the AksCapacityHeavyUsage condition. In this situation, only the following options are available:

    1. Try a different region (if possible)
      The documented primary mitigation for AKS capacity issues is to deploy to another region where capacity is available. For example, use a nearby region such as North Europe instead of West Europe when that fits the architecture.
    2. Change cluster characteristics
      Capacity is managed per type of AKS infrastructure. If the workload allows it, try changing characteristics that affect allocation, such as:
      • Using a public instead of a private configuration (or vice versa), because different reservations may exist for each.
        This can sometimes succeed even when the original configuration fails with a capacity error.
    3. Use an Enterprise Agreement subscription if available
      When capacity is tight, non‑Enterprise Agreement (EA) subscriptions are limited first to reserve resources for production scenarios. If an EA subscription is available, use that subscription for the deployment.
    4. Retry later
      Capacity is reclaimed when other customers delete or stop clusters. Retrying the deployment periodically can succeed once capacity is freed.

    If the environment must be in West Europe and none of the above workarounds are acceptable, there is no self‑service way to override the regional capacity restriction. The documentation does not provide an ETA for when capacity in a specific region (such as West Europe) will be restored; it only states that Microsoft is working on adding new capacity and recommends the mitigations above.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.
Sign in to answer

Your answer