Solutions for Overlapping IP addresses in Azure (VPN Gateway NAT / Private Link Service)

In this video we unpack the semi-common problem of overlapping IP addresses when connecting to other companies from Microsoft Azure. We then propose, explain and give a technical demonstration of two solutions. Number one uses Azure VPN Gateway NAT feature, and number two uses the IP agnostic nature of Azure Private Link Service. Links mentioned in the video are included below. Some excellent labs by fellow MSFT Azure Networking GBB: https://github.com/Danieleg82/AzureVPN-NAT https://github.com/dmauser/azure-vpn-s2s-nat Docs: https://docs.microsoft.com/en-us/azure/private-link/private-link-service-overview https://docs.microsoft.com/en-us/azure/vpn-gateway/nat-overview https://docs.microsoft.com/en-us/azure/virtual-wan/nat-rules-vpn-gateway Tip: If you are building this solution in Azure make sure you pay special attention to NSG and UDR (they need to take in to consideration the NAT ranges in play) 00:00 Introduction 01:00 Base lab topology 02:22 Spoke VNet with overlapping IP address space 04:04 Additional context and scope 04:55 Problematic BGP and effective routes analysis 06:00 Azure VPN Gateway NAT, solution and config 09:50 Azure VPN Gateway NAT, verification and demo 12:30 Azure VPN Gateway NAT, packet walk 16:00 Azure VPN Gateway NAT, Azure monitor NAT metrics 16:25 Private Link Service, solution and config 22:30 Private Link Service, verification and packet walk 24:50 Conclusion and recommendations