In order to start deploying your with CAF landing zones, you need an Azure subscription (Trial, MSDN, etc.) and you need to install the following components on your machine:
You can deploy it easily on Windows and MacOS with the following software managers:
| MacOS | Windows |
|---|---|
brew cask install visual-studio-code docker brew install git |
Install Chocolatey (https://chocolatey.org/docs/installation) choco install git vscode docker-desktop |
Once installed, open Visual Studio Code and install "Remote Development" extension as follow: 
Cloning your first repository:
git clone https://github.com/Azure/caf-terraform-landingzones.gitOpen the repository you've just cloned in Visual Studio Code, click on the lower bar, green sign and in the palette opening on the top of Visual Studio Code Window, select "Open Folder in container" or "Reopen in container"
This should take a while, in the meantime, feel free to click on Details to see the container being downloaded from the registry and being connected to yur local environment:
You will have to accept local mapping to your filesystem when Docker prompts you (here's how you reconfigure Docker Desktop to allow fileshares ), so that you can access your files from your container.
After a while, your environment is ready, note on the lower left part of Visual Studio Code, that you are now in your Azure CAF rover, which is your environment to use Azure landing zones.
You must be authenticated first: For that we will rely on Azure authentication as completed by Azure Cli, via browser method:
rover loginWe recommend that you verify the output of the login and make sure the subscription selected by default is the one you want to work on. If not, you can use the following switch:
az account set --subscription <subscription_GUID>On the first run, you need to use the launchpad to create the foundations for Terraform environment. This will set storage accounts to store the state files, and key vaults to get you started with a secure environment. It can eventually be upgraded to support your DevOps environment (pipelines, etc.)
You can find more information on the launchpad settings Here
rover -lz /tf/caf/landingzones/caf_launchpad \
-launchpad \
-var-folder /tf/caf/landingzones/caf_launchpad/scenario/100 \
-a applyNext step is to deploy the foundations (this typically could include management groups, policies, etc.). We can start with it empty, and enrich it later.
You can find more information on the launchpad settings Here
Get started with the basic foundations:
rover -lz /tf/caf/landingzones/caf_foundations \
-level level1 \
-a applyYou can deploy one of the typical Azure network topologies (hub, hub and spoke, Virtual WAN).
Have a look at the example scenario Here and pick one you want to deploy.
You can deploy a simple hub networking using:
rover -lz /tf/caf/landingzones/caf_networking \
-level level2 \
-var-folder /tf/caf/landingzones/caf_networking/scenario/100-single-region-hub \
-a applyOnce you are done testing, just use the same commands as before, juste replace the last line -a apply by -a destroy.
If you are using previous version of Azure landing zones (v1.0.1912), since we migrated to use new version of the rover, which uses non-root containers, you will have to re-create your volumes. You can achieve that running the following commands:
# To list all Dev Container volumes
docker volume ls -f label=caf
# To cleanup de Dev Container volumes make sure there is not running or stopped containers
docker ps
docker ps -a
# To cleanup a specific Dev Container
docker volume rm -f $(docker volume ls -f label=com.docker.compose.project=landingzones_devcontainer)
# To cleanup all Dev Containers
docker volume rm -f $(docker volume ls -f label=caf)You can also purge Docker cache running the following command:
docker system prune -aHappy deployment with Azure landing zones, let us know your feedback and how you need it to evolve!