azd deploy supports docker.imagePassthrough
Introduced 2026-08-26 · score 0.96
HOW TO USE IT
When deploying an existing remote image by reference, set `services.<name>.docker.imagePassthrough: true` and set the service-level `image` to its fully qualified registry reference, then run `azd deploy <service>`.
azd deploy <service>services:
<service>:
host: containerapp
image: <registry>/<repository>:<tag>
docker:
imagePassthrough: trueWHY THIS HELPS
Deploy an existing container image by reference with azd.
BEFORE THIS CHANGE
Without `imagePassthrough`, an existing external source image could be pulled, tagged, and copied to a configured destination registry.
REQUIREMENTS AND LIMITATIONS
- Version: 1.32.0
- <service> (required): Service name from `azure.yaml`.
- services.<name>.docker.imagePassthrough (required): Set to `true` to use the service image as the final remote container artifact; no local or remote image operations are performed.
- services.<name>.image (required): Fully qualified remote image reference, including an explicit registry.
- docker.remoteBuild: Cannot be combined with `docker.imagePassthrough: true`.
- azd deploy --from-package: Deploys a package path or container image tag; no flag is needed for passthrough because the configured image is reused.
- Prerequisite: Set the service host to `containerapp` in the documented configuration example.
- Prerequisite: Set the service-level image to a fully qualified remote reference that includes a registry.
- Deploys an existing container image by reference; performs no local or remote image operations.
FIRST-PARTY EVIDENCE
- https://github.com/Azure/azure-dev/releases/tag/azure-dev-cli_1.32.0
- https://learn.microsoft.com/en-us/azure/developer/azure-developer-cli/reference
- https://learn.microsoft.com/en-us/azure/developer/azure-developer-cli/publishing-workflows
- https://github.com/Azure/azure-dev/pull/9588
Check the installed version and the source before using it. Entry JSON