Engineering Camp Azure Enterprise Architecture Landing Zones — What’s That All About? Alexander Eimer [email protected] 

No content

The cloud is like an undeveloped plot of land. And before a functioning city can emerge, you need planning, infrastructure, and clear regulations. 

Steps to build our Smart City ● Development Plan Rules, Governance, Process ● Building Codes Materials, Structural Integrity, Traffic Planning ● Initial Infrastructure Roads, Water, Electricity ● Construction Automation Robots, Self-Driving Trucks, Exo-Scelets 

Azure Cloud Adoption Framework (CAF) 

What is the CAF? ● Cloud Adoption Framework (CAF) ● High-Level strategy and process to introduce the Azure Cloud ● Organizational approach ● End-to-End guidance for a sustainable cloud adoption 

CAF process https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/overview 

Cloud Adoption Scenarios https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/scenarios/ 

Cloud Adoption Scenarios https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/scenarios/ ● AI adoption ● Azure VMware Solution ● Cloud-scale analytics ● High-performance computing ● Hybrid and multicloud ● Modern application platform ● Oracle ● SAP ● Virtual Desktops ● Defense Goal: Accelerate cloud adoption journey 

Cloud Adoption Scenario components ● CAF itself ● Microsoft Learn Training Role-based training to up-skill your personnel ● Reference Architectures Templates for common technical scenarios ● Well-Architected Framework Guides workload owners ● Best Practices Guidelines for efficient solutions ● Featured Azure products Use products that are known to be a good match for your strategy 

Steps to build our Smart City ● Development Plan ✅ Rules, Governance, Process Azure CAF ● Building Codes Materials, Structural Integrity, Traffic Planning ● Initial Infrastructure Roads, Water, Electricity ● Construction Automation Robots, Self-Driving Trucks, Exo-Scelets 

Well-Architected Framework 

What is the Well-Architected Framework? ● Goal: Scalable Cloud Infrastructure ● Quality-driven tenets, architectural decision points, and review tools to help solution architects ● Structured into Pillars ○ and Design Principles ⇒ Guide to decision-making ○ and Best Practices ⇒ Concrete implementation suggestions for Design Principles Best Practice Areas Questions Best Practices Pillars Design Principles Operational Excellence Security Reliability Performance Efficiency Cost Optimization 

Content of the Azure WAF ● Reliability Resiliency, availability, recovery ● Security Data protection, threat detection, and mitigation ● Cost Optimization Cost modeling, budgets, reduce waste ● Operational Excellence Holistic observability, DevOps practices ● Performance Efficiency Scalability, load testing Design Principles ● Develop cost-management discipline ● Design with a cost-efficiency mindset ● Design for usage optimization ● Design for rate optimization ● Monitor and optimize over time Recommendation CO:04 Set spending guardrails Guardrails should include release gates, governance policies, resource limits, and access controls. Prioritize platform automation over manual processes. 

Attention! What about AWS and GCP? https://www.embarc.de/well-architected-cloud-ueberblick/ AWS Azure Google Cloud Name Pillars - Operational Excellence - Security - Reliability - Performance Efficiency - Cost Optimization Pillar “Sustainability” Pillar “System Design” Related Frameworks AWS Well-Architected Framework Azure Well-Architected Framework Google Cloud Architecture Framework ❌ ✅ ✅ ✅ ✅ ✅ ❌ ❌ ❌ AWS Cloud Adoption Framework Microsoft Cloud Adoption Framework for Azure Google Cloud Adoption Framework 

Steps to build our Smart City ● Development Plan ✅ Rules, Governance, Process Azure CAF ● Building Codes ✅ Materials, Structural Integrity, Traffic Planning Well-Architected Framework ● Initial Infrastructure Roads, Water, Electricity ● Construction Automation Robots, Self-Driving Trucks, Exo-Scelets 

Landing Zones 

What is an Azure Landing Zone? Part of the CAF in the “READY” stage Technical blueprint to implement Best Practices of Well-Architected Framework 

Landing Zone Types ● Platform landing zone ⇒ 3 Azure infrastructure LZs ○ Identity subscription ○ Management subscription ○ Connectivity subscription ● Application landing zone ⇒ Ready to use environment ○ integrates into Platform Landingzone ○ Prepares ground for application-team 

https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/landing-zone/ 

Steps to build our Smart City ● Development Plan ✅ Rules, Governance, Process Azure CAF ● Building Codes ✅ Materials, Structural Integrity, Traffic Planning Well-Architected Framework ● Initial Infrastructure ✅ Roads, Water, Electricity Landing Zones ● Construction Automation Robots, Self-Driving Trucks, Exo-Scelets 

Platform Engineering & Developer Experience 

Goals: Platform Engineering ● App development teams are customer of a PE product ● App teams can focus on building software ● Provide opinionated standardized solutions ● Encapsulate complexity for the app team ● Scalability: A small PE team can manage many instances via automation ● Ensures consistent, repeatable deployments without config drift ● Ensure compliance and governance ● Increase DX with e.g. golden paths and documentation ● Enables potential self-service 

PE x DX = 😻 Increasing the Developer Experience is a key goal of Platform Engineering 

How to PE with Landing Zones? ● IDPs are built on the Landing Zone concept ● Infrastructure as Code (IaC) is a must have ○ for all Landing Zones ○ for all IDPs building on those Landing Zones ● Build PE teams from the beginning of your journey 

Steps to build our Smart City ● Development Plan ✅ Rules, Governance, Process Azure CAF ● Building Codes ✅ Materials, Structural Integrity, Traffic Planning Well-Architected Framework ● Initial Infrastructure ✅ Roads, Water, Electricity Landing Zones ● Construction Automation ✅ Robots, Self-Driving Trucks, Exo-Scelets Platform Engineering / Developer Experience 

Do these blueprints work across different cities (cloud providers)? ➡ Vendor Lock-In? 

CAF: Yes you can… The Cloud Adoption Framework provides technical guidance for Microsoft Azure. Enterprise customers might still be trying to select a cloud vendor, or might have an intentional multicloud strategy. For these situations, the framework provides cloud-agnostic guidance for strategic decisions whenever possible. https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/overview 

CAF: …, but But to avoid lock-in, organizations are required to limit their vision for cloud adoption. Many of the most beneficial products and features in a cloud provider are not portable to other cloud providers. To achieve portability and minimize lock-in, organizations are often required to limit cloud adoption to basic infrastructure as a service (IaaS) capabilities, or invest heavily in the use of cloud-native technologies like containers or Kubernetes. https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/scenarios/hybrid/ 

CAF Scenario: hybrid and multicloud There is a CAF scenario for Multi and Hybridcloud. It promotes a “Unified Operations” pattern. You should have one primary cloud provider. It has many notices on pitfalls to avoid… https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/scenarios/hybrid/ 

Should I implement Multicloud? Adopting a cloud is also an organisational change. People need to be educated. Infrastructure like networking is per provider. Doing so for multiple provider is more expensive. Lock-In is not per-se a bad thing. If you run multicloud, there should be a business value behind it! 

Q & A