Phase 2 - Bootstrap

Info

If you prefer more control over the configuration process, see the Advanced Usage guide for manual configuration.

Follow these instructions to bootstrap your Version Control System and Azure ready to deploy your Platform landing zone.

The simplest way to get started is to use the interactive wizard which guides you through all the required inputs.

1. Run the following command to install or update the ALZ PowerShell module:

   $alzModule = Get-InstalledPSResource -Name ALZ 2>$null
   if (-not $alzModule) {
       Install-PSResource -Name ALZ
   } else {
       Update-PSResource -Name ALZ
   }
   

2. Run the accelerator with no parameters to start the interactive wizard:

   Deploy-Accelerator
   

3. The wizard will guide you through:

   • Target folder path: Where to store configuration files (default: ~/accelerator)
   • Azure login: If not already logged in, you’ll be prompted to enter your Tenant ID and authenticate via device code
   • Infrastructure as Code type: Choose between Terraform or Bicep
   • Version Control System: Choose GitHub, Azure DevOps, or Local
   • Terraform scenario: If using Terraform, select from available scenarios (1-9)
   • Configuration values: Interactive prompts for bootstrap settings with:
     • Descriptions and help links for each input
     • Selection lists for Azure regions (with [AZ] indicator for Availability Zone support)
     • Selection lists for management groups and subscriptions
     • GUID validation for subscription and tenant IDs

4. After configuration, the wizard offers to open VS Code for final review of your configuration files. You’ll need to update your platform landing zone config file at this stage before proceeding.

5. Type yes when prompted to continue with deployment, or no to exit and configure later.

6. Once it generates the plan, hit enter to deploy the bootstrap.

   Tip

   You can now update your Azure Landing Zone Terraform Accelerator Runner Registration GitHub PAT (token-2) to restrict it to the main repository created by the bootstrap.

7. For Bicep only, clone your newly created repository to your local machine and make any changes required to the parameter files. See the Bicep getting started guide for more information on customizing the parameter files. Commit and push any changes to your repository. For the local file system option, you can make changes directly in the output folder.

Now head to Phase 3.