Skip to content

Commit 54e74bd

Browse files
authored
Update load-balancer-troubleshoot.md
1 parent fdfa0e7 commit 54e74bd

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/load-balancer/load-balancer-troubleshoot.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -123,8 +123,8 @@ If an internal Load Balancer is configured inside a VNet, and one of the partici
123123
**Resolution**
124124
There are several ways to unblock this scenario, including using a proxy. Evaluate Application Gateway or other 3rd party proxies (for example, nginx or haproxy). For more information about Application Gateway, see [Overview of Application Gateway](../application-gateway/application-gateway-introduction.md)
125125

126-
## Symptom: Cannot change backend port of existing load balancer which has VM Scale Set deployed in the backend pool.
127-
### Cause : The backend port cannot be modified for a rule that’s used by a health probe for VM Scale Set.
126+
## Symptom: Cannot change backend port for existing LB rule of a load balancer which has VM Scale Set deployed in the backend pool.
127+
### Cause : The backend port cannot be modified for a load balancing rule that’s used by a health probe for load balancer referenced by VM Scale Set.
128128
**Resolution**
129129
In order to change the port, customer can remove the health probe by updating the vmss, update the port and then configure the health probe again.
130130

0 commit comments

Comments
 (0)