Preserve URI-based deployment for ARM pipeline templates using relativePath

Source facts

In Microsoft’s ARM pipeline example, relativePath is supported only for URI-based deployments, so the parent template must be supplied through the task’s file-URL option. The pipeline also depends on the repository folder and template file names; renaming them requires corresponding pipeline updates. A downloaded parent file is not automatically an equivalent input for this addressing model. Microsoft Learn.

Applicability

Use this check when refactoring the pipeline’s artifact handling or repository layout. Determine whether the parent uses relativePath before replacing its URL with a checked-out local file. Keep this path-resolution question separate from the identity used to authorize deployment.

DSE recommendation

DSE recommends treating the parent template’s retrieval mode as part of the linked-template dependency. Record the parent location, linked file and repository layout together. If a new delivery mechanism is required, review a supported redesign of the link instead of silently changing only the task’s template-location setting. Use approved artifact access controls and do not place credentials into general build logs.

Verification

In a test pipeline, deploy the intended parent and confirm that its linked resource is actually created with the expected configuration. Repeat after a proposed rename or delivery-mode change. Retain the precise artifact revisions and task settings used for the successful run. A job that finds its parent template has not, by that fact alone, proved that the child reference resolves correctly.

Official references

Microsoft Learn. Source retrieved September 9, 2026.