Skip to content

Commit b9e2501

Browse files
removed note as Propagate static routes is rolled out and also did minor accessibility improvement
1 parent 736bb95 commit b9e2501

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

includes/virtual-wan-connect-vnet-hub-include.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,6 @@ ms.topic: include
2222
* **Propagate to labels**: Labels are a logical group of route tables. For this setting, select from the dropdown.
2323
* **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.
2424
* **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.
25-
* **Propagate static route**: This setting is currently being rolled out. This setting lets you propagate static routes defined in the **Static routes** section to route tables specified in **Propagate to Route Tables**. Additionally, routes will be propagated to route tables that have labels specified as **Propagate to labels**. These routes can be propagated inter-hub, except for the default route 0/0.
25+
* **Propagate static route**: This setting lets you propagate static routes defined in the **Static routes** section to route tables specified in **Propagate to Route Tables**. Additionally, routes will be propagated to route tables that have labels specified as **Propagate to labels**. These routes can be propagated inter-hub, except for the default route 0/0.
2626

27-
1. Once you've completed the settings you want to configure, click **Create** to create the connection.
27+
1. Once you've completed the settings you want to configure, select **Create** to create the connection.

0 commit comments

Comments
 (0)