Container App Environment stuck in "Waiting" provisioning state - blocking deployment

Question

Container App Environment stuck in "Waiting" provisioning state - blocking deployment

Brian Stefanovich 0

Severity: Moderate (Business impact)

We have a Container App Environment that is stuck in a "Waiting" provisioning state and cannot perform any operations on it. This is blocking our infrastructure deployment.

Problem Summary:

The Container App Environment shows in az containerapp env list with a provisioning state of "Waiting", but does not appear in az

containerapp env show or generic resource API calls. Any attempt to create, modify, or delete this resource fails with a 409 Conflict

error.

**
Error Message**: ManagedEnvironmentOperationInProgress: Cannot modify Container Apps environment kc-next-app-test-container-app-env because another operation is in progress.

Steps Taken:

Attempted to delete the resource using az containerapp env delete --no-wait
Attempted to delete via REST API
Waited over 15 minutes for the operation to clear
Attempted to refresh Terraform/OpenTofu state
The resource remains stuck in "Waiting" state

Impact:

Cannot deploy Container App Environment for test environment
Infrastructure as Code deployment is blocked
Team cannot proceed with application deployment

Request:
Please manually clear the stuck operation lock on this Container App Environment so we can either: Complete the creation if it's in progress, or Delete the corrupted resource so we can recreate it.

Additional Context:

Activity logs show a "Create or Update Managed Environment" operation started at approximately 2025-09-29T20:04:52Z but never completed or failed. The operation appears to be in a corrupted state.

Pashikanti Kumar 1,725 Reputation points Microsoft External Staff Moderator

2025-09-29T22:47:11.22+00:00
Hi Brian Stefanovich,

Thanks for contacting Microsoft Q&A platform.

The issue of a Container App Environment being stuck in the "Waiting" provisioning state is typically caused by an incomplete or hung operation on the resource.

Check the Current State of the Environment

Use the Azure CLI to inspect the current state of the environment

az resource show --name kc-next-app-test-container-app-env --resource-group <resource-group> --resource-type "Microsoft.App/managedEnvironments"

Look for the provisioningState property. If it is stuck in Waiting or InProgress, this confirms the issue.

Cancel the Stuck Operation

Attempt to cancel the operation using the Azure CLI

az resource cancel --name kc-next-app-test-container-app-env --resource-group <resource-group> --resource-type "Microsoft.App/managedEnvironments"

If the cancellation is not supported or fails, proceed to the next step.

Force Delete the Environment

If the environment cannot be modified due to the stuck operation, force delete it

az resource delete --name kc-next-app-test-container-app-env --resource-group <resource-group> --resource-type "Microsoft.App/managedEnvironments"

Ensure there are no active Container Apps associated with the environment before deleting. Use the following command to list Container Apps:

az containerapp list --resource-group <resource-group> --query "[?managedEnvironmentId=='<environment-id>']"

After deleting the stuck environment, recreate the Container Apps environment

az containerapp env create --name kc-next-app-test-container-app-env --resource-group <resource-group> --location <location>

Dependencies: Ensure no other resources (e.g., Container Apps) are actively using the environment during modification or deletion

I hope the provided answer is helpful,

Please "Up Vote" if the information helped you. This will help us and others in the community as well.

Thanks
Pashikanti Kumar 1,725 Reputation points Microsoft External Staff Moderator

2025-09-30T19:27:41.62+00:00

Hi Brian Stefanovich,

I hope the provided answer is helpful, please "Upvote" if the information helped you. This will help us and others in the community as well.

Thanks
VenkateshDodda-MSFT 25,251 Reputation points Microsoft Employee Moderator

2025-10-01T09:28:55.75+00:00

@Brian Stefanovich Thanks for your patience on this.

Based on the shared information, I have looked at the backend logs and can confirm that container app environment "kc-nt-app-test-c*ainer-a**p-env" has been created sucessfully at 2025-09-30 00:25 UTC and deleted successfully around 2025-09-30 01:54 UTC.

If you still face the issues, please do share the required details like container app environment name, operation id or correlation id over the private message to check and assist you further.

How to access the private message in Microsoft Qna : https://learn.microsoft.com/en-us/answers/support/private-messages

Hope this helps let if know if you have any further questions on this.
Pashikanti Kumar 1,725 Reputation points Microsoft External Staff Moderator

2025-10-09T17:26:00.07+00:00

Hi Brian Stefanovich,

Some of the actions they perform on the container apps seem to reflect the status as Started/Accepted but they fail to Succeed for longer durations or until another delete/write operation is performed. This might result in UI showing the incorrect provisioning state as the action did return the Succeeded status message.

We will investigate the operations that failed to Succeed and find more information on why they end up in the bad stated. We will keep you posted once we have more findings
LeelaRajeshSayana-MSFT 17,871 Reputation points Moderator

2025-10-10T15:43:06.0766667+00:00

@Brian Stefanovich May I know if you have validated the status of the container app through a CLI command such as az containerapp show or did you monitor it just from portal? Are the observations any different compared from CLI to portal response?

Your answer

Pashikanti Kumar 1,725 Reputation points Microsoft External Staff Moderator

2025-09-30T19:27:41.62+00:00

Hi Brian Stefanovich,

I hope the provided answer is helpful, please "Upvote" if the information helped you. This will help us and others in the community as well.

Thanks
VenkateshDodda-MSFT 25,251 Reputation points Microsoft Employee Moderator

2025-10-01T09:28:55.75+00:00

@Brian Stefanovich Thanks for your patience on this.

Based on the shared information, I have looked at the backend logs and can confirm that container app environment "kc-nt-app-test-c*ainer-a**p-env" has been created sucessfully at 2025-09-30 00:25 UTC and deleted successfully around 2025-09-30 01:54 UTC.

If you still face the issues, please do share the required details like container app environment name, operation id or correlation id over the private message to check and assist you further.

How to access the private message in Microsoft Qna : https://learn.microsoft.com/en-us/answers/support/private-messages

Hope this helps let if know if you have any further questions on this.
Pashikanti Kumar 1,725 Reputation points Microsoft External Staff Moderator

2025-10-09T17:26:00.07+00:00

Hi Brian Stefanovich,

Some of the actions they perform on the container apps seem to reflect the status as Started/Accepted but they fail to Succeed for longer durations or until another delete/write operation is performed. This might result in UI showing the incorrect provisioning state as the action did return the Succeeded status message.

We will investigate the operations that failed to Succeed and find more information on why they end up in the bad stated. We will keep you posted once we have more findings
LeelaRajeshSayana-MSFT 17,871 Reputation points Moderator

2025-10-10T15:43:06.0766667+00:00

@Brian Stefanovich May I know if you have validated the status of the container app through a CLI command such as az containerapp show or did you monitor it just from portal? Are the observations any different compared from CLI to portal response?