Create an ACR Task using az acr task create with --registry <ACR_NAME>, --name <TASK_NAME>, --image <IMAGE_TAG>, --context <GIT_REPO_URL>#<BRANCH>, and --file Dockerfile
Configure a GitHub personal access token (PAT) with repo scope as the source trigger credential by passing --git-access-token to the task create command; ACR stores the token to register a GitHub webhook
The task automatically registers a webhook in the GitHub repository; on each push to the specified branch, GitHub calls back to ACR which queues a build run
Monitor task runs with az acr task logs --registry <ACR_NAME> --name <TASK_NAME> or retrieve run history with az acr task list-runs --registry <ACR_NAME>
Optionally add a base image update trigger with --base-image-trigger-enabled true so the task also fires when the upstream base image in the same ACR is updated
Known gotchas
ACR Tasks require at least the Basic service tier; free-tier or Classic registries do not support Tasks
The GitHub PAT used for the source trigger must have repo scope (not just public_repo) even for public repositories, because ACR needs to create a webhook in the repository settings
Build context is transferred to ACR from the git repository at run time; large monorepos with many files significantly increase transfer time and can cause task timeout on the default 3600-second limit
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp