Bicep Classic - Complete
The complete starter module for the Bicep Classic framework uses the traditional ALZ-Bicep modules.
WarningThis documentation is specific to the Bicep Classic framework (iac_type: bicep-classic). For the new Azure Verified Modules framework, see Bicep Azure Verified Modules for Platform landing zone (ALZ).
- Repository: ALZ-Bicep
- Architecture: Traditional ALZ-Bicep modules
- Benefits: Proven stability and existing deployment compatibility
- Recommended for: Existing ALZ-Bicep deployments
- IAC Type:
bicep-classic
The following table describes the inputs required for the complete starter module:
| Input | Placeholder | Description |
|---|---|---|
Prefix | landing-zone | This is the default prefix for names of resources and management groups. |
Environment | live | The environment name for the landing zone. This can be any lower case string. (e.g. live or canary) |
networkType | hubNetworking | The type of network configuration to deploy. Currently only hubNetworking, hubNetworkingMultiRegion, vwanConnectivity, vwanConnectivityMultiRegion or none are supported. |
SecurityContact | <email-address> | The email address of the security contact for the landing zone. |
Example input files for the Bicep Classic framework:
- inputs-azure-devops-bicep-complete.yaml
- inputs-github-bicep-complete.yaml
- inputs-local-bicep-complete.yaml
To use the Bicep Classic framework:
- Set your
iac_typetobicep-classicin your configuration file - Use the example configuration files above as a starting point
- Customize the inputs according to your requirements
- Bootstrap and deploy with the accelerator