Container registry webhook to App Service gets 405 Method Not Allowed

Jean Charles, Didier (-AZ-) 1 Reputation point
2021-09-01T16:51:21.043+00:00

Here's what we know so far...

1) the team can successfully run the Azure DevOps pipeline, which deploys a Linux container to Azure container registry
2) we can successfully verify that the new container is deployed based on the timestamp

However, when the container registry webhook attempts to execute we get a 405 Method Not Allowed -

I am looking into things and have started wondering about the permissions to pull the image to the wep service. Is there an identity that I am missing? Do I need to create something that will have a “pull” role to deploy the image?

Azure Container Registry
Azure Container Registry
An Azure service that provides a registry of Docker and Open Container Initiative images.
415 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. prmanhas-MSFT 17,901 Reputation points Microsoft Employee
    2021-09-07T11:25:12.453+00:00

    @Jean Charles, Didier (-AZ-) Apologies for the delay in response and all the inconvenience caused because of the issue.

    You need to have certain roles configured to pull the image. As mentioned here below are the roles with their respective capabilities:

    129895-image.png

    You can assign the role accordingly. Also I would recommend you to go through this as well which talks about Azure Container Registry webhook. As mentioned The endpoint for a webhook must be publicly accessible from the registry. You can configure registry webhook requests to authenticate to a secured endpoint. You can configure it accordingly as mentioned if not already done.

    Hope it helps!!!

    Please "Accept as Answer" if it helped so it can help others in community looking for help on similar topics.

    0 comments No comments