In the rapidly evolving landscape of cloud infrastructure, the Azure Bicep stands out as Azure native declarative Infrastructure as Code (IaC) language and a tool designed to simplify the deployment of Azure resources. When your organization matures with its IaC adoption, new challenges emerge like applying the DRY (Don’t Repeat Yourself) principle, improving collaboration across teams, writing a secure code that follows Microsoft recommended practices, etc.

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

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 practically how you can combine the use of public modules, curated by Microsoft, with your own code in a consistent way and how you can empower your cloud engineers to use this Library together with a custom Web Catalogue that can help the understand and use the modules better.

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, PSDocs, MKDocs, and more.

The session is based on a real-life customer project where such Modules Library was used for deploying Azure Virtual Desktop environments automatically through code.