Using Azure Resource Manager Support with Azure Load Balancer
Azure Load Balancer supports two different types: Basic and Standard. This article discusses Basic Load Balancer. Basic Load Balancer is generally available, whereas Standard Load Balancer is currently in Public Preview. For more information about Standard Load Balancer, see Standard Load Balancer Overview.
Azure Resource Manager is the preferred management framework for services in Azure. Azure Load Balancer can be managed using Azure Resource Manager-based APIs and tools.
With Resource Manager, Azure Load Balancer contains the following child resources:
- Front-end IP configuration – a Load balancer can include one or more frontend IP addresses, otherwise known as a virtual IPs (VIPs). These IP addresses serve as ingress for the traffic.
- Back-end address pool – these are IP addresses associated with the virtual machine Network Interface Card (NIC) to which load is distributed.
- Load balancing rules – a rule property maps a given frontend IP and port combination to a set of backend IP addresses and port combination. A single load balancer can have multiple load balancing rules. Each rule is a combination of a frontend IP and port and backend IP and port associated with VMs.
- Probes – probes enable you to keep track of the health of VM instances. If a health probe fails, the VM instance is taken out of rotation automatically.
- Inbound NAT rules – NAT rules defining the inbound traffic flowing through the frontend IP and distributed to the backend IP.
Azure Resource Manager allows you to provision your applications using a declarative template. In a single template, you can deploy multiple services along with their dependencies. You use the same template to repeatedly deploy your application during every stage of the application lifecycle.
Templates can include definitions for Virtual Machines, Virtual Networks, Availability Sets, Network Interfaces (NICs), Storage Accounts, Load Balancers, Network Security Groups, and Public IPs. With templates, you can create everything you need for a complex application. The template file can be checked into content management system for version control and collaboration.
For Quickstart templates using Azure Load Balancer, see the GitHub repository that hosts a set of community generated templates.
Examples of templates:
- 2 VMs in a Load Balancer and load balancing rules
- 2 VMs in a VNET with an Internal Load Balancer and Load Balancer rules
- 2 VMs in a Load Balancer and configure NAT rules on the LB
Setting up Azure Load Balancer with a PowerShell or CLI
Get started with Azure Resource Manager cmdlets, command line tools, and REST APIs
- Azure Networking Cmdlets can be used to create a Load Balancer.
- How to create a load balancer using Azure Resource Manager
- Using the Azure CLI with Azure Resource Management
- Load Balancer REST APIs
You can also get started creating an Internet facing load balancer and configure what type of distribution mode for a specific load balancer network traffic behavior.
Learn how to manage idle TCP timeout settings for a load balancer. This is important when your application needs to keep connections alive for servers behind a load balancer.