Skip to content

Files

Latest commit

c19d67e · Jan 14, 2022

History

History
49 lines (34 loc) · 3.12 KB

load-balancer-standard-virtual-machine-scale-sets.md

File metadata and controls

49 lines (34 loc) · 3.12 KB
title titleSuffix description services documentationcenter author ms.custom ms.service ms.topic ms.tgt_pltfrm ms.workload ms.date ms.author
Add rules for Azure Standard Load Balancer and virtual machine scale sets
Add rules for Azure Standard Load Balancer and virtual machine scale sets
With this learning path, get started with Azure Standard Load Balancer and virtual machine scale sets.
load-balancer
na
irenehua
seodec18
load-balancer
article
na
infrastructure-services
07/17/2020
irenehua

Add rules for Azure Load Balancer with virtual machine scale sets

When you work with virtual machine scale sets and Azure Load Balancer, consider the following guidelines.

Port forwarding and inbound NAT rules

After the scale set has been created, the back-end port can't be modified for a load-balancing rule used by a health probe of the load balancer. To change the port, remove the health probe by updating the virtual machine scale set and updating the port. Then configure the health probe again.

When you use the virtual machine scale set in the back-end pool of the load balancer, the default inbound NAT rules are created automatically.

Inbound NAT pool

Each virtual machine scale set must have at least one inbound NAT pool. An inbound NAT pool is a collection of inbound NAT rules. One inbound NAT pool can't support multiple virtual machine scale sets.

Load-balancing rules

When you use the virtual machine scale set in the back-end pool of the load balancer, the default load-balancing rule is created automatically.

Virtual Machine Scale Set Instance-level IPs

When virtual machine scale sets with public IPs per instance are created with a load balancer in front, the SKU of the instance IPs is determined by the SKU of the Load Balancer (i.e. Basic or Standard). Note that when using a Standard Load Balancer, the individual instance IPs are all of type Standard "no-zone" (though the Load Balancer frontend could be zonal or zone-redundant).

Outbound rules

To create an outbound rule for a back-end pool that's already referenced by a load-balancing rule, select No under Create implicit outbound rules in the Azure portal when the inbound load-balancing rule is created.

:::image type="content" source="./media/vm-scale-sets/load-balancer-and-vm-scale-sets.png" alt-text="Screenshot that shows load-balancing rule creation." border="true":::

Use the following methods to deploy a virtual machine scale set with an existing instance of Load Balancer: