You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/expressroute/circuit-placement-api.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ services: expressroute
5
5
author: mialdrid
6
6
ms.service: azure-expressroute
7
7
ms.topic: concept-article
8
-
ms.date: 10/19/2021
8
+
ms.date: 03/11/2026
9
9
ms.author: duau
10
10
# Customer intent: As an ExpressRoute partner, I want to utilize the CrossConnections circuit placement API to select and manage port pairs for circuit connectivity, so that I can optimize and enhance the performance of the ExpressRoute circuits I provision.
11
11
---
@@ -57,7 +57,7 @@ The ExpressRoute partner can list all port pairs within the target provider subs
Copy file name to clipboardExpand all lines: articles/expressroute/cross-network-connectivity.md
+26-37Lines changed: 26 additions & 37 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: This page describes an application scenario for cross network conne
4
4
author: duongau
5
5
ms.service: azure-expressroute
6
6
ms.topic: concept-article
7
-
ms.date: 06/30/2023
7
+
ms.date: 03/11/2026
8
8
ms.author: duau
9
9
ms.custom: sfi-image-nochange
10
10
# Customer intent: As a network administrator, I want to interconnect the networks of acquired companies using Azure networking features, so that I can ensure seamless communication between on-premises and cloud resources post-merger.
@@ -16,7 +16,7 @@ Fabrikam Inc. has a large physical presence and Azure deployment in East US. Fab
16
16
17
17
Fabrikam Inc. acquires Contoso Ltd. Following the merger, Fabrikam wants to interconnect the networks. The following figure illustrates the scenario:
:::image type="content" source="./media/cross-network-connectivity/premergerscenario.png" alt-text="Diagram of the pre-merger network scenario for Fabrikam and Contoso.":::
20
20
21
21
The dashed arrows in the middle of the figure above indicate the desired network interconnections. Specifically, there are three types cross connections desired:
22
22
@@ -26,104 +26,93 @@ The dashed arrows in the middle of the figure above indicate the desired network
26
26
27
27
The following table shows the route table of the private peering of the ExpressRoute of Contoso Ltd., before the merger.
28
28
29
-
29
+
:::image type="content" source="./media/cross-network-connectivity/contosoexr-rt-premerger.png" alt-text="Screenshot of Contoso ExpressRoute route table before the merger.":::
30
30
31
31
The following table shows the effective routes of a VM in the Contoso subscription, before the merger. Per the table, the VM on the VNet is aware of the VNet address space and the Contoso on-premises network, apart from the default ones.
32
32
33
-
33
+
:::image type="content" source="./media/cross-network-connectivity/contosovm-routes-premerger.png" alt-text="Screenshot of Contoso VM effective routes before the merger.":::
34
34
35
35
The following table shows the route table of the private peering of the ExpressRoute of Fabrikam Inc., before the merger.
36
36
37
-
37
+
:::image type="content" source="./media/cross-network-connectivity/fabrikamexr-rt-premerger.png" alt-text="Screenshot of Fabrikam ExpressRoute route table before the merger.":::
38
38
39
39
The following table shows the effective routes of a VM in the Fabrikam subscription, before the merger. Per the table, the VM on the VNet is aware of the VNet address space and the Fabrikam on-premises network, apart from the default ones.
40
40
41
-
41
+
:::image type="content" source="./media/cross-network-connectivity/fabrikamvm-routes-premerger.png" alt-text="Screenshot of Fabrikam VM effective routes before the merger.":::
42
42
43
43
In this article, let's go through step by step and discuss how to achieve the desired cross connections using the following Azure network features:
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).
52
52
53
-
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.
53
+
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](../virtual-network/create-peering-different-subscriptions.md) article.
54
54
55
55
The following picture shows the network architecture after configuring Global VNet peering.
56
56
57
-
57
+
:::image type="content" source="./media/cross-network-connectivity/vnet-peering.png" alt-text="Diagram of network architecture after configuring Global VNet peering.":::
58
58
59
59
The following table shows the routes known to the Contoso subscription VM. Pay attention to the last entry of the table. This entry is the result of cross connecting the virtual networks.
60
60
61
-
61
+
:::image type="content" source="./media/cross-network-connectivity/contosovm-routes-peering.png" alt-text="Screenshot of Contoso VM routes after VNet peering.":::
62
62
63
63
The following table shows the routes known to the Fabrikam subscription VM. Pay attention to the last entry of the table. This entry is the result of cross connecting the virtual networks.
64
64
65
-
65
+
:::image type="content" source="./media/cross-network-connectivity/fabrikamvm-routes-peering.png" alt-text="Screenshot of Fabrikam VM routes after VNet peering.":::
66
66
67
67
VNet peering directly links two virtual networks (see there are no next hop for *VNetGlobalPeering* entry in the two tables)
68
68
69
69
## Cross connecting VNets to the on-premises networks
70
70
71
-
We can connect an ExpressRoute circuit to multiple virtual networks. See [Subscription and service limits][Subscription limits] for the maximum number of virtual networks that can be connected to an ExpressRoute circuit.
71
+
We can connect an ExpressRoute circuit to multiple virtual networks. See [Subscription and service limits](../azure-resource-manager/management/azure-subscription-service-limits.md#azure-networking-limits) for the maximum number of virtual networks that can be connected to an ExpressRoute circuit.
72
72
73
-
Let's connect Fabrikam ExpressRoute circuit to Contoso subscription VNet and similarly Contoso ExpressRoute circuit to Fabrikam subscription VNet to enable cross connectivity between virtual networks and the on-premises networks. To connect a virtual network to an ExpressRoute circuit in a different subscription, we need to create and use an authorization. See the article: [Connect a virtual network to an ExpressRoute circuit][Connect-ER-VNet].
73
+
Let's connect Fabrikam ExpressRoute circuit to Contoso subscription VNet and similarly Contoso ExpressRoute circuit to Fabrikam subscription VNet to enable cross connectivity between virtual networks and the on-premises networks. To connect a virtual network to an ExpressRoute circuit in a different subscription, we need to create and use an authorization. See the article: [Connect a virtual network to an ExpressRoute circuit](./expressroute-howto-linkvnet-portal-resource-manager.md).
74
74
75
75
The following picture shows the network architecture after configuring the ExpressRoute cross connectivity to the virtual networks.
76
76
77
-
77
+
:::image type="content" source="./media/cross-network-connectivity/exr-x-connect.png" alt-text="Diagram of network architecture after configuring ExpressRoute cross-connectivity.":::
78
78
79
79
The following table shows the route table of the private peering of the ExpressRoute of Contoso Ltd., after cross connecting virtual networks to the on-premises networks via ExpressRoute. See that the route table has routes belonging to both the virtual networks.
80
80
81
-
81
+
:::image type="content" source="./media/cross-network-connectivity/contosoexr-rt-xconnect.png" alt-text="Screenshot of Contoso ExpressRoute route table after cross-connecting circuits and VNets.":::
82
82
83
83
The following table shows the route table of the private peering of the ExpressRoute of Fabrikam Inc., after cross connecting virtual networks to the on-premises networks via ExpressRoute. See that the route table has routes belonging to both the virtual networks.
84
84
85
-
85
+
:::image type="content" source="./media/cross-network-connectivity/fabrikamexr-rt-xconnect.png" alt-text="Screenshot of Fabrikam ExpressRoute route table after cross-connecting circuits and VNets.":::
86
86
87
87
The following table shows the routes known to the Contoso subscription VM. Pay attention to *Virtual network gateway* entries of the table. The VM sees routes for both the on-premises networks.
88
88
89
-
89
+
:::image type="content" source="./media/cross-network-connectivity/contosovm-routes-xconnect.png" alt-text="Screenshot of Contoso VM routes after cross-connecting circuits and VNets.":::
90
90
91
91
The following table shows the routes known to the Fabrikam subscription VM. Pay attention to *Virtual network gateway* entries of the table. The VM sees routes for both the on-premises networks.
92
92
93
-
93
+
:::image type="content" source="./media/cross-network-connectivity/fabrikamvm-routes-xconnect.png" alt-text="Screenshot of Fabrikam VM routes after cross-connecting circuits and VNets.":::
94
94
95
95
> [!NOTE]
96
96
> 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.
97
97
98
98
## Cross connecting on-premises networks
99
99
100
-
ExpressRoute Global Reach provides connectivity between on-premises networks that are connected to different ExpressRoute circuits. Let's configure Global Reach between Contoso and Fabrikam ExpressRoute circuits. Because the ExpressRoute circuits are in different subscriptions, we need to create and use an authorization. See [Configure ExpressRoute Global Reach][Configure Global Reach] article for step by step guidance.
100
+
ExpressRoute Global Reach provides connectivity between on-premises networks that are connected to different ExpressRoute circuits. Let's configure Global Reach between Contoso and Fabrikam ExpressRoute circuits. Because the ExpressRoute circuits are in different subscriptions, we need to create and use an authorization. See [Configure ExpressRoute Global Reach](./expressroute-howto-set-global-reach.md) article for step by step guidance.
101
101
102
102
The following picture shows the network architecture after configuring Global Reach.
103
103
104
-
104
+
:::image type="content" source="./media/cross-network-connectivity/globalreach.png" alt-text="Diagram of network architecture after configuring ExpressRoute Global Reach.":::
105
105
106
106
The following table shows the route table of the private peering of the ExpressRoute of Contoso Ltd., after configuring Global Reach. See that the route table has routes belonging to both the on-premises networks.
107
107
108
-
108
+
:::image type="content" source="./media/cross-network-connectivity/contosoexr-rt-gr.png" alt-text="Screenshot of Contoso ExpressRoute route table after configuring Global Reach.":::
109
109
110
110
The following table shows the route table of the private peering of the ExpressRoute of Fabrikam Inc., after configuring Global Reach. See that the route table has routes belonging to both the on-premises networks.
111
111
112
-
112
+
:::image type="content" source="./media/cross-network-connectivity/fabrikamexr-rt-gr.png" alt-text="Screenshot of Fabrikam ExpressRoute route table after configuring Global Reach.":::
113
113
114
114
## Next steps
115
115
116
-
See [virtual network FAQ][VNet-FAQ], for any further questions on VNet and VNet-peering. See [ExpressRoute FAQ][ER-FAQ] for any further questions on ExpressRoute and virtual network connectivity.
116
+
See [virtual network FAQ](../virtual-network/virtual-networks-faq.md), for any further questions on VNet and VNet-peering. See [ExpressRoute FAQ](./expressroute-faqs.md) for any further questions on ExpressRoute and virtual network connectivity.
117
117
118
-
Global Reach is rolled out on a country/region by country/region basis. To see if Global Reach is available in the countries/regions that you want, see [ExpressRoute Global Reach][Global Reach].
Global Reach is rolled out on a country/region by country/region basis. To see if Global Reach is available in the countries/regions that you want, see [ExpressRoute Global Reach](./expressroute-global-reach.md).
0 commit comments