Container App Environment - failed provisioning state caused by UpdateError

Dmitry Zvenkov 0 Reputation points
2026-08-14T16:21:51.73+00:00

User's image

Observing this problem, can't spot anything on our side that could have provoked it, also been around for more than 8 hours now, any ideas on what shall we do?

Azure Container Apps
Azure Container Apps

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

0 comments No comments

1 answer

Sort by: Most helpful
  1. Allan Solomon Mejia 3,670 Reputation points
    2026-08-14T18:59:04.26+00:00

    Hello @Dmitry Zvenkov

    Based on the screenshot, this looks like an environment-level infrastructure update failure (UpdateError), rather than a failure of an individual Container App or revision. The diagnostic message also indicates that the platform detected an environment/cluster upgrade or update error.

    Since it has remained in Failed provisioning state for more than 8 hours, I would first check whether anything affecting the environment infrastructure recently changed, particularly:

    • VNet/subnet, NSG, UDR, firewall, or custom DNS configuration
    • Azure Policy assignments affecting the managed environment or its infrastructure
    • Available subnet address space if this is a VNet-integrated environment

    Microsoft notes that VNet or Azure Policy configurations can prevent Container Apps infrastructure updates, and environments can remain in a failed state as a result.

    You can also check the environment directly with:

    az containerapp env show \
      --name <environment-name> \
      --resource-group <resource-group>
    

    Review properties.provisioningState and the environment configuration. Also check Activity Log around the time the failure started for Microsoft.App/managedEnvironments operations and any additional error details. The API exposes detailed error information such as code, message, details, and innererror when available.

    If there were no customer-side networking, policy, or environment changes and the state remains Failed, I wouldn't recommend deleting/recreating the environment yet, especially if it hosts production workloads. At that point this could require Azure Container Apps platform-side investigation, and opening an Azure Support request with the environment resource ID, region, timestamp when the issue began, and relevant Activity Log correlation IDs would be appropriate.

    Sharing you the references:

    Azure Container Apps environments | https://learn.microsoft.com/en-us/azure/container-apps/environment?

    Container Apps virtual network configuration | https://learn.microsoft.com/en-us/azure/container-apps/custom-virtual-networks?

    Azure Container Apps troubleshooting | https://learn.microsoft.com/en-us/azure/container-apps/troubleshooting?

    Please "Accept the Answer" if this information helped you. This will help others in the community as well.

    Was this answer helpful?


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.