Azure CAF Landing Zone - Hub-Spoke Architecture
About This Architecture
Azure CAF hub-spoke architecture with centralized security, identity, and connectivity across multiple application subscriptions. The hub VNet (10.0.0.0/16) hosts Azure Firewall, Application Gateway, VPN Gateway, and ExpressRoute for hybrid connectivity, while identity services via Entra ID and Azure AD B2C enforce zero-trust access. Spoke VNets (App1 10.1.0.0/16, App2 10.2.0.0/16) isolate workloads with three-tier subnets, load balancers, and Azure SQL databases, all monitored by Log Analytics and Microsoft Sentinel. This topology implements Azure Cloud Adoption Framework best practices for governance, security, and scalability across enterprise environments. Fork this diagram on Diagrams.so to customize subscriptions, IP ranges, or add additional spokes for your organization's growth.
People also ask
How do I design a scalable Azure landing zone with centralized security and multiple isolated application environments?
This diagram shows the Azure CAF hub-spoke pattern: a central hub VNet hosts Azure Firewall, Application Gateway, VPN/ExpressRoute gateways, and identity services (Entra ID, Key Vault), while spoke VNets isolate applications with three-tier subnets and databases. All traffic routes through the hub for centralized security and monitoring via Microsoft Sentinel and Log Analytics.
- Domain:
- Cloud Azure
- Audience:
- Azure solutions architects designing enterprise landing zones
Generated by Diagrams.so — AI architecture diagram generator with native Draw.io output. Fork this diagram, remix it, or download as .drawio, PNG, or SVG.