- Current version of the Azure CLI
- An Azure Subscription where you have 'Owner' RBAC permissions
You can deploy Mission LZ from your workstation using the command line. Some other configurations are possible, but this is the simplest path.
We highly recommend deploying from the Development Container since it comes packaged with all the right versions of the dependencies you'll need.
If you are planning to deploy from your local workstation, we recommend using the VS Code development container specified in this repository.
- The container includes all the tools and pre-requisites, but you have to build and run the container.
- If you have Docker Desktop installed, then VS Code makes the rest of it easy.
See the Development Container docs for how to configure your workstation.
If you want to deploy from the command line on your workstation but do not want to use the development container take a look at the Dockerfile and the devcontainer.json file for examples on required tools and how configure your environment.
With the environment pre-requisites out of the way, deploy the hub and spoke using the Command Line Deployment for step-by-step instructions:
Now that you have the core hub and spoke tiers deployed (Hub, Tier 0, Tier 1, Tier 2), the next step is to deploy one or more workload tiers. Misson LZ supports multiple workload tiers. See Workload Deployment for details and step-by-step instructions:
Once you have a lab deployment of Mission Landing Zone established and have decided to move forward, you will want to start planning your production deployment. We recommend reviewing the following pages during your planning phase.