Skip to content

Commit 11d6e51

Browse files
authored
Merge pull request #113994 from anavinahar/patch-244
Update load-balancer-standard-availability-zones.md
2 parents 5e1eb39 + 7ec86ad commit 11d6e51

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/load-balancer/load-balancer-standard-availability-zones.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -21,9 +21,9 @@ Azure Standard Load Balancer supports [availability zones](../availability-zones
2121

2222
## <a name="concepts"></a> Availability Zones concepts applied to Load Balancer
2323

24-
A Load Balancer resource itself is regional and never zonal. The granularity of what you can configure is constrained by each configuration of frontend, rule, and backend pool definition.
25-
In the context of availability zones, the behavior and properties of a Load Balancer rule are described as zone-redundant or zonal. Zone-redundant and zonal describe the zonality of a property. In the context of Load Balancer, zone-redundant always means *multiple zones* and zonal means isolating the service to a *single zone*.
26-
Both public and internal Load Balancer support zone-redundant and zonal scenarios and both can direct traffic across zones as needed (*cross-zone load-balancing*).
24+
A Load Balancer resource itself inherits zone configuration from it's components: frontend, rule, and backend pool definition.
25+
In the context of availability zones, the behavior and properties of a Load Balancer rule are described as zone-redundant or zonal. In the context of Load Balancer, zone-redundant always means *multiple zones* and zonal means isolating the service to a *single zone*.
26+
Both types (public, internal) Load Balancer support zone-redundant and zonal scenarios and both can direct traffic across zones as needed.
2727

2828
## Frontend
2929

0 commit comments

Comments
 (0)