Azure Network Topology Document Extracts and Notes

Azure Network Topology

• Two core approaches: traditional and Azure Virtual WAN
• The above document has a topology diagram for each model.

Feature	Traditional Azure Network Topology	Azure Virtual WAN Network Topology
Highlights	Customer-managed routing and security An Azure subscription can create up to 50 vnets across all regions. Vnet Peering links two vnets either in the same region or in different regions and enables you to route traffic between them using private IP addresses (carry a nominal charge). Inbound and outbound traffic is charged at both ends of the peered networks. Network appliances such as VPN Gateway and Application Gateway that are run inside a virtual network are also charged. Azure Virtual Network Pricing	A Microsoft-managed networking service providing optimized and automated branch to branch connectivity through Azure. Virtual WAN allows customers to connect branches to each other and Azure, centralizing their network and security needs with virtual appliances such as firewalls and Azure network and security services. Azure Virtual WAN Pricing
Deployment	Customized deployment with routing and security managed by the customer Virtual Network documentation – Plan virtual networks – Tutorial: Filter network traffic with a network security group using the Azure portal	Microsoft-managed service Virtual WAN documentation – Tutorial: Create an ExpressRoute association to Virtual WAN – Azure portal – Other tutorials include site-to-site and point-to-site connections
Interconnectivity	Traffic between two virtual networks across two different Azure regions is expected. Full mesh network across all Azure regions is not required.	Global connectivity between vnets in these Azure regions and multiple on-premises locations.
IPsec Tunnels	Fewer than 30 IPsec Site-to-Site tunnels are needed.	More than 30 branch sites for native IPsec termination.
Routing Policy	Full control and granularity for manually configuring your Azure network routing policy.	Not applicable
Data Collection	Collects data from servers and Kubernetes clusters.	Collects data from servers and Kubernetes clusters.
Data Storage	Stores data in Log Analytics workspace or customer’s own storage account.	Stores data in Log Analytics workspace or customer’s own storage account.
Data Analysis and Visualization	Uses Log Analytics for analysis and visualization of collected data.	Uses Azure Monitor for analysis and visualization of collected data.

Additional Information

• Hub-spoke network topology in Azure
• Hub-spoke network topology with Azure Virtual WAN
• Patterns for inter-spoke networking

Azure Landing Zone Document Extracts and Notes

What is an Azure landing zone? – Cloud Adoption Framework

Landing zone implementation options – Cloud Adoption Framework

• Overview of landing zone options
• Deploy a migration landing zone in Azure

“A migration landing zone is an environment that’s been provisioned and prepared to host certain workloads. These workloads are being migrated from an on-premises environment into Azure.”

Deploy a CAF Foundation blueprint in Azure

“The CAF Foundation blueprint does not deploy a landing zone. Instead, it deploys the tools required to establish a governance MVP (minimum viable product) to begin developing your governance disciplines. This blueprint is designed to be additive to an existing landing zone and can be applied to the CAF Migration landing zone blueprint with a single action.”

Get help building a landing zone – Cloud Adoption Framework

“Getting your Azure landing zone (ALZ) done right and on time is important. Working with a certified Azure partner is a great way to get the support you need to build your ALZ.”

• Option 1 – use Azure Migrate and Modernize.
• Option 2 – find a partner offer for a landing zone in our marketplace.

Azure landing zone FAQ

• Which are the recommended accelerators and implementations for Azure landing zones?
• What about our management group hierarchy?