Skip to content

Commit 2fe9bd6

Browse files
JamesJBarnettJamesJBarnett
authored
Merge pull request #300573 from MSFT-FrankLpnsk/finalautoscale
[Virtual WAN] True final autoscale PR - 05.29.2025
2 parents d04f741 + 5a9d70b commit 2fe9bd6

File tree

1 file changed

+67
-58
lines changed

1 file changed

+67
-58
lines changed

‎articles/virtual-wan/hub-settings.md

Lines changed: 67 additions & 58 deletions
Original file line numberDiff line numberDiff line change
@@ -13,17 +13,17 @@ ms.author: cherylmc
1313

1414
This article helps you understand the various settings available for virtual hubs. A virtual hub is a Microsoft-managed virtual network that contains various service endpoints to enable connectivity. The virtual hub is the core of your network in a region. Multiple virtual hubs can be created in the same region.
1515

16-
A virtual hub can contain gateways for site-to-site VPN, ExpressRoute, or point-to-site User VPN. For example, when using Virtual WAN, you don't create a site-to-site connection from your on-premises site directly to your VNet. Instead, you create a site-to-site connection to the virtual hub. The traffic always goes through the virtual hub gateway. This means that your VNets don't need their own virtual network gateway. Virtual WAN lets your VNets take advantage of scaling easily through the virtual hub and the virtual hub gateway. For more information about gateways, see [Gateway settings](gateway-settings.md). Note that a virtual hub gateway isn't the same as a virtual network gateway that you use for ExpressRoute and VPN Gateway.
16+
A virtual hub can contain gateways for site-to-site VPN, ExpressRoute, or point-to-site User VPN. For example, when using Virtual WAN, you don't create a site-to-site connection from your on-premises site directly to your VNet. Instead, you create a site-to-site connection to the virtual hub. The traffic always goes through the virtual hub gateway. This means that your VNets don't need their own virtual network gateway. Virtual WAN lets your VNets take advantage of scaling easily through the virtual hub and the virtual hub gateway. For more information about gateways, see [Gateway settings](gateway-settings.md). A virtual hub gateway isn't the same as a virtual network gateway that you use for ExpressRoute and VPN Gateway.
1717

18-
When you create a virtual hub, a virtual hub router is deployed. The virtual hub router, within the Virtual WAN hub, is the central component that manages all routing between gateways and virtual networks (VNets). Routing infrastructure units determine the minimum throughput of the virtual hub router, and the number of virtual machines that can be deployed in VNets that are connected to the Virtual WAN virtual hub.
18+
When you create a virtual hub, a virtual hub router is deployed. The virtual hub router, within the Virtual WAN hub, is the central component that manages all routing between gateways and virtual networks (VNets). Routing infrastructure units determine the throughput of the virtual hub router, and the number of virtual machines that can be deployed in VNets that are connected to the Virtual WAN virtual hub.
1919

20-
You can create an empty virtual hub (a virtual hub that doesn't contain any gateways) and then add gateways (S2S, P2S, ExpressRoute, etc.) later, or create the virtual hub and gateways at the same time. Once a virtual hub is created, virtual hub pricing applies, even if you don't create any gateways within the virtual hub. For more information, see [Azure Virtual WAN pricing](https://azure.microsoft.com/pricing/details/virtual-wan/).
20+
You can create an empty virtual hub (a virtual hub that doesn't contain any gateways) and then add gateways (S2S, P2S, ExpressRoute, etc.) later. You can also create the virtual hub and gateways at the same time. Once a virtual hub is created, virtual hub pricing applies, even if you don't create any gateways within the virtual hub. For more information, see [Azure Virtual WAN pricing](https://azure.microsoft.com/pricing/details/virtual-wan/).
2121

2222
## <a name="capacity"></a>Virtual hub capacity
2323

24-
By default, the virtual hub router is automatically configured to deploy with a virtual hub capacity of 2 routing infrastructure units. This supports a minimum of 3 Gbps aggregate throughput, and 2000 connected VMs deployed in all virtual networks connected to that virtual hub.
24+
By default, the virtual hub router is automatically configured to deploy with a virtual hub capacity of 2 routing infrastructure units. This supports 3-Gbps aggregate throughput and 2,000 connected VMs deployed in all virtual networks connected to that virtual hub.
2525

26-
When you deploy a new virtual hub, you can specify additional routing infrastructure units to increase the default virtual hub capacity in increments of 1 Gbps and 1000 VMs. This feature gives you the ability to secure upfront capacity without having to wait for the virtual hub to scale out when more throughput is needed. The scale unit on which the virtual hub is created becomes the minimum capacity. Creating a virtual hub without a gateway takes about 5 - 7 minutes while creating a virtual hub and a gateway can take about 30 minutes to complete. You can view routing infrastructure units, router Gbps, and number of VMs supported, in the Azure portal **Virtual hub** pages for **Create virtual hub** and **Edit virtual hub**.
26+
When you deploy a new virtual hub, you can specify additional routing infrastructure units to increase the default virtual hub capacity in increments of 1-Gbps and 1,000 VMs. This feature gives you the ability to secure upfront capacity without having to wait for the virtual hub to scale out when more throughput is needed. The scale unit on which the virtual hub is created becomes the minimum capacity. Creating a virtual hub without a gateway takes about 5 - 7 minutes while creating a virtual hub and a gateway can take about 30 minutes to complete. You can view routing infrastructure units, router Gbps, and number of VMs supported, in the Azure portal **Virtual hub** pages for **Create virtual hub** and **Edit virtual hub**.
2727

2828
When increasing the virtual hub capacity, the virtual hub router will continue to support traffic at its current capacity until the scale out is complete. It may take up to 25 minutes for the virtual hub router to scale out to additional routing infrastructure units. It's also important to note the following: currently, regardless of the number of routing infrastructure units deployed, traffic may experience performance degradation if more than 1.5 Gbps is sent in a single TCP flow.
2929

@@ -37,63 +37,72 @@ Capacity is configured on the **Basics** tab **Virtual hub capacity** setting wh
3737

3838
Adjust the virtual hub capacity when you need to support additional virtual machines and the aggregate throughput of the virtual hub router.
3939

40-
To add additional virtual hub capacity, go to the virtual hub in the Azure portal. On the **Overview** page, click **Edit virtual hub**. Adjust the **Virtual hub capacity** using the dropdown, then **Confirm**.
40+
To add additional virtual hub capacity, go to the virtual hub in the Azure portal. On the **Overview** page, select **Edit virtual hub**. Adjust the **Virtual hub capacity** using the dropdown, then **Confirm**.
41+
42+
#### Autoscaling
43+
The virtual hub router supports autoscaling based on spoke VM utilization and data processed by the hub router. See [Azure Virtual WAN monitoring data reference](monitor-virtual-wan-reference.md#metrics) for more details. As these factors change over time, the autoscaling algorithm dynamically adjusts the number of routing infrastructure units. It ensures the virtual hub router can handle the traffic load by selecting the greater value between the minimum routing infrastructure units you specify and the units required to support the current traffic load.
44+
45+
Autoscaling can help in various scenarios where the hub router requires additional processing capabilities; autoscaling isn't instantaneous however. For improved infrastructure availability and performance, ensure that your minimum provisioned routing infrastructure units (RIUs) match the requirements of your workloads. Autoscaling won't reduce the provisioned RIUs below this minimum.
46+
47+
Also consider:
48+
- The virtual hub router only scales on the data it processes, as clarified in [Azure Virtual WAN monitoring data reference](monitor-virtual-wan-reference.md#category-traffic). Review how your Virtual WAN processes data to ensure that resources are provisioned correctly.
49+
- Autoscaling can potentially affect connectivity for Private Endpoints. Review your deployment and adhere to the best practices outlined in [Use Private Link in Virtual WAN](howto-private-link.md#routing-considerations-with-private-link-in-virtual-wan).
4150

4251
### Routing infrastructure unit table
4352

4453
For pricing information, see [Azure Virtual WAN pricing](https://azure.microsoft.com/pricing/details/virtual-wan/).
4554

46-
| Routing infrastructure unit | Aggregate throughput<br>Gbps| Number of VMs |
47-
| ---| ---| --- |
48-
| 2 | 3 | 2000 |
49-
| 3 | 3 | 3000 |
50-
| 4 | 4 | 4000 |
51-
| 5 | 5 | 5000 |
52-
| 6 | 6 | 6000 |
53-
| 7 | 7 | 7000 |
54-
| 8 | 8 | 8000 |
55-
| 9 | 9 | 9000 |
56-
| 10 | 10 | 10000 |
57-
| 11 | 11 | 11000 |
58-
| 12 | 12 | 12000 |
59-
| 13 | 13 | 13000 |
60-
| 14 | 14 | 14000 |
61-
| 15 | 15 | 15000 |
62-
| 16 | 16 | 16000 |
63-
| 17 | 17 | 17000 |
64-
| 18 | 18 | 18000 |
65-
| 19 | 19 | 19000 |
66-
| 20 | 20 | 20000 |
67-
| 21 | 21 | 21000 |
68-
| 22 | 22 | 22000 |
69-
| 23 | 23 | 23000 |
70-
| 24 | 24 | 24000 |
71-
| 25 | 25 | 25000 |
72-
| 26 | 26 | 26000 |
73-
| 27 | 27 | 27000 |
74-
| 28 | 28 | 28000 |
75-
| 29 | 29 | 29000 |
76-
| 30 | 30 | 30000 |
77-
| 31 | 31 | 31000 |
78-
| 32 | 32 | 32000 |
79-
| 33 | 33 | 33000 |
80-
| 34 | 34 | 34000 |
81-
| 35 | 35 | 35000 |
82-
| 36 | 36 | 36000 |
83-
| 37 | 37 | 37000 |
84-
| 38 | 38 | 38000 |
85-
| 39 | 39 | 39000 |
86-
| 40 | 40 | 40000 |
87-
| 41 | 41 | 41000 |
88-
| 42 | 42 | 42000 |
89-
| 43 | 43 | 43000 |
90-
| 44 | 44 | 44000 |
91-
| 45 | 45 | 45000 |
92-
| 46 | 46 | 46000 |
93-
| 47 | 47 | 47000 |
94-
| 48 | 48 | 48000 |
95-
| 49 | 49 | 49000 |
96-
| 50 | 50 | 50000 |
55+
| Routing infrastructure unit | Aggregate throughput (Gbps) | Number of VMs |
56+
|----------------------------|-----------------------------|---------------|
57+
| 2 | 3 | 2,000 |
58+
| 3 | 3 | 3,000 |
59+
| 4 | 4 | 4,000 |
60+
| 5 | 5 | 5,000 |
61+
| 6 | 6 | 6,000 |
62+
| 7 | 7 | 7,000 |
63+
| 8 | 8 | 8,000 |
64+
| 9 | 9 | 9,000 |
65+
| 10 | 10 | 10,000 |
66+
| 11 | 11 | 11,000 |
67+
| 12 | 12 | 12,000 |
68+
| 13 | 13 | 13,000 |
69+
| 14 | 14 | 14,000 |
70+
| 15 | 15 | 15,000 |
71+
| 16 | 16 | 16,000 |
72+
| 17 | 17 | 17,000 |
73+
| 18 | 18 | 18,000 |
74+
| 19 | 19 | 19,000 |
75+
| 20 | 20 | 20,000 |
76+
| 21 | 21 | 21,000 |
77+
| 22 | 22 | 22,000 |
78+
| 23 | 23 | 23,000 |
79+
| 24 | 24 | 24,000 |
80+
| 25 | 25 | 25,000 |
81+
| 26 | 26 | 26,000 |
82+
| 27 | 27 | 27,000 |
83+
| 28 | 28 | 28,000 |
84+
| 29 | 29 | 29,000 |
85+
| 30 | 30 | 30,000 |
86+
| 31 | 31 | 31,000 |
87+
| 32 | 32 | 32,000 |
88+
| 33 | 33 | 33,000 |
89+
| 34 | 34 | 34,000 |
90+
| 35 | 35 | 35,000 |
91+
| 36 | 36 | 36,000 |
92+
| 37 | 37 | 37,000 |
93+
| 38 | 38 | 38,000 |
94+
| 39 | 39 | 39,000 |
95+
| 40 | 40 | 40,000 |
96+
| 41 | 41 | 41,000 |
97+
| 42 | 42 | 42,000 |
98+
| 43 | 43 | 43,000 |
99+
| 44 | 44 | 44,000 |
100+
| 45 | 45 | 45,000 |
101+
| 46 | 46 | 46,000 |
102+
| 47 | 47 | 47,000 |
103+
| 48 | 48 | 48,000 |
104+
| 49 | 49 | 49,000 |
105+
| 50 | 50 | 50,000 |
97106

98107
## <a name="routing-preference"></a>Virtual hub routing preference
99108

@@ -113,7 +122,7 @@ For more information about gateway settings, see [Gateway settings](gateway-sett
113122

114123
## <a name="type"></a>Basic and Standard
115124

116-
The virtual WAN type (Basic or Standard) determines the types of resources that can be created within a virtual hub, including the type of gateways that can be created (site-to-site VPN, point-to site User VPN, and ExpressRoute). This setting is configured on the virtual WAN object. For more information, see [Upgrade from Basic to Standard](upgrade-virtual-wan.md).
125+
The virtual WAN type (Basic or Standard) determines the types of resources that can be created within a virtual hub. This includes the type of gateways that can be created (site-to-site VPN, point-to site User VPN, and ExpressRoute). This setting is configured on the virtual WAN object. For more information, see [Upgrade from Basic to Standard](upgrade-virtual-wan.md).
117126

118127
The following table shows the configurations available for each virtual WAN type:
119128

0 commit comments

Comments
 (0)