What is an Azure landing zone? A guide for businesses
Many companies start in Azure with a single subscription and a handful of resources. That works well at first. Then come more systems, more teams and more requirements. Who may change what? Where may data be stored? Who pays for which service? How does the cloud connect to what stays on-premises?
If those questions are answered only once the systems are already in place, they become expensive to fix. A landing zone is Microsoft’s way of answering them up front, before the systems move in.
What is a landing zone?
A landing zone is a prepared environment in Azure where your systems can “land”. Microsoft describes it as a proven architecture for governing, securing and scaling an Azure environment with multiple subscriptions. Rules, networking, identities and monitoring are in place from the start, so every new system arrives in an environment that has already been thought through.
The term comes from the Microsoft Cloud Adoption Framework, Microsoft’s framework for adopting the cloud. There, landing zones belong to the Ready phase: the preparation before systems start moving to or being built in Azure.
An analogy: a landing zone is like the structure, power and plumbing of a building. Each tenant fits out their own space, but nobody has to run their own cables or set their own fire rules.
Two parts: the platform and the workloads
A landing zone has two parts.
The platform landing zone is the shared foundation. It holds the management group structure, the shared rules, the network that ties everything together, identity management and central monitoring. It is managed centrally, and most organizations need only one per Microsoft Entra ID tenant.
Workload landing zones (called application landing zones in some older material) are where each system runs. A system gets its own landing zone with its environments, such as development, test and production. The team that owns the system works freely there, but within the guardrails the platform sets.
That split is the point. Security, networking and cost tracking are solved once, centrally. Teams can still move fast in their own environments.
The design areas: what you need to decide
Microsoft divides the work on a landing zone into design areas. For each one you need to make a few basic decisions:
- Billing and tenant. How agreements and billing are set up and how your Microsoft Entra ID tenant is organized.
- Identity and access. Who may do what, how access is granted and how administrator accounts are protected.
- Resource organization. How management groups and subscriptions are divided, and how resources are named and tagged so that costs and ownership can be tracked.
- Network topology and connectivity. How networks in Azure connect, how traffic in and out is controlled and how the cloud connects to your on-premises environments.
- Security. How you protect data and systems, detect threats and handle incidents.
- Management. How you collect logs, monitor systems and handle backup and recovery.
- Governance. Which rules apply, such as permitted regions and required tags, and how costs are followed up.
- Platform automation and DevOps. How the environment is described as code, so it can be recreated, reviewed and changed in a controlled way.
Not every decision has to be final on day one. But the ones that are hard to change later, such as the network’s address plan, the management group structure and how access is granted, are worth thinking through properly.
When do you need a landing zone?
Microsoft describes the platform landing zone as where every landing zone starts. It is built before the workloads move in. Some signs that it is time:
- You plan to move more systems to Azure, or already have several there.
- Several teams or suppliers work in the same environment.
- You have requirements on where data is stored, who has access and how it is logged.
- Cloud costs are growing and nobody can say which services drive them.
- You want to use AI and automation, which need secure access to data from several systems.
If you only have one small system in Azure, you do not need an extensive landing zone. The basics still pay off: clear access rights, tagging for costs and a couple of rules about regions. Building on a simple foundation is much easier than cleaning up afterwards.
How to get started
Microsoft offers ready-made starting points called accelerators. The portal accelerator sets up the platform through a guided flow in the Azure portal, and Microsoft says it works best for organizations without infrastructure-as-code expertise. There is also an accelerator that builds the platform as code, with Bicep or Terraform and Microsoft’s Azure Verified Modules. According to Microsoft, accelerators are the fastest path for most organizations. The alternative is a custom build from scratch.
Whichever route you take, the work usually looks something like this:
- Map the requirements. Which systems are moving in, what are the requirements on security and data location, and how will the cloud connect to the on-premises environment?
- Decide the basic structure. Management groups, subscriptions, networking and access.
- Put rules and follow-up in place. Policies for regions and tags, budgets and cost alerts, logging and backup.
- Describe the environment as code. Then it can be reviewed, recreated and changed in a controlled way.
- Let a first system land. Pick a well-defined system, learn from the move and adjust the foundation before the next one.
Common mistakes
- Everything in one subscription. Quick at first, but it makes it hard to separate environments, access and costs.
- Access that is too broad. When everyone is an owner, it becomes impossible to see who changed what.
- Networking planned last. Overlapping addresses between the cloud and the on-premises environment can force systems to be re-addressed.
- No tagging. Without tags, costs cannot be linked to systems, teams or customers.
- Perfection before starting. A landing zone should grow with your needs. What matters is that the foundation is right, not that everything is finished.
Frequently asked questions about landing zones
Does a landing zone cost anything?
The structure itself, meaning management groups, subscriptions and policies, generally costs nothing extra. What costs money are the shared services you choose to run in the platform, such as a firewall, a VPN connection and log storage.
Is a landing zone only for large companies?
No. The scope should fit your organization. A smaller company needs fewer parts, but benefits just as much from clear access rights, cost tracking and a secure connection to the on-premises environment.
How do landing zones relate to a cloud migration?
The landing zone is the foundation the systems move to. A migration without one is often faster at first but more expensive later. Read more in our guide Cloud migration step by step.
Start with the foundation
A well-designed landing zone makes every later step easier: moving the next system, the security review and following up costs. Read more about how we work with cloud architecture and migration to Azure.
Want to discuss your environment? Book a call with our founder, and we will start with what your environment looks like today and what you want to achieve.
More articles about cloud architecture
Cloud migration step by step: from assessment to operations
How to move systems to the cloud in phases: assessment, the right path for each system, a secure foundation, migration in waves and follow-up afterwards.
· 6 min read