Merge pull request #298969 from raghavendermareddy/patch-549773

Clarify ECMP statement

Author: prmerger-automator[bot]

articles/expressroute/designing-for-disaster-recovery-with-expressroute-privatepeering.md

@@ -5,7 +5,7 @@ services: expressroute
 author: duongau
 ms.service: azure-expressroute
 ms.topic: concept-article
-ms.date: 11/18/2024
+ms.date: 04/28/2025
 ms.author: duau
 ---
 
@@ -68,7 +68,7 @@ Let's consider the example network illustrated in the following diagram. In the
 
 :::image type="content" source="./media/designing-for-disaster-recovery-with-expressroute-pvt/one-region.png" alt-text="Diagram of small to medium size on-premises network considerations.":::
 
-By default, if you advertise routes identically over all the ExpressRoute paths, Azure load-balances on-premises bound traffic across all the ExpressRoute paths using Equal-cost multi-path (ECMP) routing.
+By default, if you advertise routes identically over all the ExpressRoute paths, Azure load-balances on-premises bound traffic across a maximum of 4 ExpressRoute circuits using Equal-cost multi-path (ECMP) routing.
 
 However, with the geo-redundant ExpressRoute circuits we need to take into consideration different network performances with different network paths (particularly for network latency). To get more consistent network performance during normal operation, you may want to prefer the ExpressRoute circuit that offers the minimal latency.