- Migration & Assessment
- Networking
- Landing Zone & Governance
Azure Landing Zone and VMware Lift & Shift migration
CAF hub & spoke landing zone, NVA firewall, zone-redundant domain controllers and wave-based Azure Migrate migration, including a SQL Server Always On cluster.
- Industry
- Transport & mobility
- Scope
- Up to 48 servers · 29 migrated VMs
- Role
- Architect · team delivery
- Complexity
- High
As Cloud Solution Architect I led the design of the Azure landing zone for a transport operator; together with the team we then carried the delivery through to the Lift & Shift migration of workloads from VMware. The journey covered a CAF subscription model, hub & spoke networking with an NVA firewall and site-to-site VPN, zone-redundant domain controllers and Azure Migrate migration by application islands and weekly waves.
- Migrated VMs
- 29
- SQL availability groups
- 11
- CAF subscriptions
- 4
- Azure Landing Zone
- Cloud Adoption Framework
- Azure Migrate
- Hub & Spoke
- WatchGuard Firebox Cloud
- Site-to-Site VPN
- NSG / ASG
- Azure Bastion
- +6
Challenge, solution and outcomes
The challenge
- Build a Cloud Adoption Framework-governed landing zone ready for both migrated and cloud-native workloads.
- Migrate 29 heterogeneous VMs (Windows Server and Linux) respecting dependencies: about 70% during business hours and 30% outside.
- Rebuild a SQL Server Always On cluster with 11 availability groups and 12 listeners in Azure while keeping high availability.
The solution
- CAF landing zone across 4 subscriptions (management, identity, connectivity, application) with hub & spoke: 5 VNets, 8 subnets and Azure Bastion.
- NVA firewall (WatchGuard Firebox Cloud) in the hub VNet for symmetric control of all inbound and outbound internet traffic.
- East-west segmentation with 4 per-tier Network Security Groups and VM-based Application Security Groups.
- Domain controllers across Availability Zones on a dedicated identity subscription, following virtualized-DC best practices.
- Azure Migrate with a discovery appliance on VMware, 33 VMs assessed and migration organized into 4 application islands.
- SQL Server Always On on a Standard Azure Load Balancer with 12 frontend IPs, nodes across Availability Zones and a file share witness.
The outcomes
- Governed Azure platform ready to host the remaining on-premises infrastructure and new cloud-native workloads.
- Centralized network security: internet under perimeter firewall control, east-west segmentation and admin access through Bastion.
- Increased resilience for critical services with domain controllers and SQL nodes spread across Availability Zones.
Skills demonstrated
- Azure Landing Zones per the Cloud Adoption Framework
- Azure networking: hub & spoke, NVA, UDR, VPN, NSG/ASG
- Datacenter migration by application islands and waves
- High availability with Availability Zones and Load Balancer
- Team-based technical delivery and as-built documentation
Technology stack
- Azure Landing Zone
- Cloud Adoption Framework
- Azure Migrate
- Hub & Spoke
- WatchGuard Firebox Cloud
- Site-to-Site VPN
- NSG / ASG
- Azure Bastion
- Availability Zones
- SQL Server Always On
- Azure Load Balancer
- Active Directory
- Azure Backup
- Azure Monitor