1 of 27

Cloud Adoption Framework �for �Azure Landing Zone

SEP-19-2023

2 of 27

Cloud Adoption Framework

  • Collection of best practices and guidance with rich knowledges and experience
  • Used for Cloud Architects, cloud decision-makers or who ever involved in Cloud setup and configurations of tools and resources to get started.
  • To answer questions that why you move to the cloud, what benefits the cloud can offer and the drivers for cloud adoption
  • Link: https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/

3 of 27

Cloud Adoption Framework

4 of 27

What is Azure Landing Zone

  • Environment:
    • Follow key design principles across 8 design areas
    • Enable applications:
      • Migration
      • Modernization
      • Innovation at scale

5 of 27

Subscriptions

  • AZL uses Subscriptions to isolate and to scale
    • - Application Resources: Application Landing Zones
    • - Platform Resources: Platform Landing Zones

​

​

​

6 of 27

Azure Landing Zone Architecture

  • Scalable: Apply configuration and controls subscription consistently
  • Modular: Easy to deploy and modify ALZ components as evolving.

​

​

7 of 27

8 of 27

Design Areas

1 – Azure Billing and Active Directory Tenant (A)

2 – Identity and Access Management (B)

3 – Resource Organization (C )

4 – Network topology and Connectivity

5 – Security (F)

6 – Management (D,G,H)

7 – Governance (C, D)

8 – Platform Automation and DevOps (I )

9 of 27

10 of 27

11 of 27

12 of 27

13 of 27

14 of 27

Platform LZ vs Application LZ

Platform LZ: Subscriptions provides shared services (identity, connectivity, management) to applications in Application LZ

Application LZ: subscription hosting applications (provision application using IaC and use management group to assign policies)

15 of 27

Azure Landing Zone Accelerators

  • Platform LZ Accelerator: deploy conceptual Architecture
  • You can use Bicep or Terraform
    • Link: https://learn.microsoft.com/en-us/azure/architecture/landing-zones/landing-zone-deploy#platform

​

16 of 27

Azure Landing Zone Accelerators

  • Application LZ Accelerator: deploy application landing zones
    • AKS landing zone accelerator: target AKS deployment
    • App Service landing zone accelerator: target ASEv3 based deployment
    • APIM landing zone accelerator: target APIM deployment with Azure functions as backend
    • SAP landing zone accelerator: target SAP systems deployment
    • HPC landing zone accelerator: target HPC cluster solution deployment
    • VMware landing zone accelerator: target VMWare private cloud deployment
    • Virtual Desktop landing zone accelerator: target Virtual desktop deployment
    • RedHat OpenShift landing zone accelerator: target RedHat open sources deployment
    • Azure Spring landing zone accelerator: target Sprint boot applications deployment
    • Azure Arc landing zone accelerator: target Azure-Arc servers deployment
    • Enterprise scale Citrix landing zone accelerator: target Citrix cloud deployment

​

​

​

​

​

​

17 of 27

Azure App Service LZ Accelerator

  • Modular to customize environment variables
  • Follow Design Guidelines: Multi-tenant or Single tenant App Service deployment
    • IAM
    • Network and connectivity
    • Security
    • Management
    • Governance
    • DevOps
  • Implementation to create environment for deployment and to test the deployed environments

​

18 of 27

19 of 27

20 of 27

Hub vs Spoke

  • Hub virtual network. The hub virtual network hosts shared Azure services. Workloads hosted in the spoke virtual networks can use these services. The hub virtual network is the central point of connectivity for cross-premises networks.
  • Spoke virtual networks. Spoke virtual networks isolate and manage workloads separately in each spoke. Each workload can include multiple tiers, with multiple subnets connected through Azure load balancers. Spokes can exist in different subscriptions and represent different environments, such as Production and Non-production.

​

21 of 27

Choose the landing zone for your organization�

  • Start small and expand: centralized operations, start simple build and minimal subscriptions and scale as needed, using Cloud Adoption Framework to add more best practices.
  • Enterprise-scale: Enterprise operations, Start the entire Azure tenant references regardless of scale-point, including cloud native operations, implement automation for platform and applications.

​

22 of 27

Demo

  • On Hotmail account

23 of 27

24 of 27

25 of 27

26 of 27

27 of 27

References

​

​

​