Ability to connection Azure Virtual Network Gateway to AWS Transit Gateway through VPN
Ability to connect Azure VNet to AWS VPC through Azure Virtual Network Gateway and AWS Transit Gateway through VPN connection with BGP. Found 169.x.x.x AWS use for tunnel IP in routed VPN but Azure uses it for reserved range and that causes conflict right now.
Vijay Thakorlal commented
I would support this too, we have the same requirement but for GCP. This prevents us from having higher availability dynamic tunnels.
Any update or workaround on this having the same issue with Virtual Hub Site to site vpn and with AWS regular Site to site connections.
AWS and Google Cloud both use 169 as the inside CIDR and Azure does not let override / use that range.