Skip to content

Commit 07515e8

Browse files
committed
siderchanges
1 parent 6b7ecac commit 07515e8

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

articles/virtual-wan/virtual-wan-expressroute-portal.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ Verify that you've met the following criteria before beginning your configuratio
3333

3434
* Obtain an IP address range for your hub region. The hub is a virtual network that is created and used by Virtual WAN. The address range that you specify for the hub can't overlap with any of your existing virtual networks that you connect to. It also can't overlap with your address ranges that you connect to on-premises. If you're unfamiliar with the IP address ranges located in your on-premises network configuration, coordinate with someone who can provide those details for you.
3535

36-
* The ExpressRoute circuit must be a Premium or Standard circuit in order to connect to the hub gateway.
36+
* The following ExpressRoute circuit SKUs can be connected to the hub gateway: Local, Standard, and Premium
3737

3838
* If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
3939

@@ -87,16 +87,17 @@ In this section, you create the peering connection between your hub and a VNet.
8787
* **Connection name** - Name your connection.
8888
* **Hubs** - Select the hub you want to associate with this connection.
8989
* **Subscription** - Verify the subscription.
90-
* **Virtual network** - Select the virtual network you want to connect to this hub. The virtual network can't have an already existing virtual network gateway (neither VPN, nor ExpressRoute).
90+
* **Virtual network** - Select the virtual network you want to connect to this hub. The virtual network can't have an already existing virtual network gateway (neither VPN nor ExpressRoute).
9191

9292
## <a name="connectcircuit"></a>Connect your circuit to the hub gateway
9393

9494
Once the gateway is created, you can connect an [ExpressRoute circuit](../expressroute/expressroute-howto-circuit-portal-resource-manager.md) to it.
9595

96-
* ExpressRoute Standard or Premium circuits that are in ExpressRoute Global Reach-supported locations can connect to a Virtual WAN ExpressRoute gateway and enjoy all Virtual WAN transit capabilities (VPN-to-VPN, VPN, and ExpressRoute transit).
97-
96+
* ExpressRoute Standard or Premium circuits that are in ExpressRoute Global Reach-supported locations can connect to a Virtual WAN ExpressRoute gateway and enjoy all Virtual WAN transit capabilities (VPN-to-VPN, VPN-to-ExpressRoute, and ExpressRoute-to-ExpressRoute transit).
97+
[SID: NEED TO REWORD? Check with Madhu]
9898
* ExpressRoute Standard and Premium circuits that are in non-Global Reach locations can connect to Azure resources, but won't be able to use Virtual WAN transit capabilities. ExpressRoute Local is also supported with Azure Virtual WAN virtual hubs.
9999

100+
100101
### To connect the circuit to the hub gateway
101102

102103
In the portal, go to the **Virtual hub -> Connectivity -> ExpressRoute** page. If you have access in your subscription to an ExpressRoute circuit, you'll see the circuit you want to use in the list of circuits. If you don’t see any circuits, but have been provided with an authorization key and peer circuit URI, you can redeem and connect a circuit. See [To connect by redeeming an authorization key](#authkey).

0 commit comments

Comments
 (0)