You can now publish Bicep modules to an Azure Container Registry (ACR), just like Docker images. This solves the “shared module” problem in enterprises.
# Publish
bicep publish storage.bicep --target br:myregistry.azurecr.io/modules/storage:v1
// Consume
module stg 'br:myregistry.azurecr.io/modules/storage:v1' = {
name: 'mystorage'
params: { ... }
}
This enables a central platform team to version and distribute approved infrastructure patterns (like secure storage accounts) to app teams.
Discover more from C4: Container, Code, Cloud & Context
Subscribe to get the latest posts sent to your email.