Merge pull request #264362 from duongau/erconnectionnew

ExpressRoute - link vnet to circuit (new create experience)

Author: v-regandowner

articles/expressroute/expressroute-howto-linkvnet-portal-resource-manager.md

@@ -1,16 +1,17 @@
 ---
-title: 'Link a virtual network to an ExpressRoute circuit - Azure portal'
-description: This article shows you how to create a connection to link a virtual network to an Azure ExpressRoute circuit using the Azure portal. 
+title: 'Link a virtual network to ExpressRoute circuits - Azure portal'
+description: This article shows you how to create a connection to link a virtual network to Azure ExpressRoute circuits using the Azure portal. 
 services: expressroute
 author: duongau
 ms.service: expressroute
 ms.topic: how-to
 ms.date: 08/31/2023
 ms.author: duau
 ms.custom: seodec18, template-tutorial
+zone_pivot_groups: expressroute-experience
 ---
 
-# Connect a virtual network to an ExpressRoute circuit using the Azure portal
+# Connect a virtual network to ExpressRoute circuits using the Azure portal
 
 > [!div class="op_single_selector"]
 > * [Azure portal](expressroute-howto-linkvnet-portal-resource-manager.md)
@@ -19,7 +20,7 @@ ms.custom: seodec18, template-tutorial
 > * [PowerShell (classic)](expressroute-howto-linkvnet-classic.md)
 > 
 
-This article helps you create a connection to link a virtual network (virtual network) to an Azure ExpressRoute circuit using the Azure portal. The virtual networks that you connect to your Azure ExpressRoute circuit can either be in the same subscription or part of another subscription.
+This article helps you create a connection to link a virtual network (virtual network) to Azure ExpressRoute circuits using the Azure portal. The virtual networks that you connect to your Azure ExpressRoute circuit can either be in the same subscription or part of another subscription.
 
 :::image type="content" source="./media/expressroute-howto-linkvnet-portal-resource-manager/gateway-circuit.png" alt-text="Diagram showing a virtual network linked to an ExpressRoute circuit.":::
 
@@ -51,23 +52,79 @@ This article helps you create a connection to link a virtual network (virtual ne
 
 ### To create a connection
 
-1. Ensure that your ExpressRoute circuit and Azure private peering have been configured successfully. Follow the instructions in [Create an ExpressRoute circuit](expressroute-howto-circuit-arm.md) and [Create and modify peering for an ExpressRoute circuit](expressroute-howto-routing-arm.md). Your ExpressRoute circuit should look like the following image:
+::: zone pivot="expressroute-preview"
+
+1. Sign in to the Azure portal with this [Preview link](https://aka.ms/expressrouteguidedportal). This link is required to access the new preview connection create experience to an ExpressRoute circuit.
+
+::: zone-end
+
+2. Ensure that your ExpressRoute circuit and Azure private peering have been configured successfully. Follow the instructions in [Create an ExpressRoute circuit](expressroute-howto-circuit-arm.md) and [Create and modify peering for an ExpressRoute circuit](expressroute-howto-routing-arm.md). Your ExpressRoute circuit should look like the following image:
 
     :::image type="content" source="./media/expressroute-howto-linkvnet-portal-resource-manager/express-route-circuit.png" alt-text="ExpressRoute circuit screenshot":::
 
-1. You can now start provisioning a connection to link your virtual network gateway to your ExpressRoute circuit. Select **Connection** > **Add** to open the **Add connection** page.
+3. You can now start provisioning a connection to link your virtual network gateway to your ExpressRoute circuit. Select **Connection** > **Add** to open the **Create connection** page.
 
     :::image type="content" source="./media/expressroute-howto-linkvnet-portal-resource-manager/add-connection.png" alt-text="Add connection screenshot":::
 
-1. Enter a name for the connection and then select **Next: Settings >**.
+::: zone pivot="expressroute-preview"
+
+4. Select the **Connection type** as **ExpressRoute** and then select **Next: Settings >**.
+
+    :::image type="content" source="./media/expressroute-howto-linkvnet-portal-resource-manager/create-connection-basic-new.png" alt-text="Screenshot of create a connection basic page.":::
+
+5. Select the resiliency type for your connection. You can choose **Maximum resiliency** or **Standard resiliency**.
+
+    **Maximum resiliency** - This option provides the highest level of resiliency to your virtual network. It provides two redundant connections from the virtual network gateway to two different ExpressRoute circuits in different ExpressRoute locations.
+    
+    :::image type="content" source="./media/expressroute-howto-linkvnet-portal-resource-manager/maximum-resiliency.png" alt-text="Diagram of a virtual network gateway connected to two different ExpressRoute circuits.":::
+
+    **Standard resiliency** - This option provides a single redundant connection from the virtual network gateway to a single ExpressRoute circuit. 
+
+    :::image type="content" source="./media/expressroute-howto-linkvnet-portal-resource-manager/standard-resiliency.png" alt-text="Diagram of a virtual network gateway connected to a single ExpressRoute circuit.":::
+    
+6. Enter the following information for the respective resiliency type and then select **Review + create**. Then select **Create** after validation completes.
+
+    :::image type="content" source="./media/expressroute-howto-linkvnet-portal-resource-manager/create-connection-configuration.png" alt-text="Screenshot of the settings page for maximum resiliency ExpressRoute connections to a virtual network gateway.":::
+
+    **Maximum resiliency**
+
+    | Setting | Value |
+    | ---     | ---   |
+    | Virtual network gateway | Select the virtual network gateway that you want to connect to the ExpressRoute circuit. |
+    | Use existing connection or create new | You can augment resiliency for an ExpressRoute connection you already created by selecting **Use existing**. Then select an existing ExpressRoute connection for the first connection. If you select **Use existing**, you only need to configure the second connection. If you select **Create new**, enter following information for both connections. |
+    | Name | Enter a name for the connection. |
+    | ExpressRoute circuit | Select the ExpressRoute circuit that you want to connect to. |
+    | Routing weight | Enter a routing weight for the connection. The routing weight is used to determine the primary and secondary connections. The connection with the higher routing weight is the preferred circuit. |
+    | FastPath | Select the checkbox to enable FastPath. For more information, see [About ExpressRoute FastPath](about-fastpath.md). |
+
+    Complete the same information for the second ExpressRoute connection. When selecting an ExpressRoute circuit for the second connection, you are provided with the distance from the first ExpressRoute circuit. This information appears in the diagram and can help you select the second ExpressRoute location.
+
+    > [!NOTE]
+    > To have maximum resiliency, you should select two circuits in different peering location. You'll be given the following warning if you select two circuits in the same peering location.
+    >
+    > :::image type="content" source="./media/expressroute-howto-linkvnet-portal-resource-manager/same-location-warning.png" alt-text="Screenshot of warning in the Azure portal when selecting two ExpressRoute circuits in the same peering location.":::
+
+    **Standard resiliency**
+
+    For standard resiliency, you only need to enter information for one connection.
+
+7. After your connection has been successfully configured, your connection object will show the information for the connection.
+
+    :::image type="content" source="./media/expressroute-howto-linkvnet-portal-resource-manager/connection-object.png" alt-text="Screenshot of a created connection resource.":::
+
+::: zone-end
+
+::: zone pivot="expressroute-current"
+
+4. Enter a name for the connection and then select **Next: Settings >**.
 
     :::image type="content" source="./media/expressroute-howto-linkvnet-portal-resource-manager/create-connection-basic.png" alt-text="Create connection basic page":::
 
-1. Select the gateway that belongs to the virtual network that you want to link to the circuit and select **Review + create**. Then select **Create** after validation completes.
+5. Select the gateway that belongs to the virtual network that you want to link to the circuit and select **Review + create**. Then select **Create** after validation completes.
 
     :::image type="content" source="./media/expressroute-howto-linkvnet-portal-resource-manager/create-connection-settings.png" alt-text="Create connection settings page":::
 
-1. After your connection has been successfully configured, your connection object will show the information for the connection.
+6. After your connection has been successfully configured, your connection object will show the information for the connection.
 
     :::image type="content" source="./media/expressroute-howto-linkvnet-portal-resource-manager/connection-object.png" alt-text="Connection object screenshot":::
 
@@ -77,14 +134,11 @@ You can share an ExpressRoute circuit across multiple subscriptions. The followi
 
 :::image type="content" source="./media/expressroute-howto-linkvnet-portal-resource-manager/cross-subscription.png" alt-text="Cross-subscription connectivity":::
 
-> [!NOTE]
-> Connecting virtual networks between Azure sovereign clouds and Public Azure cloud is not supported. You can only link virtual networks from different subscriptions in the same cloud.
-
 Each of the smaller clouds within the large cloud is used to represent subscriptions that belong to different departments within an organization. Each of the departments within the organization uses their own subscription for deploying their services--but they can share a single ExpressRoute circuit to connect back to your on-premises network. A single department (in this example: IT) can own the ExpressRoute circuit. Other subscriptions within the organization may use the ExpressRoute circuit.
 
-  > [!NOTE]
-  > Connectivity and bandwidth charges for the dedicated circuit will be applied to the ExpressRoute circuit owner. All virtual networks share the same bandwidth.
-  >
+> [!NOTE]
+> * Connecting virtual networks between Azure sovereign clouds and Public Azure cloud is not supported. You can only link virtual networks from different subscriptions in the same cloud.
+> * Connectivity and bandwidth charges for the dedicated circuit will be applied to the ExpressRoute circuit owner. All virtual networks share the same bandwidth.
 
 ### Administration - About circuit owners and circuit users
 
@@ -126,9 +180,10 @@ You can delete a connection by selecting the **Delete** icon for the authorizati
 :::image type="content" source="./media/expressroute-howto-linkvnet-portal-resource-manager/delete-authorization-key.png" alt-text="Delete authorization key":::
 
 If you want to delete the connection but retain the authorization key, you can delete the connection from the connection page of the circuit.
+
 > [!NOTE]
-  > Connections redeemed in different subscriptions will not display in the circuit connection page. Navigate to the subscription where the authorization was redeemed and delete the top-level connection resource.
-  >
+> Connections redeemed in different subscriptions will not display in the circuit connection page. Navigate to the subscription where the authorization was redeemed and delete the top-level connection resource.
+
 
 :::image type="content" source="./media/expressroute-howto-linkvnet-portal-resource-manager/delete-connection-owning-circuit.png" alt-text="Delete connection owning circuit":::
 
@@ -164,6 +219,8 @@ The circuit user needs the resource ID and an authorization key from the circuit
 
 You can enable [ExpressRoute FastPath](expressroute-about-virtual-network-gateways.md) if your virtual network gateway is Ultra Performance or ErGw3AZ. FastPath improves data path performance such as packets per second and connections per second between your on-premises network and your virtual network.
 
+::: zone-end
+
 **Configure FastPath on a new connection**
 
 When adding a new connection for your ExpressRoute gateway, select the checkbox for **FastPath**.