Skip to content

Commit 0ec2ea0

Browse files
author
Michael Bender
committed
Acrolinx
1 parent a594381 commit 0ec2ea0

File tree

1 file changed

+18
-18
lines changed

1 file changed

+18
-18
lines changed

articles/load-balancer/update-load-balancer-with-vm-scale-set.md

Lines changed: 18 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
2-
title: Update or delete an existing load balancer used by virtual machine scale sets
2+
title: Update or delete an existing load balancer used by Virtual Machine Scale Sets
33
titleSuffix: Azure Load Balancer
4-
description: With this how-to article, get started with Azure Standard Load Balancer and virtual machine scale sets.
4+
description: With this how-to article, get started with Azure Standard Load Balancer and Virtual Machine Scale Sets.
55
services: load-balancer
66
documentationcenter: na
77
author: mbender-ms
@@ -10,35 +10,35 @@ ms.service: load-balancer
1010
ms.topic: article
1111
ms.tgt_pltfrm: na
1212
ms.workload: infrastructure-services
13-
ms.date: 12/29/2020
13+
ms.date: 12/06/2022
1414
ms.author: mbender
1515
ROBOTS: NOINDEX
1616
---
17-
# Update or delete a load balancer used by virtual machine scale sets
17+
# Update or delete a load balancer used by Virtual Machine Scale Sets
1818

19-
When you work with virtual machine scale sets and an instance of Azure Load Balancer, you can:
19+
When you work with Virtual Machine Scale Sets and an instance of Azure Load Balancer, you can:
2020

2121
- Add, update, and delete rules.
2222
- Add configurations.
2323
- Delete the load balancer.
2424

25-
## Set up a load balancer for scaling out virtual machine scale sets
25+
## Set up a load balancer for scaling out Virtual Machine Scale Sets
2626

27-
Make sure that the instance of Azure Load Balancer has an [inbound NAT pool](/cli/azure/network/lb/inbound-nat-pool) set up and that the virtual machine scale set is put in the backend pool of the load balancer. Load Balancer will automatically create new inbound NAT rules in the inbound NAT pool when new virtual machine instances are added to the virtual machine scale set.
27+
Make sure that the instance of Azure Load Balancer has an [inbound NAT pool](/cli/azure/network/lb/inbound-nat-pool) set up and that the Virtual Machine Scale Set is put in the backend pool of the load balancer. Load Balancer will automatically create new inbound NAT rules in the inbound NAT pool when new virtual machine instances are added to the Virtual Machine Scale Set.
2828

2929
To check whether the inbound NAT pool is properly set up:
3030

3131
1. Sign in to the [Azure portal](https://portal.azure.com).
3232
1. On the left menu, select **All resources**. Then select **MyLoadBalancer** from the resource list.
33-
1. Under **Settings**, select **Inbound NAT rules**. In the right pane, if you see a list of rules created for each individual instance in the virtual machine scale set, you're all set to go for scaling up at any time.
33+
1. Under **Settings**, select **Inbound NAT rules**. In the right pane, if you see a list of rules created for each individual instance in the Virtual Machine Scale Set, you're all set to go for scaling up at any time.
3434

3535
## Add inbound NAT rules
3636

37-
Individual inbound NAT rules can't be added. But you can add a set of inbound NAT rules with defined front-end port range and back-end port for all instances in the virtual machine scale set.
37+
Individual inbound NAT rules can't be added. But you can add a set of inbound NAT rules with defined front-end port range and back-end port for all instances in the Virtual Machine Scale Set.
3838

39-
To add a whole set of inbound NAT rules for the virtual machine scale sets, first create an inbound NAT pool in the load balancer. Then reference the inbound NAT pool from the network profile of the virtual machine scale set. A full example using the CLI is shown.
39+
To add a whole set of inbound NAT rules for the Virtual Machine Scale Sets, first create an inbound NAT pool in the load balancer. Then reference the inbound NAT pool from the network profile of the Virtual Machine Scale Set. A full example using the CLI is shown.
4040

41-
The new inbound NAT pool should not have an overlapping front-end port range with existing inbound NAT pools. To view existing inbound NAT pools that are set up, use this [CLI command](/cli/azure/network/lb/inbound-nat-pool#az-network-lb-inbound-nat-pool-list):
41+
The new inbound NAT pool shouldn't have an overlapping front-end port range with existing inbound NAT pools. To view existing inbound NAT pools that are set up, use this [CLI command](/cli/azure/network/lb/inbound-nat-pool#az-network-lb-inbound-nat-pool-list):
4242

4343
```azurecli-interactive
4444
az network lb inbound-nat-pool create
@@ -62,9 +62,9 @@ The new inbound NAT pool should not have an overlapping front-end port range wit
6262
```
6363
## Update inbound NAT rules
6464

65-
Individual inbound NAT rules can't be updated. But you can update a set of inbound NAT rules with a defined front-end port range and a back-end port for all instances in the virtual machine scale set.
65+
Individual inbound NAT rules can't be updated. But you can update a set of inbound NAT rules with a defined front-end port range and a back-end port for all instances in the Virtual Machine Scale Set.
6666

67-
To update a whole set of inbound NAT rules for virtual machine scale sets, update the inbound NAT pool in the load balancer.
67+
To update a whole set of inbound NAT rules for Virtual Machine Scale Sets, update the inbound NAT pool in the load balancer.
6868

6969
```azurecli-interactive
7070
az network lb inbound-nat-pool update
@@ -152,21 +152,21 @@ Make sure to create separate inbound NAT pools with non-overlapping frontend por
152152
--name MyVMSS2
153153
```
154154

155-
## Delete the front-end IP configuration used by the virtual machine scale set
155+
## Delete the front-end IP configuration used by the Virtual Machine Scale Set
156156

157157
To delete the front-end IP configuration in use by the scale set:
158158

159159
1. First delete the inbound NAT pool (the set of inbound NAT rules) that references the front-end IP configuration. Instructions on how to delete the inbound rules are found in the previous section.
160160
1. Delete the load-balancing rule that references the front-end IP configuration.
161161
1. Delete the front-end IP configuration.
162162

163-
## Delete a load balancer used by a virtual machine scale set
163+
## Delete a load balancer used by a Virtual Machine Scale Set
164164

165165
To delete the front-end IP configuration in use by the scale set:
166166

167167
1. First delete the inbound NAT pool (the set of inbound NAT rules) that references the front-end IP configuration. Instructions on how to delete the inbound rules are found in the previous section.
168-
1. Delete the load-balancing rule that references the back-end pool that contains the virtual machine scale set.
169-
1. Remove the `loadBalancerBackendAddressPool` reference from the network profile of the virtual machine scale set.
168+
1. Delete the load-balancing rule that references the back-end pool that contains the Virtual Machine Scale Set.
169+
1. Remove the `loadBalancerBackendAddressPool` reference from the network profile of the Virtual Machine Scale Set.
170170

171171
A full example using the CLI is shown here:
172172

@@ -184,6 +184,6 @@ Finally, delete the load balancer resource.
184184

185185
## Next steps
186186

187-
To learn more about Azure Load Balancer and virtual machine scale sets, read more about the concepts.
187+
To learn more about Azure Load Balancer and Virtual Machine Scale Sets, read more about the concepts.
188188

189189
> [Azure Load Balancer with virtual machine scale sets](load-balancer-standard-virtual-machine-scale-sets.md)

0 commit comments

Comments
 (0)