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
Copy file name to clipboardExpand all lines: articles/virtual-network-manager/concept-user-defined-route.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -88,16 +88,16 @@ You can also easily choose an Azure Firewall as the next hop by selecting **Impo
88
88
89
89
### Use more user-defined routes in a single route table
90
90
91
-
In Azure Virtual Network Manager UDR management, users can now create up to 1,000 user-defined routes (UDRs) in a single route table, compared to the traditional 400-route limit. This higher limit enables more complex routing configurations, such as directing traffic from on-premises data centers through a firewall to each spoke virtual network in a hub-and-spoke topology. This expanded capacity is especially useful for managing traffic inspection and security across large-scale network architectures with numerous spokes.
91
+
In Azure Virtual Network Manager UDR management, users can now create up to 1,000 user-defined routes in a single route table, compared to the traditional 400-route limit. This higher limit enables more complex routing configurations, such as directing traffic from on-premises data centers through a firewall to each spoke virtual network in a hub-and-spoke topology. This expanded capacity is especially useful for managing traffic inspection and security across large-scale network architectures with numerous spokes.
92
92
93
-
For example, in a hubandspoke topology, it is common for users to require network traffic to be inspected or filtered by a firewall in the hub virtual network before reaching the spoke virtual networks. The Azure Virtual Network Manager supports up to 1000 spoke virtual networks and allows the configuration of the gateway subnet's route table to support up to 1000 User-Defined Routes for traffic from the firewall to the spoke virtual networks. To achieve this, follow these steps:
93
+
In a hub-and-spoke topology, it's common for users to require that network traffic be inspected or filtered by a firewall located in the hub virtual network before reaching any spoke virtual networks. Azure Virtual Network Manager supports up to 1,000 spoke virtual networks and allows you to configure the route table associated with the gateway subnet to include up to 1,000 user-defined routes. To set this up, follow these steps:
94
94
1. Create an Azure Virtual Network Manager instance.
95
-
1. Create a network group and include the gateway containing the firewall in this group.
95
+
1. Create a network group and include the gateway subnet in this network group.
96
96
1. Establish a routing configuration and create a rule collection, setting the target network group as the one created in Step 2.
97
97
1. Define a routing rule by adding the address spaces of the spoke virtual networks. Set the next hop to "virtual appliance" and specify the firewall's IP address as the next hop address.
98
98
1. Deploy this routing configuration in the region where the gateway subnet is located.
99
99
100
-
This method allows the firewall gateway's route table to accommodate up to 1000 UDRs. When adding a new spoke virtual network, simply include its address spaces in the existing rule and redeploy the routing configuration.
100
+
This method allows the route table of the gateway subnet to accommodate up to 1000 user-defined routes. When adding a new spoke virtual network, simply include its address spaces in the existing rule and redeploy the routing configuration.
0 commit comments