Merge pull request #214914 from cherylmc/VWAN-Bypass

Screenshots and bypass next hop IP

Author: v-regandowner

articles/virtual-wan/how-to-virtual-hub-routing.md

@@ -7,78 +7,61 @@ author: cherylmc
 
 ms.service: virtual-wan
 ms.topic: how-to
-ms.date: 04/27/2021
+ms.date: 10/18/2022
 ms.author: cherylmc
 
 ---
 # How to configure virtual hub routing
 
-A virtual hub can contain multiple gateways such as a Site-to-site VPN gateway, ExpressRoute gateway, Point-to-site gateway, and Azure Firewall. The routing capabilities in the virtual hub are provided by a router that manages all routing, including transit routing, between the gateways using Border Gateway Protocol (BGP). This router also provides transit connectivity between virtual networks that connect to a virtual hub and can support up to an aggregate throughput of 50 Gbps. These routing capabilities apply to Standard Virtual WAN customers.
+A virtual hub can contain multiple gateways such as a site-to-site VPN gateway, ExpressRoute gateway, point-to-site gateway, and Azure Firewall. The routing capabilities in the virtual hub are provided by a router that manages all routing, including transit routing, between the gateways using Border Gateway Protocol (BGP). This router also provides transit connectivity between virtual networks that connect to a virtual hub and can support up to an aggregate throughput of 50 Gbps. These routing capabilities apply to customers using **Standard** Virtual WANs. For more information, see [About virtual hub routing](about-virtual-hub-routing.md).
 
-For more information, see [About virtual hub routing](about-virtual-hub-routing.md).
+## Create a route table
 
-## <a name="create-table"></a>Create a route table
+1. In the Azure portal, navigate to the **virtual hub**.
+1. On the **Virtual HUB** page, in the left pane, select **Route Tables**. The **Route Tables** page will populate the current route tables for this hub.
+1. Select **+ Create route table** to open the **Create Route Table** page.
+1. On the **Basics** page, complete the following fields, then click **Labels** to move to the Labels page.
 
-1. In the Azure portal, navigate to the virtual hub.
-2. Under **Connectivity**, select **Routing**. On the Routing page, you see the **Default** and **None** route tables.
+   :::image type="content" source="./media/how-to-virtual-hub-routing/basics.png" alt-text="Screenshot showing the Create Route Table page Basics tab." lightbox="./media/how-to-virtual-hub-routing/basics.png":::
 
-   :::image type="content" source="./media/how-to-virtual-hub-routing/routing.png" alt-text="Routing page":::
-3. Select **+Create route table** to open the **Create Route Table** page.
-4. On the Create Route Table page **Basics** tab, complete the following fields.
-
-   :::image type="content" source="./media/how-to-virtual-hub-routing/basics.png" alt-text="Basics tab":::
-
-   * **Name**
-   * **Routes**
-   * **Route name**
-   * **Destination type**
+   * **Name**: Name the route table instance.
+   * **Route name**: Name the route.
+   * **Destination type**: Select from the dropdown.
    * **Destination prefix**: You can aggregate prefixes. For example: VNet 1: 10.1.0.0/24 and VNet 2: 10.1.1.0/24 can be aggregated as 10.1.0.0/16. **Branch** routes apply to all connected VPN sites, ExpressRoute circuits, and User VPN connections.
    * **Next hop**: A list of virtual network connections, or Azure Firewall.
+   * **Next Hop IP**: If you select a virtual network connection for Next hop, you'll see **Configure static routes** when you click **Configure**. This is an optional configuration setting. For more information, see [Configuring static routes](about-virtual-hub-routing.md#static).
 
-     If you select a virtual network connection, you will see **Configure static routes**. This is an optional configuration setting. For more information, see [Configuring static routes](about-virtual-hub-routing.md#static).
-
-      :::image type="content" source="./media/how-to-virtual-hub-routing/next-hop.png" alt-text="Next hop":::
-
-5. Select the **Labels** tab to configure label names. Labels provide a mechanism to logically group route tables.
-
-    :::image type="content" source="./media/how-to-virtual-hub-routing/labels.png" alt-text="Configure label names":::
-
-6. Select the **Associations** tab to associate connections to the route table.
-You will see **Branches**, **Virtual Networks**, and the **Current settings** of the connections.
-
-    :::image type="content" source="./media/how-to-virtual-hub-routing/associations.png" alt-text="Association connections to the route table":::
+1. On the **Labels** page, configure label names. Labels provide a mechanism to logically group route tables. Configure any required labels, then move to the Associations page.
 
-7. Select the **Propagations** tab to propagate routes from connections to the route table.
+1. On the **Associations** page, associate connections to the route table. You'll see **Branches**, **Virtual Networks**, and the **Current settings** of the connections. After configuring settings, move to the Propagations page.
 
-    :::image type="content" source="./media/how-to-virtual-hub-routing/propagations.png" alt-text="Propagate routes":::
+    :::image type="content" source="./media/how-to-virtual-hub-routing/associations-settings.png" alt-text="Screenshot shows Associations page with connections to the route table." lightbox="./media/how-to-virtual-hub-routing/associations-settings.png":::
 
-8. Select **Create** to create the route table.
+1. On the **Propagations** page, select the settings to propagate routes from connections to the route table.
 
-## <a name="edit-table"></a>To edit a route table
+    :::image type="content" source="./media/how-to-virtual-hub-routing/propagations-settings.png" alt-text="Screenshots shows propagations settings." lightbox="./media/how-to-virtual-hub-routing/propagations-settings.png":::
 
-In the Azure portal, locate the route table of your virtual hub. Select the route table to edit any information.
+1. Select **Create** to create the route table.
 
-## <a name="delete-table"></a>To delete a route table
+## Edit a route table
 
-In the Azure portal, locate the route table of your virtual hub. You cannot delete a Default or None route table. However, you can delete all custom route tables. Click **"…"**, and then select **Delete**.
+In the Azure portal, go to your **Virtual HUB -> Route Tables** page. To open the **Edit route table page**, click the name of the route table you want to edit. Edit the values you want to change, then click **Review + create** or **Create** (depending on the page that you are on) to save your settings.
 
-## <a name="view-routes"></a>To view effective routes
+## Delete a route table
 
-In the Azure portal, locate the route table of your virtual hub. Click **"…"** and select **Effective Routes** to view routes learned by the selected route table. Propagated routes from the connection to the route table are automatically populated in **Effective Routes** of the route table. For more information, see [About effective routes](effective-routes-virtual-hub.md).
+In the Azure portal, go to your **Virtual HUB -> Route Tables** page. Select the checkbox for route table that you want to delete. Click **"…"**, and then select **Delete**. You can't delete a Default or None route table. However, you can delete all custom route tables. 
 
-:::image type="content" source="./media/how-to-virtual-hub-routing/effective.png" alt-text="View Effective Routes" lightbox="./media/how-to-virtual-hub-routing/effective-expand.png":::
+## View effective routes
 
-## <a name="routing-configuration"></a>To set up routing configuration for a virtual network connection
+1. In the Azure portal, go to your **Virtual HUB -> Effective Routes** page.
+1. From the dropdowns, select the route table to view routes learned by the selected route table. Propagated routes from the connection to the route table are automatically populated in **Effective Routes** of the route table. For more information, see [About effective routes](effective-routes-virtual-hub.md).
+1. To download this information to a csv file, click **Download** at the top of the page.
 
-1. In the Azure portal, navigate to your virtual WAN and, under **Connectivity**, select **Virtual Network Connections**.
-1. Select **+Add connection**.
-1. Select the virtual network from the dropdown.
-1. Set up the routing configuration to associate to a route table. For **Associate Route Table**, select the route table from the dropdown.
-1. Set up the routing configuration to propagate to one or many route tables. For **Propagate to Route Table**, select from the dropdown.
-1. For **Static routes**, configure static routes for Network Virtual Appliance (if applicable). Virtual WAN supports a single next hop IP for static route in a virtual network connection. For example, if you have a separate virtual appliance for ingress and egress traffic flows, it would be best to have the virtual appliances in separate VNETs and attach the VNETs to the virtual hub.
+   :::image type="content" source="./media/how-to-virtual-hub-routing/effective-routes.png" alt-text="Screenshot of Effective Routes page." lightbox="./media/how-to-virtual-hub-routing/effective-routes.png":::
 
+## <a name="routing-configuration"></a>Set up routing configuration for a virtual network connection
 
-:::image type="content" source="./media/how-to-virtual-hub-routing/routing-configuration.png" alt-text="Set up routing configuration" lightbox="./media/how-to-virtual-hub-routing/routing-configuration-expand.png":::
+[!INCLUDE [Connect](../../includes/virtual-wan-connect-vnet-hub-include.md)]
 
 ## Next steps
 

articles/virtual-wan/howto-connect-vnet-hub.md

@@ -5,7 +5,7 @@ description: Learn how to connect a VNet to a Virtual WAN hub using the portal.
 author: cherylmc
 ms.service: virtual-wan
 ms.topic: how-to
-ms.date: 05/13/2022
+ms.date: 10/18/2022
 ms.author: cherylmc
 
 ---

articles/virtual-wan/media/how-to-virtual-hub-routing/associations-settings.png

@@ -1,31 +1,26 @@
 ---
 author: cherylmc
 ms.author: cherylmc
-ms.date: 08/22/2022
+ms.date: 10/17/2022
 ms.service: virtual-wan
 ms.topic: include
 
 #This include is used in multiple articles. Before modifying, verify that any changes apply to all articles that use this include.
 ---
-1. Go to your **Virtual WAN**.
 
-1. In the left pane, under Connectivity, select **Virtual network connections**.
+1. In the Azure portal, go to your **Virtual WAN -> Virtual network connections** page.
+1. On the **Add connection** page, configure the connection settings. For information about routing settings, see [About routing](../articles/virtual-wan/about-virtual-hub-routing.md).
 
-1. On the **Virtual network connections** page, click **+Add connection**.
-
-   :::image type="content" source="./media/virtual-wan-connect-vnet-hub/add-connection.png" alt-text="Screenshot shows add connection.":::
-
-1. On the **Add connection** page, configure the required settings. For more information about routing settings, see [About routing](../articles/virtual-wan/about-virtual-hub-routing.md).
-
-   :::image type="content" source="./media/virtual-wan-connect-vnet-hub/connection.png" alt-text="Screenshot shows VNet connection page.":::
+   :::image type="content" source="./media/virtual-wan-connect-vnet-hub/add.png" alt-text="Screenshot of the Add connection page." lightbox="./media/virtual-wan-connect-vnet-hub/add.png":::
 
    * **Connection name**: Name your connection.
    * **Hubs**: Select the hub you want to associate with this connection.
    * **Subscription**: Verify the subscription.
-   * **Resource group**: The resource group that contains the VNet.
+   * **Resource group**: Select the resource group that contains the virtual network to which you want to connect.
    * **Virtual network**: Select the virtual network you want to connect to this hub. The virtual network you select can't have an already existing virtual network gateway.
    * **Propagate to none**: This is set to **No** by default. Changing the switch to **Yes** makes the configuration options for **Propagate to Route Tables** and **Propagate to labels** unavailable for configuration.
-   * **Associate Route Table**: You can select the route table that you want to associate.
-   * **Static routes**: You can use this setting to specify next hop.
-
-1. Once you've completed the settings you want to configure, select **Create** to create the connection.
+   * **Associate Route Table**: From the dropdown, you can select a route table that you want to associate.
+   * **Propagate to labels**: Labels are a logical group of route tables. For this setting, select from the dropdown.
+   * **Static routes**: Configure static routes, if necessary. Configure static routes for Network Virtual Appliances (if applicable). Virtual WAN supports a single next hop IP for static route in a virtual network connection. For example, if you have a separate virtual appliance for ingress and egress traffic flows, it would be best to have the virtual appliances in separate VNets and attach the VNets to the virtual hub.
+   * **Bypass Next Hop IP for workloads within this VNet**: This setting lets you deploy NVAs and other workloads into the same VNet without forcing all the traffic through the NVA. This setting can only be configured when you're configuring a new connection. If you want to use this setting for a connection you've already created, delete the connection, then add a new connection.
+1. Once you've completed the settings you want to configure, click **Create** to create the connection.