Azure Networking Cheat Sheet

Updated 2026-04-28

Next Topic: Content Delivery Networks - CDN Cheat Sheet

Azure Networking is Microsoft's comprehensive suite of cloud networking services that enable secure connectivity, traffic management, and network security for resources deployed in Azure. Operating across 60+ global AI regions with a backbone now exceeding 18 petabits per second of WAN capacity, Azure networking provides the foundation for hybrid cloud architectures, application delivery, and zero-trust security models. As of March 31, 2026, all newly created virtual networks default to private subnets with no default outbound internet access, requiring explicit methods (NAT Gateway, Load Balancer, or Public IP) — a fundamental shift toward secure-by-default network design. New services like Azure Virtual Network Manager, DNS Security Policy with Threat Intelligence, and StandardV2 NAT Gateway continue to raise the bar for enterprise-grade networking.

What This Cheat Sheet Covers

This topic spans 14 focused tables and 118 indexed concepts. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.

Table 1: Virtual Network FoundationsTable 2: VNet Peering and ConnectivityTable 3: Hybrid Connectivity – VPNTable 4: Hybrid Connectivity – ExpressRouteTable 5: Network Security – CoreTable 6: Network Security – AdvancedTable 7: Routing and Traffic ManagementTable 8: Load Balancing – Layer 4Table 9: Load Balancing – Layer 7Table 10: Global Traffic ManagementTable 11: Content Delivery and DNSTable 12: Advanced Virtual WANTable 13: Azure Virtual Network ManagerTable 14: Network Monitoring and Diagnostics

Table 1: Virtual Network Foundations

Concept	Example	Description
Virtual Network (VNet)	`10.0.0.0/16` address space	• Isolated private network in Azure • supports custom RFC 1918 address spaces and can be segmented into subnets, peered, or connected to on-premises.
Subnet	`10.0.1.0/24`	• Subdivision of a VNet • Azure reserves 5 IPs per subnet (first 4 and last 1), so a /29 gives only 3 usable IPs.
Subnet Delegation	Subnet delegated to `Microsoft.Web/serverFarms`	• Designates a subnet for injection of a specific Azure PaaS service • the service can add its own network intent policies (routes, NSG rules) to that subnet.
Address Space	`10.0.0.0/16, 172.16.0.0/16`	• CIDR blocks defining IP ranges for a VNet • can be expanded or added after creation without downtime if the new range contains all existing subnets.
Network Interface (NIC)	`nic-vm-01` attached to VM	• Virtual network adapter attached to a VM • can have multiple IP configurations (primary + secondary private IPs) and supports accelerated networking via SR-IOV.

Table 1: Virtual Network Foundations

Concept	Example	Description
Virtual Network (VNet)	`10.0.0.0/16` address space	• Isolated private network in Azure • supports custom RFC 1918 address spaces and can be segmented into subnets, peered, or connected to on-premises.
Subnet	`10.0.1.0/24`	• Subdivision of a VNet • Azure reserves 5 IPs per subnet (first 4 and last 1), so a /29 gives only 3 usable IPs.
Subnet Delegation	Subnet delegated to `Microsoft.Web/serverFarms`	• Designates a subnet for injection of a specific Azure PaaS service • the service can add its own network intent policies (routes, NSG rules) to that subnet.
Address Space	`10.0.0.0/16, 172.16.0.0/16`	• CIDR blocks defining IP ranges for a VNet • can be expanded or added after creation without downtime if the new range contains all existing subnets.
Network Interface (NIC)	`nic-vm-01` attached to VM	• Virtual network adapter attached to a VM • can have multiple IP configurations (primary + secondary private IPs) and supports accelerated networking via SR-IOV.