Azure Gateway Load Balancer

Brass Contributor

Hello Folk's 


I am back with my new topic in Azure Discussion space. Today I will discuss a topic related to networking ,  will discuss about Azure Load Balancer (ALB) . Today I will discuss on the following things - 


1) What is Azure Gateway Load Balancer 

2) What are the benefits of Gateway Load Balancer 

3) Why we use Azure Gateway Load Balancer

4) What are the updates related to Gateway Load Balancer.


So Let's Go !!!


What is Azure Gateway Load Balancer 


Gateway Load Balancer it is just a high version of Azure Load Balancer with third party integrations and some advanced networking  concepts. With the the help of this you can easily deploy and maintain Network Appliances in Azure . It just requires a click to enable a Gateway Load Balancer .

With this , you can easily add or remove network functionality. With this technology you can easily route traffic to your appliance rather than directly moving traffic to your Infra.

It maintains flow stickiness to a specific instance in the backend pool along with flow symmetry .



What are the benefits of Gateway Load Balancer 

  •  You can easily integrate your virtual appliance with it
  • You can scale it , while maintaining costs
  • Interlink applications across various regions 

It can be attached to a standard public load balancer. Once attached to it  on a virtual machine, no additional configuration is needed to ensure traffic from the application endpoint.



Why we use Azure Gateway Load Balancer 


Gateway Load Balancer easily helps to deploy , scale and integrate your third party network virtual appliance  . It gives you one gateway for distributing traffic across multiple virtual appliances while scaling them up or down, based on demand. 


You can use your appliances on a different scenario such as in - 

  • Firewall
  • IDPS
  • Traffic monitoring and mirroring
  • Also help in DDOS attacks
  • Custom appliances across your network


What are the updates related to Gateway Load Balancer 


Gateway load balancer borrows a majority of the same concepts as the Standard Load Balancers that customers are familiar with today. As you can compare the  components like Frontend IPs, load balancing rules, backend pools, health probes, and metrics, but here you will get to  see a new component unique to Load Balancer ie VXLAN tunnel interfaces.

It is an encapsulation protocol utilized by GWLB. This allows  encapsulation and decapsulation with the help of its  headers as they provide  the appropriate data path, all while maintaining their original source IP and also a component known as flow symmetry which does not require   (SNAT) or other things  like user-defined routes (UDRs).

The VXLAN tunnel interfaces are configured as part of the Load Balancers  back-end pool and enable the network virtual appliances to isolate “untrusted” traffic from “trusted” traffic.

Tunnel interfaces can either be internal or external and each backend pool can have up to two tunnel interfaces.

Typically, this ex traffic is used for “untrusted” traffic—traffic coming from the internet and headed to the appliance. Correspondingly, the internal interface is used for “trusted” traffic—traffic going from your appliances to your application.

They are now generally available in all region and you can have a try in China region also.



Thank you !!!

3 Replies
best response confirmed by Shashwat3105 (Brass Contributor)

@A1 thanks...for this.

@Shashwat3105 Hello! Please only post Tech Community website related questions in the Tech Community discussion space. This is the second time you have posted off-topic in this space (we moved your prior post to the Azure Architecture space and responded indicated we'd done so) and if you continue to do so, we may have to take further action. 


I'm moving this post to the Azure Networking discussion space. Please post Azure Networking-related posts herein the future. 



1 best response

Accepted Solutions
best response confirmed by Shashwat3105 (Brass Contributor)

@A1 thanks...for this.

View solution in original post