Access Azure Verified Modules (AVM)
Directly in your own Git

With IPM, accessing every Azure Verified Module (AVM) for Bicep has never been easier. Seamlessly integrate AVM modules into your workflow, use them free of charge, and effortlessly innersource code with zero telemetry. Every package includes built-in documentation, allowing you to load Bicep code directly into your own repository—eliminating external dependencies. Plus, leverage nested packages to streamline management and speed up deployments.

IPMHub Logo

Stay Up-to-Date with Azure Verified Modules (AVM)
Using IPM

Stay ahead with the latest Azure Verified Modules using IPM. Enjoy automatic updates, robust version control, and direct access to the AVM source code—no external dependencies required. Manage your deployments on your terms with in-package documentation and secure, consistent IaC updates that empower you to maintain control over every module.

Azure Verified Modules

Name Description Version Last update

What Are Azure Verified Modules?

Azure Verified Modules (AVM) define the gold standard for quality Infrastructure-as-Code (IaC). Developed by Microsoft and trusted partners, AVM ensures consistent, best-practice configurations ideal for cloud-native and migrated applications. Supporting languages like Bicep and Terraform, AVM enables developers to build reliable solutions with Microsoft's official guidance, community-driven input, and a unified code base.

Portal Image

IPM AVM

We believe in the value of Azure Verified Modules (AVM), which is why we've made them freely accessible through IPM. By providing seamless, direct access to AVM modules, we aim to equip you with reliable, best-practice IaC solutions, so you can concentrate on driving project success without hassle.

AVM

Azure Verified Modules (AVM) are Microsoft-certified, high-quality Infrastructure-as-Code (IaC) templates designed to simplify and standardize deployments. AVM modules offer best-practice configurations, available in languages like Bicep, to streamline cloud-native and migrated application setups.

Yes, we ensure AVM packages are always current by checking for updates every 24 hours. When a new AVM version is available, we promptly release an updated package.

Infrastructure as Code (IaC) is a method of automating infrastructure setup and management using code, allowing consistent, reliable, and repeatable deployments across environments. AVM supports IaC best practices for secure, scalable cloud infrastructure.

IPM

IPM, or Infrastructure Package Manager, is our tool for managing IaC packages through ipmhub.io. With IPM, you can easily download, publish, and manage Infrastructure as Code packages. For detailed guidance, visit our documentation at https://docs.ipmhub.io/docs.

The IPM client is available for download for multiple operation systems. Follow the steps at https://docs.ipmhub.io/docs/installation/.

Yes, an account is required to download AVM packages. It only takes 30 seconds to sign up. Visit https://ipmhub.io/login to create one.

Yes, using IPM is free, and AVM packages are provided under the MIT license.

About This Project

IPM gives you full control over AVM package source code directly within your own repository, enabling you to access documentation and leverage IPM's features like versioning, status updates, and Tracked Workspaces.

We've made minor, non-breaking modifications to the AVM packages to enhance functionality. These changes include:
  • Within the Module itself:
    • Appending original AVM Module version metadata
    • Appending original AVM Module published date metadata
    • Disabling telemetry by default
  • Adding a DISCLAIMER.md
  • Adding a LICENSE.txt (geen .md)

If you believe the bug originates from the AVM package itself, please report it to the AVM team. If it's an IPM client issue, report it on our GitHub discussion page.

To customize an AVM module for community or internal use, follow these steps:
  • Create a new IPM package.
  • Download the original AVM package.
  • Apply your changes.
  • Publish the updated version.