Can I use Azure GWLB solution with NVA for the Internet Outbound Traffic?

Hi @Rangaraj Gunasekaran

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

• You need an SLB with outbound rules configured. These rules specify which outbound traffic from your W365 VMs should be directed to the GWLB. You can set outbound rules to send all internet-bound traffic to the GWLB or define more specific rules.
• The GWLB distributes the outbound traffic across your pool of NVAs. This distribution is based on the GWLB configuration. This allows you to use your firewalls in an active/active configuration, maximizing throughput and redundancy.
• For your reference: https://learn.microsoft.com/en-us/azure/load-balancer/gateway-overview#:~:text=Gateway%20Load%20Balancer%20supports%20both%20inbound%20and%20outbound%20traffic%20inspection.%20For%20inserting%20NVAs%20in%20the%20path%20of%20outbound%20traffic%20with%20Standard%20Load%20Balancer%2C%20Gateway%20Load%20Balancer%20must%20be%20chained%20to%20the%20frontend%20IP%20configurations%20selected%20in%20the%20configured%20outbound%20rules.
• The NVA inspect the traffic, apply security policies, and perform any other required functions. For your reference: https://learn.microsoft.com/en-us/azure/architecture/networking/guide/nva-ha
• After inspection, the NVA forward the traffic to the internet. This typically happens via a default route on the NVA pointing to the internet or an Azure NAT Gateway/Public IP.
• Return traffic from the internet follows the reverse path, being inspected by the same NVA that handled the outbound request. GWLB ensures session stickiness to maintain flow affinity.
• Your Palo Alto firewalls need to be configured to accept and process traffic from the GWLB. They also need to have a route to the internet, and they must not perform NAT unless specifically required. The GWLB preserves the original source IP, which is essential for proper return traffic handling. The firewalls should focus on security functions, not NAT.
• You'll need to create a GWLB and configure a backend pool containing your NVAs. The health probes for the backend pool are essential to ensure that the GWLB only sends traffic to healthy firewalls. A TCP health probe on a port that the firewall actively listens on is recommended.
•  The GWLB automatically scales to handle increased traffic. Make sure that your NVAs are also configured to scale appropriately to meet demand.
• For your reference: https://learn.microsoft.com/en-us/azure/load-balancer/gateway-overview#:~:text=You%20can%20insert,Custom%20appliances
• Deploy your NVAs in an Availability Set or across Availability Zones for high availability. Cross verify again all your routing tables (UDRs, NVA routing) to make sure that the traffic flows as expected.

I hope this has been helpful!

Your feedback is important so please accept an answer if correct. Original posters help the community find answers faster by identifying the correct answer. Here is how.

If you still have questions, please let us know what is needed in the comments below so the question can be answered.

Thanks,

Sai.

Hi @Rangaraj Gunasekaran

Just checking in to see if you have got a chance to see my response to your question in resolving the issue.

If you are still facing any further issues, please let us know in the comments below so that we can address them.

Hi @Rangaraj Gunasekaran

Just checking in to see if you have got a chance to see my response to your question in resolving the issue.

If you are still facing any further issues, please let us know in the comments below so that we can address them.

Sai,
I don't think your answer is correct.
The way GWLB works is that it needs to be plugged into either the frontend IP of a public Standard LB, or the public NIC of a VM.

Check this document: https://learn.microsoft.com/en-us/azure/load-balancer/gateway-overview

see the paragraph below:

Gateway Load Balancer supports both inbound and outbound traffic inspection. For inserting NVAs in the path of outbound traffic with Standard Load Balancer, Gateway Load Balancer must be chained to the frontend IP configurations selected in the configured outbound rules.

See, you still need a Standard LB. A GWLB alone is not going to work.

Hi @Rangaraj Gunasekaran

We apologize for not providing an answer up to your expectations and for any inconvenience this may have caused.

Yes, A GWLB cannot directly handle outbound internet traffic from VMs (including W365 VMs) without being chained to a SLB.

You need a SLB with outbound rules configured. These rules define which outbound traffic from your W365 VMs should be sent to the GWLB.  You can configure outbound rules to send all internet-bound traffic to the GWLB, or you can define more specific rules.

The GWLB is then chained to the frontend IP of the SLB.  This is the key connection. The SLB sends traffic that matches its outbound rules to the GWLB's frontend IP.

The GWLB has a backend pool consisting of your Palo Alto NVAs. The GWLB distributes the traffic it receives from the SLB across these NVAs for inspection. Please refer the document.

W365 VMs to SLB: Your W365 VMs need a UDR that directs internet-bound traffic to the frontend IP address of the Standard Load Balancer.

SLB to GWLB: This is the automatic chaining and no UDR is needed here. Traffic matching the SLB outbound rules is automatically forwarded to the GWLB.

GWLB to NVAs: The GWLB handles this distribution.

The return traffic from the internet follows the reverse path.  The GWLB maintains session affinity, ensuring that return traffic is sent to the same NVA that handled the outbound request.

Kindly let us know if the above helps or you need further assistance on this issue.