Skip to content

Commit 52a15ad

Browse files
authored
Minor tweaks for ExpressRoute Cross-network connectivity
1 parent a53b1b1 commit 52a15ad

File tree

1 file changed

+4
-6
lines changed

1 file changed

+4
-6
lines changed

articles/expressroute/cross-network-connectivity.md

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,6 @@ ms.service: azure-expressroute
66
ms.topic: concept-article
77
ms.date: 06/30/2023
88
ms.author: duau
9-
109
---
1110

1211
# Cross-network connectivity
@@ -17,7 +16,7 @@ Fabrikam Inc. acquires Contoso Ltd. Following the merger, Fabrikam wants to inte
1716

1817
![The Application scenario](./media/cross-network-connectivity/premergerscenario.png)
1918

20-
The dashed arrows in the middle of the above figure indicate the desired network interconnections. Specifically, there are three types cross connections desired:
19+
The dashed arrows in the middle of the figure above indicate the desired network interconnections. Specifically, there are three types cross connections desired:
2120

2221
1. Fabrikam and Contoso virtual network cross connect
2322
1. Cross regional on-premises and virtual network cross connects. That is, connecting Fabrikam on-premises network to Contoso virtual network and connecting Contoso on-premises network to Fabrikam virtual network.
@@ -49,7 +48,7 @@ In this article, let's go through step by step and discuss how to achieve the de
4948

5049
Virtual network peering (VNet peering) provides the most optimal and the best network performance when connecting two virtual networks. VNet peering supports peering two VNets both within the same Azure region (commonly called VNet peering) and in two different Azure regions (commonly called Global VNet peering).
5150

52-
Let's configure Global VNet peering between the VNets in Contoso and Fabrikam Azure subscriptions. For how to create the virtual network peering between two the virtual networks, see [Create a virtual network peering][Configure VNet peering] article.
51+
Let's configure Global VNet peering between the VNets in Contoso and Fabrikam Azure subscriptions. For how to create the virtual network peering between two virtual networks, see [Create a virtual network peering][Configure VNet peering] article.
5352

5453
The following picture shows the network architecture after configuring Global VNet peering.
5554

@@ -91,9 +90,8 @@ The following table shows the routes known to the Fabrikam subscription VM. Pay
9190

9291
![Fabrikam VM routes after cross connecting ExR and VNets](./media/cross-network-connectivity/fabrikamvm-routes-xconnect.png)
9392

94-
>[!NOTE]
95-
>In either the Fabrikam and/or Contoso subscriptions you can also have spoke VNets to the respective hub VNet (a hub and spoke design is not illustrated in the architecture diagrams in this article). The cross connections between the hub VNet gateways to ExpressRoute will also allow communication between East and West hubs and spokes.
96-
>
93+
> [!NOTE]
94+
> In either the Fabrikam and/or Contoso subscriptions you can also have spoke VNets to the respective hub VNet (a hub and spoke design is not illustrated in the architecture diagrams in this article). The cross connections between the hub VNet gateways to ExpressRoute will also allow communication between East and West hubs and spokes.
9795
9896
## Cross connecting on-premises networks
9997

0 commit comments

Comments
 (0)