Question

Your organization maintains reusable Bicep modules that multiple product teams consume across separate repositories. Currently each team copies module files into their own repo, causing drift and inconsistent versions. You must centralize the modules so teams reference a single published, immutable, versioned source that integrates natively with Bicep tooling and does not require exposing module source files in a shared Git repo. What should you implement?

Accepted Answer

Publish the modules to a private Bicep module registry hosted in Azure Container Registry and reference them by version tag using the 'br:' path scheme.

Answer

Store the modules in an Azure Artifacts universal package feed and download them with a UniversalPackages task before each deployment.

Answer

Create a Git submodule pointing each consumer repo to a central modules repository and pin it to a commit hash.

Answer

Package the modules as a NuGet package in a GitHub Packages feed and restore them during the build stage.