AWS/Azure/OpenShift Network

How To Set Up Public Load Balancer in Azure Step By Step


In this article, I will show you how to set up a public load balancer in Azure. Where it can distribute the incoming traffic over multiple servers. It will split up the load over two Virtual Machines. IPAM enables the administration and monitoring of DHCP and DNS and provides a comprehensive view of where IP addresses are used, it also collects information from domain controllers and Network Policy Servers (NPSs), and then stores that information in the Windows Internal Database.

Also here are some of my related guides: How to configure Network Load Balancing (NLB), how to create a load balancer for Azure Stack Hub, how to deploy a load balancer from scratch and adding backend servers, how to use Aws to deploy, schedule and run playbooks, how to configure azure resources with tools, how to install and configure Ansible on Ubuntu, how to install Kerberos packages in Windows via Cygwin and how to deploy Azure VMware solution private cloud.

Create Virtual Machines

We’ll create VMs in each virtual network (VNet) so that we can communicate between them.

Let’s Create 1st VM. On the Azure Portal menu tab, select Virtual machines


Select the + Create button to create virtual machine.


From the Resource group section, select create new.


Type the resource group name (rg-web) and then click OK


Instance details
Enter a virtual machine name (web1)
Region select (East US)
Availability options – select Availability set.
Availability set select to create new.


Enter a Availability set name loadbalanceset and then click OK


in the Image section, please select Windows Server 2019 Datacenter. You can select various operating systems, but the remaining steps assume you selected Windows Server 2019 Datacenter.


Administrator account
Enter a username, Password for your account.
Public inbound ports choose to allow selected ports.
Select inbound ports (HTTP, HTTPS, RDP) and then click on Review + create >


Select create


Your deployment is complete


Create the second Virtual Machine

Complete by creating the second VM by using the following changes below:

Name: Value
Resource group: rg-web
Virtual machine name: web2
Region: (US) West US
Availability options: Availability set
Availability set: loadbalanceset
Image: Windows Server 2019 Datacenter
Administrator account: username & password
Public inbound port: allow selected ports
Select inbound ports: HTTP, HTTPS, RDP
Click Create

The Virtual Machines take a few minutes to create. Now we have created both Virtual Machines (web1, web2) successfully.


Create Network Load Balancer

From the Microsoft Azure menu, select Load Balancers


Select create a load balancer


Select resource group rg-web


Kindly ensure the following details below are filled.

  • Enter the name of the Load Balancer.
  • Select Region (East US).
  • keep it Public and SKU Basic.
  • Set the Public Address.
  • Create new, enter a name lbpublicip keep it dynamic and then select Review + create >

In the window below, you can see the validation has passed. Kindly click on Create!


Now you can see the load balancer successfully created, click on lbweb


Here, I will be configuring the Health Probes for our Load Balancer. So, we can specify how many servers we want to make the Load Balancer.

In the Backend Pools, we specify the servers which we are going to use in the Load Balancer.

Backend Pools

Click on Backend Pools and then click on + Add


Enter the following information below.

  • Add backend pool wizard, Type a name
  • Virtual network (rg-web)
  • Associate to select virtual machines and then click the add button under a virtual machine.

Then add the virtual machine to the backend pool wizard. Select the VMs and then click add.


After selecting the VMs, then click on i.


The backend pool has been configured successfully. Inside Load Balancer, go to Health Probes


Click on Add

  • Enter a name to the Health Probe.
  • Protocol (HTTP)

NOTE: The interval shows that it is going to make a probing attempt at 5-second intervals. The unhealthy threshold shows that after 2 attempts of failed probe, it is going to declare it as an unhealthy server. Click ok


Health probe successfully created, click on Load Balancing Rules.


Click on + Add button


Also ensure the following parameters are filled in corrtcly.

  • Add load balancing rule wizard, The IP version is IPv4
  • Select frontend IP Address
  • The protocol is TCP, the port number is 80
  • Backend port is 80, the backend pool is the one that we have just created and the health probe is the one that we have created.
  • Session persistence is by default – None
  • Idle timeout is by default – 4 minutes.
  • Floating IP disabled. Click on OK.
  • Load Balancing Rule has been created.

Test Network Load Balancer

After remoting to both VMs. Right-click, select new, and then click text documents\ on each VM and then delete these files.


Open the text file


Type this is windows server web1. Select file and then save as.


Type index.html Save as type All Files and click save.


Select the Azure menu and then load balancers.


Click on load balancer lbweb


In the Load Balancer, Copy and paste your Public IP address, then paste it in the explorer address bar.


On the first hit, it takes me to the web1 server, then waits for some minutes again press enter key and it will open the web2 server just as it is shown below.

I hope you found this blog post helpful. Please let me know in the comment session if you have any questions.

Notify of

Inline Feedbacks
View all comments
Would love your thoughts, please comment.x