Automatically generated Github Actions yaml is wrong

Question

Automatically generated Github Actions yaml is wrong

Tyler Suard 25

When I create a web app and set it up for CI/CD with a container registry and Github, Azure creates a YAML for the workflow file. That YAML is wrong, and it creates an image in a repository that the web app is not looking for. I get not found/unauthorized errors every time.

Specifically, this:

tags: ragchatcr.azurecr.io/${{ secrets.AZUREAPPSERVICE_CONTAINERUSERNAME}}/ch5-image:${{ github.sha }}

Should be this:

tags: ragchatcr.azurecr.io/ch5-image:${{ github.sha }}

Tyler Suard 25 Reputation points

2025-08-08T02:07:45.6633333+00:00

@Bhargavi Naragani The generated YAML often includes an incorrect tag format. Why? Can you please contact the developers responsible for that and ask them to fix their mistake?
Bhargavi Naragani 7,445 Reputation points Microsoft External Staff Moderator

2025-08-11T08:50:23.8466667+00:00

Hi Tyler Suard,

This happens because the current GitHub Actions workflow template that Azure generates tries to dynamically insert a username variable (${{ secrets.AZUREAPPSERVICE_CONTAINERUSERNAME }}) into the ACR repository path. In most cases, this variable isn’t required for the image name and ends up creating a path mismatch between what’s pushed to ACR and what your Web App is configured to pull.

1 answer

Your answer

Tyler Suard 25 Reputation points

2025-08-08T02:07:45.6633333+00:00

@Bhargavi Naragani The generated YAML often includes an incorrect tag format. Why? Can you please contact the developers responsible for that and ask them to fix their mistake?
Bhargavi Naragani 7,445 Reputation points Microsoft External Staff Moderator

2025-08-11T08:50:23.8466667+00:00

Hi Tyler Suard,

This happens because the current GitHub Actions workflow template that Azure generates tries to dynamically insert a username variable (${{ secrets.AZUREAPPSERVICE_CONTAINERUSERNAME }}) into the ACR repository path. In most cases, this variable isn’t required for the image name and ends up creating a path mismatch between what’s pushed to ACR and what your Web App is configured to pull.

Answer 1

Hi Tyler Suard,

When you configure CI/CD using the Azure Portal with a custom container from Azure Container Registry (ACR), it automatically generates a GitHub Actions workflow file. However, the generated YAML often includes an incorrect tag format, this causes image pull failures (404 Not Found or Unauthorized) because the image gets pushed to a repository name that doesn't match what your App Service is configured to pull from.

ragchatcr.azurecr.io/USERNAME/ch5-image is not the correct target – the USERNAME part shouldn't be there.

Go to your GitHub repository => .github/workflows/your-workflow.yaml, find the docker build or docker/build-push-action step. Update the tags field to remove the ${{ secrets.AZUREAPPSERVICE_CONTAINERUSERNAME }} segment.

tags: ragchatcr.azurecr.io/ch5-image:${{ github.sha }}

Commit the change and re-run your GitHub Actions workflow.

Once that’s done, your container should be pushed to the expected ACR path, and your Web App will be able to pull and run it successfully.

Configure CI/CD with GitHub Actions for App Service using container registry
GitHub Action for Docker build and push (docker/build-push-action)
Azure Web App for Containers - Configure container settings

Hope this helps, if you have any further concerns or queries, please feel free to reach out to us.

Share via

Automatically generated Github Actions yaml is wrong

1 answer

Your answer