Azure Container App stuck on Activating

Hello @Harold Cabrera,
When an Azure Container App is stuck in the "Activating" state, it usually means it’s trying to start a new replica but hasn’t been able to complete the process. Since this is happening across all your environments in the Sweden region, here are a few things to check. First, make sure your health probes are configured correctly, if the container fails health checks, it won’t transition out of the activating state.

Also, check your ingress settings to confirm that the port your app is listening on matches the port defined in your container app configuration. If you’re using a virtual network, ensure it has the right DNS and outbound access, especially if you're pulling images from a private registry.

Since you’ve set the app to scale with zero minimum replicas, it will only start when triggered, so double-check that your Service Bus queue has active messages and that your scaling rules are still valid. It’s also a good idea to look at the Revisions and Replicas section in the portal to see if the latest revision is showing as degraded or failed.

Occasionally, issues can come from regional capacity or service health, so we recommend checking the Azure status page for any active issues in the Sweden region. If nothing seems off, try restarting or redeploying the app to see if that resolves the activation issue. Sometimes resource constraints or backend issues can delay activation.

Kindly refer below links:

Troubleshoot start failures in Azure Container Apps

https://azure.status.microsoft/en-us/status

Troubleshoot a container app

Hope this helps. Do let us know if you any further queries.

Thank you for your response.

All the Container Apps was working this morning. I checked the Sweden Central region and there are no outage reported. There has been no change in the configuration and setup.

The Logstream for the Application is just black. I've tried stopping and restarting the Container App, with no luck. I know there are messages in the queue, hence the Activation of the Container. I have tried a new deployment in Dev and limit the instance to 1. When I did that, I actually got an Activation Failed message. But no other clues on why it failed.

Do you have any other ideas?

Hello @Harold Cabrera,
Thanks for the update. Since you’re seeing an Activation Failed message and no logs, it likely means the container is failing very early during startup. Please check if your container image or startup command might have any issues. Also, look at the container’s exit code or events in the Azure portal or use the Azure CLI to get more details on why it’s failing. Since you’re using GPU resources in Sweden, verify that the region has available capacity and that your app is correctly configured to request those resources.

Make sure the app can pull the container image from the registry without any authentication problems. To help isolate the issue, you could try deploying a simple, known container image in the same region and see if it starts successfully. If that minimal container also fails, the problem might be with the platform or regional capacity.

Hello @Harold Cabrera,
Just checking in to see if above information was helpful. If you have any further updates on this issue, please feel free to post back.

Unfortunately not. It's all still stuck on Activating. We've opened a support ticket with Microsoft and it has been escalated to the Product Team.

What's worst is that it seems that we are being charged for the Resource over the last day!