Expand your landing zone

This section of the Ready methodology builds on the principles of landing zone refactoring. As outlined in that article, a refactoring approach to infrastructure as code removes blockers to business success while minimizing risk. This series of articles assumes that you've deployed your first landing zone and would now like to expand that landing zone to meet enterprise requirements.

Shared architecture principles

Expanding your landing zone provides a code-first approach to embedding the following principles into the landing zone and more broadly into your overall cloud environment.

Shared architecture principles Figure 1: Shared architecture principles.

These same architecture principles are shared by Azure Advisor, the Microsoft Azure Well-Architected Framework, and the solutions in the Azure Architecture Center.

Applying these principles to your landing zone improvements

To better align with the methodologies of the Cloud Adoption Framework, the principles above are grouped into actionable landing zone improvements:

  • Basic considerations: refactor a landing zone to refine hosting, fundamentals, and other foundational elements.
  • Operations expansions: add operations management configurations to improve performance, reliability, and operational excellence.
  • Governance expansions: add governance configurations to improve cost, reliability, security, and consistency.
  • Security expansions: add security configurations to improve protection of sensitive data and critical systems.


Adoption teams who have a midterm objective (within 24 months) to host more than 1,000 assets (applications, infrastructure, or data assets) in the cloud should consider each of these expansions early in their cloud adoption journey. For all other adoption patterns, landing zone expansions could be a parallel iteration, allowing for early business success.

Next steps

Before refactoring your first landing zone, it is important to understand test-driven development of landing zones.