Landing zone considerations
A landing zone is the basic building block of any cloud adoption environment. The term landing zone refers to an environment that's been provisioned and prepared to host workloads in a cloud environment like Azure. A fully functioning landing zone is the final deliverable of any iteration of the Cloud Adoption Framework's Ready methodology.
This image shows the major considerations for implementing any landing zone deployment. The considerations can be broken into three categories or types of considerations: hosting, Azure fundamentals, and governance.
All landing zones provide structure for hosting options. The structure is created explicitly through governance controls or organically through the adoption of services within the landing zone. The following articles can help you make decisions that will be reflected in the blueprint or other automation scripts that create your landing zone:
- Compute decisions. To minimize operational complexity, align compute options with the purpose of the landing zone. This decision can be enforced by using automation toolchains, like Azure Policy initiatives and landing zone blueprints.
- Storage decisions. Choose the right Azure Storage solution to support your workload requirements.
- Networking decisions. Choose the networking services, tools, and architectures to support your organization's workload, governance, and connectivity requirements.
- Database decisions. Determine which database technology is best suited for your workload requirements.
Each landing zone is part of a broader solution for organizing resources across a cloud environment. Azure fundamentals are the foundational building blocks for organization.
- Azure fundamental concepts. Learn fundamental concepts and terms that are used to organize resources in Azure, and how the concepts relate to one another.
- Resource organization decision guide. When you understand each of the fundamentals, the resource organization decision guide can help you make decisions that shape the landing zone.
The Cloud Adoption Framework's Govern methodologies establish a process for governing the environment as a whole. However, there are many use cases that might require you to make governance decisions on a per-landing zone basis. In many scenarios, governance baselines are enforced on a per-landing zone basis, even though the baselines are established holistically. It's true for the first few landing zones that an organization deploys.
The following articles can help you make governance-related decisions about your landing zone. You can factor each decision into your governance baselines.
- Cost requirements. Based on an organization's motivation for cloud adoption and operational commitments made about its environment, various cost management configurations might need to be changed for the landing zone.
- Monitoring decisions. Depending on the operational requirements for a landing zone, various monitoring tools can be deployed. The monitoring decisions article can help you determine the most appropriate tools to deploy.
- Using role-based access control. Azure role-based access control (RBAC) offers fine-grained, group-based access management for resources that are organized around user roles.
- Policy decisions. Azure Blueprint samples provide premade compliance blueprints, each with predefined policy initiatives. Policy decisions help inform a selection of the best blueprint or policy initiative based on your requirements and constraints.
- Create hybrid cloud consistency. Create hybrid cloud solutions that give your organization the benefits of cloud innovation while maintaining many of the conveniences of on-premises management.