Infrastructure Chaos 

Last Updated on February 17, 2024 by Arnav Sharma

Azure Verified Modules (AVM) is a transformative initiative by Microsoft, designed to align the deployment of Infrastructure-as-Code (IaC) modules with the well-architected framework. This initiative is crucial for customers evolving from managing Azure resources directly through the portal to adopting IaC methods like Bicep, or Terraform. AVM represents a community-driven aspiration within Microsoft, aiming to provide and define standards for what a good infrastructure-as-code module looks like.

The Problem: 

Modules: The Core of AVM

The AVM framework leverages popular languages like Bicep and Terraform, reflecting the technologies used by Microsoft’s customer base. It includes two types of modules:

  1. Resource Modules: These modules, acting as building blocks, set up single Azure services. For example, a resource module for a virtual machine provides a fully operational VM with all necessary components like network connections.
  2. Pattern Modules: These modules are comprehensive blueprints that combine multiple services to create complete solutions, such as an entire application landing environment, including load balancers, VMSS, and security features.

Bicep and Terraform Integration

AVM’s initial release prominently features Bicep and Terraform, aligning with the well-architected framework to ensure secure and reliable deployments. This integration enables customers to deploy Azure resources and architectural patterns consistently and efficiently.

A Unified IaC Approach

AVM introduces a unified approach to IaC, addressing the confusion and inefficiencies caused by varied deployment methods within an organization. It offers a single source of truth across Microsoft, aligning with secure and reliable deployment standards, and enabling a consistent view across languages.

Empowering Community Participation

AVM is a community-driven initiative, encouraging contributions from both inside and outside of Microsoft. Contributors play a vital role in the AVM ecosystem:

  • Module Owners: Microsoft team and FTEs, responsible for creating, managing, and maintaining modules.
  • Module Contributors: Open to anyone globally, these contributors support module owners in managing and maintaining modules.

The Future of AVM

AVM is set to broaden its impact by expanding module offerings and enhancing its framework. The Module Triage Board offers a glimpse into ongoing developments, proposed modules, and the progress of this initiative.

The Starting Point of AVM

AVM represents the beginning of a journey for customers in their IaC journey, offering modules that simplify and accelerate the deployment process, regardless of their current stage.

AVM’s Mission and Vision

AVM’s mission is to provide a unified, secure, and efficient approach to deploying Azure resources and architectural patterns. Its vision is to accelerate deployment, ensure consistency, and support the development of well-architected solutions in Azure.

FAQ: AVM

Q: What can developers do to enhance their understanding of Azure Verified Modules (AVM)?

Azure Verified Modules (AVM) enable developers to construct and manage infrastructure as code (IaC) using languages such as Terraform etc. To enhance their understanding, developers can explore topics related to AVM modules, learn from the guidance provided, and contribute their own code. The AVM team, supported by Microsoft, encourages developers to participate and drive the community-driven aspiration of these modules.

Q: How can a user view and consume Azure Verified Modules?

A user can view and consume Azure Verified Modules by exploring the repository on GitHub. This repository offers a comprehensive description of each module’s capabilities and provides a policy for their usage. Additionally, users can explore topics within the repository to find modules that suit their specific needs in infrastructure management.

Q: What resources are available for learning about Azure Verified Modules?

For those who would like to learn about Azure Verified Modules, there are various resources available. One can explore YouTube for video tutorials and transcripts that offer step-by-step guidance. Additionally, the Azure platform itself may provide documentation and support, helping users to understand how to use and test these modules effectively.

Q: How does the Azure community contribute to the development of Azure Verified Modules?

The Azure community contributes to the development of Azure Verified Modules by acting as both contributors and consumers. They can create and update modules, test them in real-world scenarios, and provide feedback. This community-driven approach ensures that the modules stay relevant and effective for a wide range of use cases in infrastructure management.

Q: What are the benefits of Azure Verified Modules for infrastructure management?

Azure Verified Modules provide a structured way to manage infrastructure through code. They offer a package of pre-built, Microsoft-supported solutions that make it easier for developers to deploy and manage cloud resources. These modules enable streamlined and efficient infrastructure development,

Q: What role do partners play in the Azure Verified Modules ecosystem?

Partners in the Azure Verified Modules ecosystem play a crucial role by collaborating with the AVM team to create and test new modules. They bring in their expertise to drive innovation and expand the range of modules available, ensuring they meet the high standards required for Azure infrastructure management. This partnership is essential in maintaining the quality and relevance of the modules.

Q: How can a developer update their knowledge about the latest Azure Verified Modules?

A developer can update their knowledge about the latest Azure Verified Modules by regularly checking the GitHub repository for the latest releases and updates. They can also subscribe to update notifications or join community forums where new releases and features are often discussed. Staying informed helps developers to leverage the latest tools and practices in infrastructure management.

Q: What is the significance of the ‘0’ identifier in Azure Verified Modules?

The ‘0’ identifier in Azure Verified Modules is significant as it typically represents the initial release or a major update of a module. It indicates a foundational version from which further iterations and improvements are made. Understanding these versions is important for developers to ensure they are using the most suitable module for their infrastructure needs.

Q: Can you explain the cookie policy in the context of Azure Verified Modules?

The cookie policy in the context of Azure Verified Modules is related to the web platforms, like GitHub or Azure’s own site, where these modules are hosted and discussed. The policy outlines how cookies are used to enhance the user experience, manage user sessions, and remember preferences. Users can often update their choices regarding cookie usage on these platforms.


iac languages community driven aspiration to update your choices

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Toggle Dark Mode