Azure P2S VPN routing caveats (with multiple VNet gateways)

I’ve recently worked with a customer that had an Azure Virtual Network Gateway in place to connect their remote workers (using native P2S functionality, supported under subnet 192.168.17.0/24) to both Azure and on-premises networks. Pretty usual setup, to be fair. Let’s say:

  • Virtual Network Gateway
    • Name: vpngwA
    • Virtual Network: vnetA (172.16.0.0/16)
  • Local Network Gateway
    • Name: lngwA
    • Remote Network: 192.168.0.0/24 (using S2S connection named “s2sA”)
Continue reading “Azure P2S VPN routing caveats (with multiple VNet gateways)”