Skip to content

Commit 8918902

Browse files
Merge pull request #270652 from mialdrid/patch-231
Update designing-for-high-availability-with-expressroute.md
2 parents 8005908 + 49f6c11 commit 8918902

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/expressroute/designing-for-high-availability-with-expressroute.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ In this section, let us review optional (depending on your Azure deployment and
7777

7878
### Availability Zone aware ExpressRoute virtual network gateways
7979

80-
An Availability Zone in an Azure region is a combination of a fault domain and an update domain. If you opt for zone-redundant Azure IaaS deployment, you may also want to configure zone-redundant virtual network gateways that terminate ExpressRoute private peering. To learn further, see [About zone-redundant virtual network gateways in Azure Availability Zones][zone redundant vgw]. To configure zone-redundant virtual network gateway, see [Create a zone-redundant virtual network gateway in Azure Availability Zones][conf zone redundant vgw].
80+
An Availability Zone in an Azure region is a combination of a fault domain and an update domain. To achieve the highest resiliency and availability, you should configure a zone-redundant ExpressRoute virtual network gateway. To learn more, see [About zone-redundant virtual network gateways in Azure Availability Zones][zone redundant vgw]. To configure a zone-redundant virtual network gateway, see [Create a zone-redundant virtual network gateway in Azure Availability Zones][conf zone redundant vgw].
8181

8282
### Improving failure detection time
8383

0 commit comments

Comments
 (0)