Opscraft
Azure for AWS engineers · Lesson 4 of 9 · 4 min read

Networking

Virtual networks and filtering

  • VNet (≈ VPC) — address space, regional, divided into subnets. Unlike AWS, subnets span all availability zones in the region (not per-AZ).
  • Network Security Groups (NSGs) (≈ security groups + NACLs): allow/deny rules evaluated by priority — lowest number first, first match wins; associated with subnets and/or NICs (both apply). Rules are stateful. Default rules allow VNet-internal traffic and outbound internet, deny inbound from the internet.
  • Service tags (Internet, VirtualNetwork, AzureLoadBalancer, Storage.CentralIndia) — named groups of Microsoft IP ranges usable in rules (≈ AWS managed prefix lists).
  • Application Security Groups (ASGs) — group NICs by role and reference them in NSG rules (≈ referencing a security group in another SG rule).
  • Route tables / User-Defined Routes (UDRs) — override system routes, e.g. send 0.0.0.0/0 through Azure Firewall.
Enlarge diagramVNET 10.30.0.0/16 · CENTRAL INDIAsnet-aks10.30.0.0/20 · NSGsnet-db10.30.16.0/24 · NSGsnet-peprivate endpointszones 1, 2 and 3every subnet spans all three zones (in AWS, a subnet lives in one AZ)
Figure 1. An Azure VNet differs from a VPC in one important way: subnets span all zones in the region.
Swipe sideways to see all of it, or tap to open it full screen.

Connectivity

Azure AWS equivalent Notes
VNet peering (regional/global) VPC peering Non-transitive by default; "gateway transit" allows sharing a hub's VPN gateway
Hub-and-spoke / Virtual WAN Transit Gateway designs Hub VNet hosts firewall, gateways, shared services; spokes peer to the hub; UDRs force traffic through the hub firewall
VPN Gateway Site-to-Site VPN / VGW IPsec to on-prem
ExpressRoute Direct Connect Private circuits
NAT Gateway NAT gateway Outbound SNAT for subnets
Azure Firewall AWS Network Firewall Stateful managed firewall
Private Endpoint (Private Link) Interface VPC endpoint / PrivateLink A NIC with a private IP for a PaaS resource (storage account, SQL, Key Vault); combine with Private DNS zones (privatelink.blob.core.windows.net)
Service Endpoint Gateway endpoint (loosely) Optimised route to PaaS over the backbone; the PaaS public endpoint is still used but can be restricted to the subnet
Azure DNS / Private DNS zones Route 53 public/private hosted zones Private zones linked to VNets
Azure DNS Private Resolver Route 53 Resolver endpoints Hybrid DNS forwarding
Enlarge diagramHUB VNETAzure FirewallVPN / ExpressRoute GWDNS Private Resolverspoke: shop-prodpeered to hubspoke: shop-devpeered to hubon-premisesExpressRoute
Figure 2. Hub-and-spoke on Azure: shared firewall and gateways in the hub; workload VNets peer to it and route through the firewall.
Swipe sideways to see all of it, or tap to open it full screen.

Load balancing family

Service Layer / scope AWS analogue
Azure Load Balancer L4, regional NLB
Application Gateway (+ WAF) L7, regional ALB (+ WAF)
Azure Front Door L7, global, CDN + WAF + anycast CloudFront + Global Accelerator + WAF
Traffic Manager DNS-based global routing (priority, weighted, performance, geographic) Route 53 routing policies
Enlarge diagramLoad BalancerL4, regional · ≈ NLBApplication GatewayL7 + WAF, regional · ≈ ALBFront DoorL7 global, CDN + WAF · ≈ CloudFrontTraffic ManagerDNS-based global · ≈ Route 53 routing
Figure 3. Azure load balancing, by layer and reach.
Swipe sideways to see all of it, or tap to open it full screen.