Hub-spoke virtual networks in Azure
summary
Compares Azure service endpoints (backbone routing, no extra cost) with private endpoints cost extra and create one-way private NICs that expose internal IPs for each resource, explains private DNS zones and the frequent pitfall that must link private DNS zones to vnets or VMs resolve public IPs, shows hub‑spoke design using VNet peering, Azure Firewall as virtual network appliance with user‑defined routes to force hub transit, warns peering and endpoint egress incur charges and DNS changes often require VM reboots.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 1:05Speaker intro
- 2:32What this session covers and Azure networking basics
- 3:56IP range mistakes
- 4:17Azure networking history
- 6:07Service endpoints for security
- 7:30Service endpoints demo
- 12:17Private endpoints vs service endpoints
- 13:41How private endpoints work
- 16:20Private endpoints cost
- 17:44DNS in virtual networks
- 18:26Private DNS zones
- 22:25Custom DNS pitfalls
- 26:04Pairing virtual networks
- 27:52Azure Virtual Network Manager
- 28:54Virtual network pairing basics
- 31:50DNS in paired networks
- 32:53Hub-spoke architecture
- 35:23Network appliances in hub-spoke
- 37:29User-defined routes
- 39:35Scaling DNS in hub-spoke
- 41:26DNS server config
- 43:35Summary
related talks
27mKeynote: Container Networking
41mBuilding a solid foundation on Azure: Landing Zones best-practices
59mBuilding Resilient Applications In Microsoft Azure
28mCase Study: Integrating Azure IPv6 PrivateLink with Kubernetes
01h 00mBuilding Resilient Applications In Microsoft Azure
36mIntro: Virtual Kubelet
36mIntro: Virtual Kubelet
31mVirtual What? Virtual Kubelet vs. Virtual Node