Configuration Files

Three configuration inputs are available:

• Bootstrap Configuration File
• Platform landing zone Configuration File
• Platform landing zone Library (lib) Folder

JSON instead of YAML

If you are unable to install the powershell-yaml module (the ALZ module tries to install this automatically for you when invoked), you can use .json files instead.

We would advise you complete the customizations in YAML and then convert to JSON if necessary as a final step prior to running the Deploy-Accelerator function.

You will need to convert your YAML files to JSON before running the bootstrap script. You can use an online YAML to JSON converter or a tool like DevToys.

YAML file containing configuration for bootstrapping your VCS and Azure. Examples are provided for each IaC and VCS combination.

Note

Some of this configuration is also fed into the starter module to avoid duplication of inputs. This includes management group ID, subscriptions IDs, starter locations, etc. You will see a terraform.tfvars.json file is created in your repository after the bootstrap has run for this purpose.

Note

Only required for Terraform ALZ starter module. Bicep users can skip this.

HCL tfvars file determining deployed resources and hub networking type. Copied to your repository as *.auto.tfvars.

Examples: Scenarios

This is the yaml file that determines resource names and other configuration for the Bicep Azure Verified Modules for Platform landing zone (ALZ) starter module.

Note

Only required for Terraform ALZ starter module. Bicep users can skip this.

Configuration files for customizing management groups and policies. By default, an empty lib folder is provided.

Use cases:

• Renaming or restructuring management groups
• Modifying policy assignments
• Adding custom policy definitions

Documentation:

• Platform landing zone Library
• AVM for Management Groups and Policy