Tutorial: Load balance VMs within an availability zone by using the Azure portal
This tutorial creates a public load balancer with a zonal IP. In the tutorial, you specify a zone for your frontend and backend instances.
In this tutorial, you learn how to:
- Create a virtual network with an Azure Bastion host for management.
- Create a NAT gateway for outbound internet access of the resources in the virtual network.
- Create a load balancer with a health probe and traffic rules.
- Create zonal virtual machines (VMs) and attach them to a load balancer.
- Create a basic Internet Information Services (IIS) site.
- Test the load balancer.
For more information about availability zones and a standard load balancer, see Standard load balancer and availability zones.
- An Azure subscription
Sign in to Azure
Sign in to the Azure portal.
Create a virtual network and bastion host
In this section, you creates a virtual network with a resource subnet, an Azure Bastion subnet, and an Azure Bastion host.
Hourly pricing starts from the moment that Bastion is deployed, regardless of outbound data usage. For more information, see Pricing and SKUs. If you're deploying Bastion as part of a tutorial or test, we recommend that you delete this resource after you finish using it.
In the portal, search for and select Virtual networks.
On the Virtual networks page, select + Create.
On the Basics tab of Create virtual network, enter or select the following information:
Setting Value Project details Subscription Select your subscription. Resource group Select Create new. Enter load-balancer-rg in Name. Select OK. Instance details Name Enter lb-vnet. Region Select East US.
Select the Security tab or Next button at the bottom of the page.
Under Azure Bastion, enter or select the following information:
Setting Value Azure Bastion Enable Azure Bastion Select checkbox. Azure Bastion host name Enter lb-bastion. Azure Bastion public IP address Select Create new. Enter lb-bastion-ip in Name. Select OK.
Select the IP addresses tab, or Next at the bottom of the page.
On Create virtual network page, enter or select the following information:
Setting Value Add IPv4 address space IPv4 address space Enter 10.0.0.0/16 (65,356 addresses). Subnets Select the default subnet link to edit. Subnet template Leave the default Default. Name Enter backend-subnet. Starting address Enter 10.0.0.0. Subnet size Enter /24(256 addresses). Security NAT Gateway Select lb-nat-gateway.
Select Review + create at the bottom of the screen, and when validation passes, select Create.
Create NAT gateway
In this section, you'll create a NAT gateway for outbound internet access for resources in the virtual network. For other options for outbound rules, check out Network Address Translation (SNAT) for outbound connections
Sign in to the Azure portal.
In the search box at the top of the portal, enter NAT gateway. Select NAT gateways in the search results.
Select + Create.
In the Basics tab of Create network address translation (NAT) gateway enter or select the following information:
Setting Value Project details Subscription Select your subscription. Resource group Select Create new. Enter load-balancer-rg in Name. Select OK. Instance details NAT gateway name Enter lb-nat-gateway. Region Select East US. Availability zone Select None. Idle timeout (minutes) Enter 15.
Select the Outbound IP tab or select the Next: Outbound IP button at the bottom of the page.
Select Create a new public IP address under Public IP addresses.
Enter nat-gw-public-ip in Name in Add a public IP address.
Select the Subnet tab or select the Next: Subnet button at the bottom of the page.
On the Subnet page, for Virtual network, select lb-vnet from the dropdown.
For Subnet name, select backend-subnet.
Select the blue Review + create button at the bottom of the page, or select the Review + create tab.
Create load balancer
In this section, you create a load balancer for the virtual machines.
In the search box at the top of the portal, enter Load balancer. Select Load balancers in the search results.
In the Load balancer page, select Create or the Create load balancer button.
In the Basics tab of the Create load balancer page, enter, or select the following information:
Setting Value Project details Subscription Select your subscription. Resource group Select lb-resource-group. Instance details Name Enter load-balancer Region Select (US) East US. SKU Leave the default Standard. Type Select Public. Tier Leave the default Regional.
Select the Frontend IP configuration tab, or select the Next: Frontend IP configuration button at the bottom of the page.
In Frontend IP configuration, select + Add a frontend IP configuration.
Enter lb-frontend-IP in Name.
Select IPv4 or IPv6 for the IP version.
IPv6 isn't currently supported with Routing Preference or Cross-region load-balancing (Global Tier).
Select IP address for the IP type.
For more information on IP prefixes, see Azure Public IP address prefix.
Select Create new in Public IP address.
In Add a public IP address, enter lb-public-IP for Name.
Select Zone-redundant in Availability zone.
In regions with Availability Zones, you have the option to select no zone (default option), a specific zone, or zone-redundant. The choice will depend on your specific domain failure requirements. In regions without Availability Zones, this field won't appear. For more information on availability zones, see Availability zones overview.
Select the Next: Backend pools> button at the bottom of the page.
In the Backend pools tab, select + Add a backend pool.
Enter lb-backend-pool for Name in Add backend pool.
Select lb-VNet in Virtual network.
Select IP Address for Backend Pool Configuration and select Save.
Select the Inbound rules tab, or select the Next: Inbound rules button at the bottom of the page.
In Load balancing rule in the Inbound rules tab, select + Add a load balancing rule.
In Add load balancing rule, enter or select the following information:
Setting Value Name Enter lb-HTTP-rule IP Version Select IPv4 or IPv6 depending on your requirements. Frontend IP address Select lb-frontend-IP. Backend pool Select lb-backend-pool. Protocol Select TCP. Port Enter 80. Backend port Enter 80. Health probe Select Create new. In Name, enter lb-health-probe. Select HTTP in Protocol. Leave the rest of the defaults, and select Save. Session persistence Select None. Idle timeout (minutes) Enter 15. Enable TCP reset Select checkbox. Enable Floating IP Select checkbox. Outbound source network address translation (SNAT) Leave the default of (Recommended) Use outbound rules to provide backend pool members access to the internet.
Select the blue Review + create button at the bottom of the page.
In this example we created a NAT gateway to provide outbound Internet access. The outbound rules tab in the configuration is bypassed as it's optional and isn't needed with the NAT gateway. For more information on Azure NAT gateway, see What is Azure Virtual Network NAT? For more information about outbound connections in Azure, see Source Network Address Translation (SNAT) for outbound connections.
Create virtual machines
In this section, you create two VMs (lb-vm1 and lb-VM2) in a single zone (Zone 1).
These VMs are added to the backend pool of the load balancer that was created earlier.
In the search box at the top of the portal, enter Virtual machine. Select Virtual machines in the search results.
In Virtual machines, select + Create > Azure virtual machine.
In Create a virtual machine, enter or select the following values in the Basics tab:
Setting Value Project Details Subscription Select your Azure subscription Resource Group Select load-balancer-rg Instance details Virtual machine name Enter lb-VM1 Region Select ((US) East US) Availability Options Select Availability zones Availability zone Select Zone 1 Security type Select Standard. Image Select Windows Server 2022 Datacenter: Azure Edition - Gen2 Azure Spot instance Leave the default of unchecked. Size Choose VM size or take default setting Administrator account Username Enter a username Password Enter a password Confirm password Reenter password Inbound port rules Public inbound ports Select None
Select the Networking tab, or select Next: Disks, then Next: Networking.
In the Networking tab, select or enter the following information:
Setting Value Network interface Virtual network Select lb-vnet Subnet Select backend-subnet Public IP Select None. NIC network security group Select Advanced Configure network security group Skip this setting until the rest of the settings are completed. Complete after Select a backend pool. Delete NIC when VM is deleted Leave the default of unselected. Accelerated networking Leave the default of selected. Load balancing Load balancing options Load-balancing options Select Azure load balancer Select a load balancer Select load-balancer Select a backend pool Select lb-backend-pool Configure network security group Select Create new. In the Create network security group, enter lb-NSG in Name. Under Inbound rules, select +Add an inbound rule. In Service, select HTTP. Under Priority, enter 100. In Name, enter lb-NSG-Rule Select Add Select OK
Select Review + create.
Review the settings, and then select Create.
Follow the steps 1 through 7 to create another VM with the following values and all the other settings the same as lb-VM1:
Setting VM 2 Name lb-VM2 Availability zone Zone 1 Network security group Select the existing lb-NSG
Azure provides a default outbound access IP for VMs that either aren't assigned a public IP address or are in the backend pool of an internal basic Azure load balancer. The default outbound access IP mechanism provides an outbound IP address that isn't configurable.
The default outbound access IP is disabled when one of the following events happens:
- A public IP address is assigned to the VM.
- The VM is placed in the backend pool of a standard load balancer, with or without outbound rules.
- An Azure Virtual Network NAT gateway resource is assigned to the subnet of the VM.
VMs that you create by using virtual machine scale sets in flexible orchestration mode don't have default outbound access.
For more information about outbound connections in Azure, see Default outbound access in Azure and Use Source Network Address Translation (SNAT) for outbound connections.
Select All services in the left-hand menu, select All resources, and then from the resources list, select lb-VM1 that is located in the load-balancer-rg resource group.
On the Overview page, select Connect, then Bastion.
Select Use Bastion.
Enter the username and password entered during VM creation.
On the server desktop, navigate to Windows Administrative Tools > Windows PowerShell.
In the PowerShell Window, run the following commands to:
- Install the IIS server
- Remove the default iisstart.htm file
- Add a new iisstart.htm file that displays the name of the VM:
# Install IIS server role Install-WindowsFeature -name Web-Server -IncludeManagementTools # Remove default htm file Remove-Item C:\inetpub\wwwroot\iisstart.htm # Add a new htm file that displays server name Add-Content -Path "C:\inetpub\wwwroot\iisstart.htm" -Value $("Hello World from " + $env:computername)
Close the Bastion session with lb-VM1.
Repeat steps to install IIS and the updated iisstart.htm file on lb-VM2.
Test the load balancer
In the search box at the top of the page, enter Load balancer. Select Load balancers in the search results.
Click the load balancer you created, load-balancer. On the Frontend IP configuration page for your load balancer, locate the public IP address.
Copy the public IP address, and then paste it into the address bar of your browser. The custom VM page of the IIS Web server is displayed in the browser.
Clean up resources
When no longer needed, delete the resource group, load balancer, and all related resources. To do so, select the resource group load-balancer-rg that contains the resources and then select Delete.
Advance to the next article to learn how to load balance VMs across availability zones: