Container App Not Found During Deployment via GitHub Actions

Hello Krishnakumar srinivasan

You can check Azure services health status https://azure.status.microsoft/en-us/status

There could be multiple reasons that cause the issue:

• Old azcli version: Update to newer version https://stackoverflow.com/questions/79629090/github-action-to-deploy-to-azure-fails-no-changes-made-containerapp-does-no
• Transient Azure Control Plane Issues: Instances have been reported where Azure's control plane experiences temporary disruptions, leading to deployment failures and timeouts. For example, a user reported a 504 GatewayTimeout error during container app creation, which was caused by such a transient issue https://learn.microsoft.com/en-us/azure/container-apps/troubleshooting?tabs=bash
• Implement Retry Logic in Deployments: Given the transient nature of some Azure issues, incorporating retry logic into your GitHub Actions workflows can help mitigate temporary failures.

Hi Krishnakumar srinivasan,

First, check the GitHub Actions job is actually signing into the same Azure subscription and resource group where the Container App lives. After you use the azure/login action with the service principal credentials, add a quick check.

az account show
az account set --subscription ${{ secrets.AZURE_SUBSCRIPTION_ID }}

and then immediately run

az containerapp show --name medical-chat-app --resource-group MyResourceGroup

to confirm that the CLI can see the exact app by name. If that command still returns NotFound, try the same CLI commands on the local machine against the same subscription and resource group if it works locally but fails inside Actions, the culprit is almost always missing permissions on the service principal. Head into the Azure portal’s Access Control (IAM) page for that resource group and give the principal at least Contributor permissions so it can list and manage Container Apps.

If the CLI can see the app both locally and in the workflow context, the next thing to check is that the Azure CLI version and extensions being used in the GitHub runner actually support Container Apps. In the workflow, install or update the Azure CLI to a current release and explicitly add the containerapp extension before any az containerapp commands.

- name: Install Azure CLI and Container Apps extension
  run: |
    curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash
    az extension add --name containerapp

This guarantees that az containerapp show knows how to find the app.

Finally, if you’ve only just created the Container App in Azure moments before triggering the workflow, give Azure a minute to finish propagating the resource. Sometimes deployment requests are accepted by ARM but aren’t immediately visible through the CLI for a short window. Waiting 60–90 seconds after creation before running the workflow can be enough to avoid that NotFound error. Once the service principal is pointed at the correct subscription and group, has enough role-based access, and the CLI is up to date with the containerapp extension installed, GitHub Actions will be able to locate and deploy to medical-chat-app without any more hiccups.

Hope it helps!

Please do not forget to click "Accept the answer” and Yes wherever the information provided helps you, this can be beneficial to other community members.

If you have any other questions or still running into more issues, let me know in the "comments" and I would be happy to help you.