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

Terraform - Azure Verified Modules for Platform Landing Zone (ALZ)

The Azure Verified Modules for Platform Landing Zone (ALZ) (platform_landing_zone) starter module deploys the end to end platform landing zone using Azure Verified Modules. It is fully configurable to meet different scenarios.

This documentation covers the top scenarios and documents all available configuration settings for this module.

We aim to cover 80% of common scenarios. If the particular scenario is not covered here, it may be possible to adjust the configuration settings to match the requirements. If not, then please raise an Issue and we’ll see if we can support it.

This documentation covers the following:

Follow these steps to populate and configure your platform landing zone configuration file:

If you followed our phase 0 planning and decisions guidance, you should have these choices already.

1 - Scenarios

Scenarios are common high level use cases when deploying the platform landing zone.

Choose your preferred scenario and copy the example configuration file to your platform-landing-zone.tfvars file.

The scenarios can be found in the Scenarios documentation.

2 - Microsoft Defender for Cloud security contact email address

The defender_email_security_contact is used by Microsoft Defender for Cloud to send security alerts to the security contact at your organization. You need to update the value with a valid security contact email address for your organization.

You’ll find this setting near the top of the platform-landing-zone.tfvars file.

To update it:

  1. Use Ctrl + F to bring up the search dialog
  2. Enter defender_email_security_contact in the search dialog
  3. Hit enter to search for the key
  4. Update the value replace_me@replace_me.com with a valid security contact email address for your organization
  5. Save the configuration file

3 - Options

The options section details how to make configuration changes that apply to the common scenarios.

Choose your preferred option and update the your platform-landing-zone.tfvars file by following the detailed instructions for each option.

The options can be found in the Options documentation.

4 - Advanced

If you were unable to cover all your platform landing zone requirements with our standard scenarios and options, you can use the advanced configuration settings to further customize your deployment.

The advanced configuration settings can be found in the Platform landing zone configuration file documentation.

Next Steps

Now head back to Phase 2 to continue your deployment.