I'm wondering if it's possible to add a NAT Gateway to an existing Virtual Network Gateway in Azure. I understand that the VNG is mainly for VPN or ExpressRoute connections, and it seems like NAT Gateways are solely for outbound connections from a subnet. Is there a way to configure this without disrupting existing services?
2 Answers
It's not as straightforward as it sounds! The Virtual Network Gateway (VNG) is designed for VPN or ExpressRoute, meaning it doesn't handle outbound traffic to the internet. On the other hand, a NAT Gateway is specifically for managing outbound traffic from a subnet. So, if you're looking to direct internet-bound traffic while still maintaining your existing VNG, that could be tricky.
Great question! However, it seems adding a NAT Gateway to a GatewaySubnet isn't typically supported. If your goal is to allow outbound traffic with a fixed public IP, consider using Azure Firewall or a Network Virtual Appliance (NVA) instead. You would set up a Route Table on the GatewaySubnet to guide traffic to the firewall or NVA, which can then egress via a public IP. Just a heads-up, rules will need to be in place to allow that traffic through the firewall.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures