Phase 3 - Run

Phase 3 of the accelerator is to run pipeline. Follow the steps below to do that.

Now you have created your bootstrapped environment you can deploy you Azure landing zone by triggering the continuous delivery pipeline in your version control system.

If you encounter permission errors while running the pipelines, please note that it may take some time for permissions to fully propagate. Although the pipelines include retry logic to manage this, it can sometimes take up to 30 minutes for the permissions to take effect.

1. Navigate to dev.azure.com and sign in to your organization.
2. Navigate to your project.
3. Click Pipelines in the left navigation.
4. Click the 02 Azure Landing Zones Continuous Delivery pipeline.
5. Click Run pipeline in the top right.
6. Take the defaults and click Run.
7. Your pipeline will run a plan.
8. If you provided apply_approvers to the bootstrap, it will prompt you to approve the apply stage.
9. Your pipeline will run an apply and deploy an Azure landing zone based on the starter module you choose.

1. Navigate to github.com.
2. Navigate to your repository.
3. Click Actions in the top navigation.
4. Click the 02 Azure Landing Zones Continuous Delivery pipeline in the left navigation.
5. Click Run workflow in the top right, then keep the default branch and click Run workflow.
6. Your pipeline will run a plan.
7. If you provided apply_approvers to the bootstrap, it will prompt you to approve the apply job.
8. Your pipeline will run an apply and deploy an Azure landing zone based on the starter module you choose.

Follow the steps below to deploy the landing zone locally. If you want to hook it up to you custom version control system, follow their documentation on how to that.

The Bicep option outputs a deploy-local.ps1 file that you can use to deploy the ALZ.

NOTE: If you set the grant_permissions_to_current_user input to false in the bootstrap, you will need to set permissions on your management group, subscriptions and storage account before the commands will succeed.

1. Ensure you have the latest versions of the AZ PowerShell Module and Bicep installed.
2. Open a new PowerShell Core (pwsh) terminal or use the one you already have open.
3. Navigate to the directory shown in the module_output_directory_path output from the bootstrap.
4. Login to Azure using Connect-AzAccount -TenantId 00000000-0000-0000-0000-000000000000 -SubscriptionId 00000000-0000-0000-0000-000000000000.
5. (Optional) Examine the ./scripts/deploy-local.ps1 to understand what it is doing.
6. Run ./scripts/deploy-local.ps1.
7. A what if will run and then you’ll be prompted to check it and run the deploy.
8. Type yes and hit enter to run the deploy.
9. The ALZ will now be deployed, this may take some time.

The Terraform option outputs a deploy-local.ps1 file that you can use to deploy the ALZ.

NOTE: If you set the grant_permissions_to_current_user input to false in the bootstrap, you will need to set permissions on your management group, subscriptions and storage account before the commands will succeed.

1. Open a new PowerShell Core (pwsh) terminal or use the one you already have open.
2. Navigate to the directory shown in the module_output_directory_path output from the bootstrap.
3. (Optional) Ensure you are still logged in to Azure using az login --tenant 00000000-0000-0000-0000-000000000000.
4. (Optional) Connect to your target subscription using az account set --subscription 00000000-0000-0000-0000-000000000000.
5. (Optional) Examine the ./scripts/deploy-local.ps1 to understand what it is doing.
6. Run ./scripts/deploy-local.ps1.
7. A plan will run and then you’ll be prompted to check it and run the deploy.
8. Type yes and hit enter to run the deploy.
9. The ALZ will now be deployed, this may take some time.

This concludes the accelerator. You now have a fully deployed Azure landing zone. If you have any issues, please raise them in the GitHub issues.