Euvic Bicep Modules

Reusable Azure infrastructure modules, published as compiled Bicep artifacts to a public container registry. 27 modules are available today; browse them in Available modules.

The registry allows anonymous pull, so consuming a module needs no Azure login and no credential.

How to consume

Add the registry alias to your bicepconfig.json:

{
  "moduleAliases": {
    "br": {
      "Euvic-Modules": {
        "registry": "geitbicepmodweucr01.azurecr.io",
        "modulePath": "bicep/modules"
      }
    }
  }
}

Reference a module by its exact version:

module mod_vault 'br/Euvic-Modules:key-vault/vault:1.0.0' = {
  name: 'mod-vault'
  params: {
    par_key_vault_name: 'my-vault'
  }
}

Run az bicep restore before building.

What you get, and what you do not

Modules are published compiled. You receive the ARM manifest, not the Bicep source, so implementation detail stays private while the interface is fully documented here: every parameter, every output and every resource type the module creates.

Published versions are immutable. A tag is never overwritten, so a build that worked yesterday works today. Fixes ship as a new patch version, which is why you pin an exact version rather than a range.

Machine-readable catalogue

The same data backing this site is served as JSON at available-modules.json. Fetch it with a plain curl; no token, no login.