The Azure Verified Solutions is a platform designed to host and manage Azure Verified Modules for downstream organizations. The project aims to provide a centralized repository for customizing and extending new and existing modules, which are available in the Public Azure Bicep Registry, Enabling downstream organizations to leverage the benefits of Azure Verified Modules, combined with formal architecture documentation enabled trough the use of the C4 Model while maintaining control over their infrastructure as code, publishing to the enterprises own hosted repository (Azure Container Registry for Bicep, and Azure Template Specs).
The Azure Verified Solutions repository is positioned as an extension of the Azure Bicep Registry, providing a platform for downstream organizations to customize and extend the registry to meet their specific needs. The project is designed to work seamlessly with the Azure Verified Modules Registry, leveraging its governance and management capabilities to ensure the integrity and security of the modules hosted within the Azure Verified Solutions.
codeowners and version filesThe Public Bicep Registry, supported by the AVM and BRM repositories, is Microsoft's official Bicep Registry for first-party-supported Bicep modules. It has been in existence for a while and has garnered significant contributions.
As various teams within Microsoft collaborated to establish a unified Infrastructure as Code (IaC) approach and library, the Azure Verified Modules (AVM) initiative was launched to bridge gaps by defining specifications for both Bicep and Terraform modules.
In the BRM repository, "vanilla modules" (non-AVM modules) can be found in the /modules folder, while AVM modules are located in the /avm folder. Both are published to the same endpoint, the Public Bicep Registry. AVM Bicep modules are published under a dedicated namespace, using the avm/res & avm/ptn prefixes to distinguish them from the Public Registry's vanilla modules.
Azure-Verified-Solutions modules adhere to AVM specifications and are published to our Enterprise Bicep Registry and Template Spec. These modules are developed and maintained by our organization and partners. They are considered the most reliable and secure, recommended for use in production environments. The scope of these modules is to address features and policies missing from the AVM-published Public Bicep Registry or to override parameters with opinionated governance decisions to align with our governance and security principles. Additionally, these modules include proprietary resources and patterns to sustain the delivery of versioned solutions and platforms for our teams and partners in the form of utilities and solutions.
To get started with the Azure Verified Solutions, follow the step-by-step guide to contributing to Azure Verified Modules in the Contributing Steps Documentation.