Introducing Azure Gateway Load Balancer: Deploy and scale network virtual appliances with ease

This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.

When we announced High Availability (HA) Ports for Azure Load Balancer, we enabled you to leverage network virtual appliances with more flexibility in Azure. HA ports is a unique capability that makes network virtual appliance (NVA) flexible as you deploy them in Azure – a first in the industry, it changed how you deploy NVAs at scale.


Today, we are pleased to announce the preview of Gateway Load Balancer, a fully managed service enabling you to deploy, scale, and enhance the availability of third party NVAs in Azure, that builds on that capability. You can add your favorite third party appliance whether it is a firewall, inline DDoS appliance, deep packet inspection system, or even your own custom appliance into the network path transparently – all with a single click.


With Gateway Load Balancer, you can easily add or remove advanced network functionality without additional management overhead. You can think of Gateway LB, as providing the bump-in-the-wire technology you need to ensure all traffic to a public endpoint is first sent to the appliance before your application. What makes Gateway LB even more powerful is ensuring symmetrical flows or ensuring a consistent route to your network virtual appliance – without having to update routes manually. As a result, packets traverse the same network path in both directions to function are able to do so.



Inserting network virtual appliances in the path transparently is also known as service chaining. With Gateway LB, you can enable service chaining in Azure. Once chained to a Standard Public Load Balancer frontend or IP configuration on a virtual machine, no additional configuration is needed to ensure traffic to and from the application endpoint is sent to the Gateway LB. Traffic flows from the consumer virtual network to the provider virtual network and then returns to the consumer virtual network. Gateway Load Balancer exchanges application traffic with the appliance in it's backend pool using VXLAN encapsulation. This allows preservation of the content of the traffic. The consumer virtual network and provider virtual network can be in different subscriptions, tenants, or regions enabling greater flexibility and ease of management.


Gateway Load Balancer brings together a pass through load balancer to distribute your traffic at scale and a single entry and exit point for your traffic - with a single click. All you need to do is chain your application to a Gateway Load Balancer. You can scale up or scale down as needed. You can also leverage auto scale with virtual machine scale sets.

To get started with Gateway Load Balancer:

  1. Find your favorite virtual appliance in the Azure Marketplace
  2. Deploy the NVA instances
  3. Create a Gateway LB and place them in the backend pool
  4. Chain the Gateway LB to your Public IP or Standard Load Balancer frontend

Gateway Load Balancer Launch partners

Azure's Network Virtual Appliance partners are able to offer their managed solutions via SaaS - Software as a Service with Gateway Load Balancer. Appliance providers do not need to worry about scale, load balancing, or even availability, they can rely on Gateway LB to take care of that. Gateway Load Balancer has a rich ecosystem of partners within the Azure Marketplace available, so you can start leveraging the solution today. You can choose from a plethora of industry leading appliances in the Azure Marketplace. Here are links to their blogs to learn more.


Customers are already using Gateway LB for many scenarios - firewalls, advanced network security functions, deep packet inspection, analytics, IoT and so many more. Gateway Load Balancer is available across all Azure public regions, Government cloud regions, and China cloud regions. You can get started via the Azure Portal, CLI, PowerShell, templates, or Terraform. Learn more and deploy yours today.





REMEMBER: these articles are REPUBLISHED. Your best bet to get a reply is to follow the link at the top of the post to the ORIGINAL post! BUT you're more than welcome to start discussions here:

This site uses Akismet to reduce spam. Learn how your comment data is processed.