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

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Likhitha Sulake 100 Reputation points Microsoft External Staff Moderator
    2026-08-24T17:07:01.6633333+00:00

    Hi @Dmitry Zvenkov ,

    Based on the screenshot, the issue appears to be with the Azure Container Apps Managed Environment, not with a specific Container App or revision.

    The environment is in a Failed provisioning state with an UpgradeError/UpdateError, which suggests that a platform update or upgrade did not complete successfully.

    Please check the following:

    1. Networking: Verify the subnet, NSG, UDR, NAT Gateway, and DNS settings, especially any recent changes.
    2. Policies/Locks: Check for Azure Policies or resource locks that may be blocking updates.
    3. Activity Logs: Review Microsoft.App/managedEnvironments operations and note any error messages or correlation IDs.

    CLI: Run:

    Dockerfile

    az containerapp env show

    Check the provisioningState and any detailed error information.

    Was this answer helpful?

    0 comments
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    6 deleted comments

    Comments have been turned off. Learn more

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.