Skip to content

Commit e3fde27

Browse files
author
Craig Casey
authored
Update expressroute-connect-azure-to-public-cloud.md
Correcting an issue flagged by the loc team (fragment) per https://mseng.visualstudio.com/TechnicalContent/_workitems/edit/1597334
1 parent 0f628c8 commit e3fde27

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/expressroute/expressroute-connect-azure-to-public-cloud.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ When connecting through Layer3 provider, Microsoft will advertise customer VNET
3232

3333
![](media/expressroute-connect-azure-to-public-cloud/azure-to-public-clouds-l3.png)
3434

35-
Provider may be landing each cloud provider in a separate VRF. If traffic from all the cloud providers will reach at customer router. If customer is running BGP with service provider, then these routes will be re-advertised to other cloud providers by default.
35+
Provider may be landing each cloud provider in a separate VRF, if traffic from all the cloud providers will reach at customer router. If customer is running BGP with service provider, then these routes will be re-advertised to other cloud providers by default.
3636

3737
If service provider is landing all the cloud providers in the same VRF, then routes will be advertised to other cloud providers from the service provider directly. This is assuming standard BGP operation where eBGP routes are advertised to other eBGP neighbors by default.
3838

0 commit comments

Comments
 (0)