Azure landing zone Documentation
Home GitHub Issue Toggle Dark/Light/Auto mode Toggle Dark/Light/Auto mode Toggle Dark/Light/Auto mode Back to homepage
Edit page

Bicep AVM - Azure Verified Modules for Platform landing zone (ALZ)

The complete starter module for the new Bicep framework uses Azure Verified Modules from the alz-bicep-accelerator repository.

Tip
This is the new Bicep framework (iac_type: bicep) built on Azure Verified Modules. For the traditional framework, see Bicep Classic - Complete.

Framework Overview

  • Repository: alz-bicep-accelerator
  • Architecture: Built on Azure Verified Modules (AVM)
  • Benefits: Enhanced modularity, better maintainability, alignment with Microsoft’s latest best practices
  • Recommended for: New Azure Landing Zone deployments
  • IAC Type: bicep

Key Features

The new framework provides:

  • Modular Architecture: Leverages Azure Verified Modules for better component isolation
  • Enhanced Maintainability: Improved code structure and organization
  • Future-Proof: Aligned with Microsoft’s latest Azure Landing Zone guidance
  • Simplified Deployment: Streamlined module structure for easier customization

Module Structure

The framework includes the following core modules:

  • Core Governance: Management group structure and policy assignments
  • Core Logging: Centralized logging and monitoring setup
  • Networking Options:
    • Hub networking for traditional hub-spoke architectures
    • Virtual WAN for integrated and automated hub and spoke configuration and connectivity

Configuration Inputs

The following table describes the inputs required for the complete starter module:

InputPlaceholderDescription
networkTypehubNetworkingThe type of network configuration to deploy. Currently only hubNetworking, vwanConnectivity, or none are supported.
bootstrap_module_version<version>The specific release version of the Acccelerator Bootstrap modules to target. We recommend using “Latest”
starter_module_version<version>The specific release version of the ALZ Bicep Accelerator modules to target. We recommend using “Latest”

Example Configuration Files

Migration from Classic

If you’re considering migrating from the classic framework:

  • New Deployments: Start with the new framework for enhanced capabilities
  • Existing Deployments: Continue with the classic framework for stability for now
Note
Migration guidance will be provided as the new framework reaches general availability.