In the rapidly evolving landscape of cloud infrastructure, the Azure Bicep stands out as a declarative language and a tool designed to simplify the deployment of Azure resources.

In this post, we will explore the world of Bicep modules that are published to Microsoft’s Public Registry through the Azure Verified Modules (AVM) initiative and how they can be combined with private modules that organizations can develop to fit their specific needs.

We will focus on a practical example on how to build a ‘Private Modules Library’, a publishing engine on GitHub that can follow recommended practice for testing and validating your modules before they are published to your private registry.

The goal is to demonstrate how you can combine the use of public modules, curated by Microsoft, with your own code in a consistent way and how to empower your cloud engineers to use this Library.

The demo environment (and repository) will contain all code artefacts for building the Private Modules Library, provisioning all necessary prerequisites, and deploying a ‘solution’ using a private pattern module.

The main building blocks of this solution are Bicep, AVM, GitHub Actions workflows, PowerShell, PSRule for Azure and a few more.