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
This tutorial walks you through the steps to add and remove a virtual network gateway for a pre-existing virtual network (VNet). The steps for this configuration apply to VNets that were created using the Resource Manager deployment model for an ExpressRoute configuration. For more information about virtual network gateways and gateway configuration settings for ExpressRoute, see [About virtual network gateways for ExpressRoute](expressroute-about-virtual-network-gateways.md).
20
+
This tutorial walks you through the steps to add and remove a virtual network gateway for a pre-existing virtual network (virtual network). The steps for this configuration apply to VNets that were created using the Resource Manager deployment model for an ExpressRoute configuration. For more information about virtual network gateways and gateway configuration settings for ExpressRoute, see [About virtual network gateways for ExpressRoute](expressroute-about-virtual-network-gateways.md).
21
21
22
22
In this tutorial, you learn how to:
23
23
> [!div class="checklist"]
@@ -45,7 +45,7 @@ The steps for this tutorial use the values in the following configuration refere
45
45
## Create the gateway subnet
46
46
47
47
1. In the [portal](https://portal.azure.com), navigate to the Resource Manager virtual network for which you want to create a virtual network gateway.
48
-
1. In the **Settings** section of your VNet, select **Subnets** to expand the Subnet settings.
48
+
1. In the **Settings** section of your virtual network, select **Subnets** to expand the Subnet settings.
49
49
1. Select **+ Gateway subnet** to add a gateway subnet.
50
50
51
51
:::image type="content" source="./media/expressroute-howto-add-gateway-portal-resource-manager/add-gateway-subnet.png" alt-text="Screenshot that shows the button to add the gateway subnet.":::
@@ -66,9 +66,9 @@ The steps for this tutorial use the values in the following configuration refere
66
66
| Setting | Value |
67
67
| --------| ----- |
68
68
| Subscription | Verify that the correct subscription is selected. |
69
-
| Resource Group | The resource group will automatically be chosen once you select the virtual network. |
70
-
| Name | Name your gateway. This isn't the same as naming a gateway subnet. It's the name of the gateway resource you're creating.|
71
-
| Region | Change the **Region** field to point to the location where your virtual network is located. If the region isn't pointing to the location where your virtual network is, the virtual network won't appear in the **Virtual network** dropdown. |
69
+
| Resource Group | The resource group gets automatically chosen once you select the virtual network. |
70
+
| Name | Name your gateway. This name isn't the same as naming a gateway subnet. It's the name of the gateway resource you're creating.|
71
+
| Region | Change the **Region** field to point to the location where your virtual network is located. If the region isn't pointing to the location where your virtual network is, the virtual network doesn't appear in the **Virtual network** dropdown. |
72
72
| Gateway type | Select **ExpressRoute**|
73
73
| SKU | Select the gateway SKU from the dropdown. |
74
74
| Virtual network | Select *TestVNet*. |
@@ -92,7 +92,7 @@ If you no longer need the ExpressRoute gateway, locate the gateway in the virtua
92
92
93
93
In this tutorial, you learned how to create a virtual network gateway. For more information about virtual network gateways, see: [ExpressRoute virtual network gateways](expressroute-about-virtual-network-gateways.md).
94
94
95
-
To learn how to link your VNet to an ExpressRoute circuit, advance to the next tutorial.
95
+
To learn how to link your virtual network to an ExpressRoute circuit, advance to the next tutorial.
96
96
97
97
> [!div class="nextstepaction"]
98
98
> [Link a Virtual Network to an ExpressRoute circuit](expressroute-howto-linkvnet-portal-resource-manager.md)
Copy file name to clipboardExpand all lines: articles/expressroute/expressroute-howto-circuit-portal-resource-manager.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: In this quickstart, you learn how to create, provision, verify, upd
4
4
services: expressroute
5
5
author: duongau
6
6
ms.author: duau
7
-
ms.date: 07/18/2022
7
+
ms.date: 08/31/2023
8
8
ms.topic: quickstart
9
9
ms.service: expressroute
10
10
ms.custom: mode-ui
@@ -54,7 +54,7 @@ From a browser, sign in to the [Azure portal](https://portal.azure.com) and sign
54
54
| --- | --- |
55
55
| Port type | Select if you're connecting to a service provider or directly into Microsoft's global network at a peering location. |
56
56
| Create new or import from classic | Select if you're creating a new circuit or if you're migrating a classic circuit to Azure Resource Manager. |
57
-
| Provider | Select the internet service provider who you'll be requesting your service from. |
57
+
| Provider | Select the internet service provider who you are requesting your service from. |
58
58
| Peering Location | Select the physical location where you're peering with Microsoft. |
59
59
| SKU | Select the SKU for the ExpressRoute circuit. You can specify **Local** to get the local SKU, **Standard** to get the standard SKU or **Premium** for the premium add-on. You can change between Local, Standard and Premium. |
60
60
| Billing model | Select the billing type for egress data charge. You can specify **Metered** for a metered data plan and **Unlimited** for an unlimited data plan. You can change the billing type from **Metered** to **Unlimited**. |
@@ -75,19 +75,19 @@ You can view all the circuits that you created by searching for **ExpressRoute c
75
75
76
76
:::image type="content" source="./media/expressroute-howto-circuit-portal-resource-manager/expressroute-circuit-menu.png" alt-text="Screenshot of ExpressRoute circuit menu.":::
77
77
78
-
All Expressroute circuits created in the subscription will appear here.
78
+
All Expressroute circuits created in the subscription appear here.
79
79
80
80
:::image type="content" source="./media/expressroute-howto-circuit-portal-resource-manager/expressroute-circuit-list.png" alt-text="Screenshot of ExpressRoute circuit list.":::
81
81
82
82
**View the properties**
83
83
84
-
You can view the properties of the circuit by selecting it. On the Overview page for your circuit, you'll find the **Service Key**. Provide the service key to the service provider to complete the provisioning process. The service key is unique to your circuit.
84
+
You can view the properties of the circuit by selecting it. On the Overview page for your circuit, you find the **Service Key**. Provide the service key to the service provider to complete the provisioning process. The service key is unique to your circuit.
85
85
86
86
:::image type="content" source="./media/expressroute-howto-circuit-portal-resource-manager/expressroute-circuit-overview.png" alt-text="Screenshot of ExpressRoute properties.":::
87
87
88
88
### Send the service key to your connectivity provider for provisioning
89
89
90
-
On this page, **Provider status** gives you the current state of provisioning on the service-provider side. **Circuit status** provides you the state on the Microsoft side. For more information about circuit provisioning states, see the [Workflows](expressroute-workflows.md#expressroute-circuit-provisioning-states) article.
90
+
On this page, **Provider status** gives you the current state of provisioning on the service-provider side. **Circuit status** provides you with the state on the Microsoft side. For more information about circuit provisioning states, see the [Workflows](expressroute-workflows.md#expressroute-circuit-provisioning-states) article.
91
91
92
92
When you create a new ExpressRoute circuit, the circuit is in the following state:
Copy file name to clipboardExpand all lines: articles/expressroute/expressroute-howto-linkvnet-arm.md
+19-19Lines changed: 19 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,11 @@
1
1
---
2
-
title: 'Tutorial: Link a VNet to an ExpressRoute circuit - Azure PowerShell'
2
+
title: 'Tutorial: Link a virtual network to an ExpressRoute circuit - Azure PowerShell'
3
3
description: This tutorial provides an overview of how to link virtual networks (VNets) to ExpressRoute circuits by using the Resource Manager deployment model and Azure PowerShell.
@@ -35,15 +35,15 @@ In this tutorial, you learn how to:
35
35
* Follow the instructions to [create an ExpressRoute circuit](expressroute-howto-circuit-arm.md) and have the circuit enabled by your connectivity provider.
36
36
* Ensure that you have Azure private peering configured for your circuit. See the [configure routing](expressroute-howto-routing-arm.md) article for routing instructions.
37
37
* Ensure that Azure private peering gets configured and establishes BGP peering between your network and Microsoft for end-to-end connectivity.
38
-
* Ensure that you have a virtual network and a virtual network gateway created and fully provisioned. Follow the instructions to [create a virtual network gateway for ExpressRoute](expressroute-howto-add-gateway-resource-manager.md). A virtual network gateway for ExpressRoute uses the GatewayType 'ExpressRoute', not VPN.
38
+
* Ensure that you have a virtual network and a virtual network gateway created and fully provisioned. Follow the instructions to [create a virtual network gateway for ExpressRoute](expressroute-howto-add-gateway-resource-manager.md). A virtual network gateway for ExpressRoute uses the GatewayType `ExpressRoute`, not VPN.
39
39
40
40
* You can link up to 10 virtual networks to a standard ExpressRoute circuit. All virtual networks must be in the same geopolitical region when using a standard ExpressRoute circuit.
41
41
42
-
* A single VNet can be linked to up to 16 ExpressRoute circuits. Use the steps in this article to create a new connection object for each ExpressRoute circuit you're connecting to. The ExpressRoute circuits can be in the same subscription, different subscriptions, or a mix of both.
42
+
* A single virtual network can be linked to up to 16 ExpressRoute circuits. Use the steps in this article to create a new connection object for each ExpressRoute circuit you're connecting to. The ExpressRoute circuits can be in the same subscription, different subscriptions, or a mix of both.
43
43
44
-
* If you enable the ExpressRoute premium add-on, you can link virtual networks outside of the geopolitical region of the ExpressRoute circuit. The premium add-on will also allow you to connect more than 10 virtual networks to your ExpressRoute circuit depending on the bandwidth chosen. Check the [FAQ](expressroute-faqs.md) for more details on the premium add-on.
44
+
* If you enable the ExpressRoute premium add-on, you can link virtual networks outside of the geopolitical region of the ExpressRoute circuit. The premium add-on allows you to connect more than 10 virtual networks to your ExpressRoute circuit depending on the bandwidth chosen. Check the [FAQ](expressroute-faqs.md) for more details on the premium add-on.
45
45
46
-
* In order to create the connection from the ExpressRoute circuit to the target ExpressRoute virtual network gateway, the number of address spaces advertised from the local or peered virtual networks needs to be equal to or less than **200**. Once the connection has been successfully created, you can add additional address spaces, up to 1,000, to the local or peered virtual networks.
46
+
* In order to create the connection from the ExpressRoute circuit to the target ExpressRoute virtual network gateway, the number of address spaces advertised from the local or peered virtual networks needs to be equal to or less than **200**. Once the connection has been successfully created, you can add more address spaces, up to 1,000, to the local or peered virtual networks.
47
47
48
48
* Review guidance for [connectivity between virtual networks over ExpressRoute](virtual-network-connectivity-guidance.md).
The response to the previous commands will contain the authorization key and status:
111
+
The response to the previous commands contains the authorization key and status:
112
112
113
113
```azurepowershell
114
114
Name : MyAuthorization1
@@ -179,7 +179,7 @@ You can update certain properties of a virtual network connection.
179
179
180
180
**To update the connection weight**
181
181
182
-
Your virtual network can be connected to multiple ExpressRoute circuits. You may receive the same prefix from more than one ExpressRoute circuit. To choose which connection to send traffic destined for this prefix, you can change *RoutingWeight* of a connection. Traffic will be sent on the connection with the highest *RoutingWeight*.
182
+
Your virtual network can be connected to multiple ExpressRoute circuits. You may receive the same prefix from more than one ExpressRoute circuit. To choose which connection to send traffic destined for this prefix, you can change *RoutingWeight* of a connection. Traffic is sent on the connection with the highest *RoutingWeight*.
### FastPath and Private Link for 100Gbps ExpressRoute Direct
210
+
### FastPath and Private Link for 100-Gbps ExpressRoute Direct
211
211
212
-
With FastPath and Private Link, Private Link traffic sent over ExpressRoute bypasses the ExpressRoute virtual network gateway in the data path. This is Generally Available for connections associated to 100Gb ExpressRoute Direct circuits. To enable this, follow the below guidance:
212
+
With FastPath and Private Link, Private Link traffic sent over ExpressRoute bypasses the ExpressRoute virtual network gateway in the data path. This is Generally Available for connections associated to 100-Gb ExpressRoute Direct circuits. To enable, follow the below guidance:
213
213
1. Send an email to **[email protected]**, providing the following information:
214
214
* Azure Subscription ID
215
-
* Virtual Network (VNet) Resource ID
215
+
* Virtual Network (virtual network) Resource ID
216
216
* Azure Region where the Private Endpoint/Private Link service is deployed
217
217
218
218
2. Once you receive a confirmation from Step 1, run the following Azure PowerShell command in the target Azure subscription.
With FastPath and virtual network peering, you can enable ExpressRoute connectivity directly to VMs in a local or peered virtual network, bypassing the ExpressRoute virtual network gateway in the data path.
238
238
239
-
With FastPath and UDR, you can configure a UDR on the GatewaySubnet to direct ExpressRoute traffic to an Azure Firewall or third party NVA. FastPath will honor the UDR and send traffic directly to the target Azure Firewall or NVA, bypassing the ExpressRoute virtual network gateway in the data path.
239
+
With FastPath and UDR, you can configure a UDR on the GatewaySubnet to direct ExpressRoute traffic to an Azure Firewall or third party NVA. FastPath honors the UDR and send traffic directly to the target Azure Firewall or NVA, bypassing the ExpressRoute virtual network gateway in the data path.
240
240
241
241
To enroll in the preview, send an email to **[email protected]**, providing the following information:
242
242
* Azure Subscription ID
243
-
* Virtual Network (VNet) Resource ID
243
+
* Virtual Network (virtual network) Resource ID
244
244
* ExpressRoute Circuit Resource ID
245
245
* ExpressRoute Connection(s) Resource ID(s)
246
-
* Number of Private Endpoints deployed to the local/Hub VNet.
247
-
* Resource ID of any User-Defined-Routes (UDRs) configured in the local/Hub VNet.
246
+
* Number of Private Endpoints deployed to the local/Hub virtual network.
247
+
* Resource ID of any User-Defined-Routes (UDRs) configured in the local/Hub virtual network.
248
248
249
249
**FastPath support for virtual network peering and UDRs is only available for ExpressRoute Direct connections**.
250
250
251
-
### FastPath and Private Link for 10Gbps ExpressRoute Direct
251
+
### FastPath and Private Link for 10-Gbps ExpressRoute Direct
252
252
253
-
With FastPath and Private Link, Private Link traffic sent over ExpressRoute bypasses the ExpressRoute virtual network gateway in the data path. This preview supports connections associated to 10Gbps ExpressRoute Direct circuits. This preview doesn't support ExpressRoute circuits managed by an ExpressRoute partner.
253
+
With FastPath and Private Link, Private Link traffic sent over ExpressRoute bypasses the ExpressRoute virtual network gateway in the data path. This preview supports connections associated to 10-Gbps ExpressRoute Direct circuits. This preview doesn't support ExpressRoute circuits managed by an ExpressRoute partner.
254
254
255
255
To enroll in this preview, run the following Azure PowerShell command in the target Azure subscription:
> Any connections configured for FastPath in the target subscription will be enrolled in the selected preview. We do not advise enabling these previews in production subscriptions.
263
263
> If you already have FastPath configured and want to enroll in the preview feature, you need to do the following:
264
-
> 1. Enroll in one of the FastPath preview features with the Azure PowerShell commands above.
264
+
> 1. Enroll in one of the FastPath preview features with the Azure PowerShell commands.
265
265
> 1. Disable and then re-enable FastPath on the target connection.
266
266
> 1. To switch between preview features, register the subscription with the target preview PowerShell command, and then disable and re-enable FastPath on the connection.
In this tutorial, you learned how to connect a virtual network to a circuit in the same subscription and in a different subscription. For more information about ExpressRoute gateways, see: [ExpressRoute virtual network gateways](expressroute-about-virtual-network-gateways.md).
280
280
281
-
To learn how to configure route filters for Microsoft peering using PowerShell, advance to the next tutorial.
281
+
To learn how to configure, route filters for Microsoft peering using PowerShell, advance to the next tutorial.
282
282
283
283
> [!div class="nextstepaction"]
284
284
> [Configure route filters for Microsoft peering](how-to-routefilter-powershell.md)
![prmerger-automator[bot]](https://avatars.githubusercontent.com/u/22479449?v=4&size=40){kind=avatar}
0 commit comments