Azure Landing Zone Design

Imagine you're about to build a new city. Before constructing buildings, roads, and parks, you need to prepare the land. You lay down the infrastructure: water pipes, electricity, roads, and zoning rules. This foundational work ensures that everything you build afterward is organized, efficient, and scalable. An Azure Landing Zone works in much the same way but for cloud environments.

Our assessment for designing and delivering the Azure Landing Zone (LZ) model is structured into five key phases:

Content of the Assessment

Workshop 1: A 1.5-hour workshop involving Enfo and the customer. Focus on making decisions regarding LZ architecture and technical choices.

Initial Design: Independent work by Enfo to create the initial design of the Azure Landing Zone.

Workshop 2: Another 1.5-hour workshop with Enfo and the customer. Further decision points for refining the LZ architecture and technical choices.

Final Design: Enfo independently completes the final design. Optionally includes implementation of Infrastructure as Code (IaC).

Deliverables

• A 45-minute presentation meeting with Enfo and the customer.
• Landing Zone design documents including but not restricted to Networking and DNS, Backups for VMs and other resources, VM patching, Secret and certificate management, Logging, Cost alerting, Governance policies, DevOps agent for automated deployments, Dashboards, Azure RBAC configuration
• Standardized order form
• Landing Zone user’s manual
• Proposal for next steps to move forward with the implementation.