You have container source code stored in a Git repository.

Azure Container Registry Tasks provides Azure-hosted container build capabilities, eliminating the need to maintain external Docker build servers or dedicated CI build infrastructure. A Quick task uses commands such as az acr build to send the build context to ACR-managed compute, where Azure builds the container image and, by default, pushes the successfully built image directly into the registry. Microsoft describes quick tasks as cloud-based, on-demand build-and-push operations that do not require a local Docker Engine.

For automatic execution after source-code changes, use a Source-triggered task . ACR Tasks can associate a task with a GitHub or Azure Repos repository and automatically execute the image build whenever code is committed to the configured branch. Microsoft documents that when a commit occurs, the source-control trigger causes ACR Tasks to build and push the resulting image.

A Webhook is not the required standalone ACR build component here. ACR Tasks creates and manages the necessary source-repository webhook as part of configuring the source trigger. An Artifact Cache rule caches upstream container artifacts and does not build application images from Git commits.

Study Guide references: Azure Container Registry Tasks → Quick tasks; Automatically triggered tasks; Source-code commit triggers; cloud-based image builds.