hello

Author: wtnlee

articles/virtual-wan/about-nva-hub.md

@@ -116,7 +116,7 @@ If the total amount of traffic that passes through an NVA at a given time goes a
 
 ### Hub address space
 
-Every Virtual WAN hub is allocated a hub address space. The minimum recommended hub address space is /23. Virtual WAN automatically carves out subnets within the hub to deploy different services within the Virtual WAN hub such as Azure Firewalls, NVAs and gateway connectivity services. 
+Every Virtual WAN hub is deployed with a hub address space. The minimum recommended hub address space is /23. Virtual WAN automatically carves out subnets within the hub to deploy different services within the Virtual WAN hub such as Azure Firewalls, NVAs and gateway connectivity services.
 
 There are a limited number of IP addresses available in the Virtual WAN hub that can be assigned to the internal or external subnet of NVA deployments. The number of IP addresses allocated to either the internal or external subnet of NVAs is static for all Virtual WAN hubs deployed with a specific address size, irrespective of whether or not customers utilize or plan to utilize all services in the Virtual WAN hub. Service-level allocation can't be modified.
 
@@ -129,7 +129,7 @@ The following table describes the number of IP addresses available for NVA deplo
 |/21|59| 59|
 |/20 or larger| 123| 123|
 
-#### Consumed IP addresses
+#### <a name="ipconsumed" ></a> Consumed IP addresses
 
 >[NOTE]
 > Select your hub address space with scalability taken into consideration as the subnets allocated to NVAs can't be re-sized. Actions such as deploying multiple NVAs in the hub or adding additional IP configurations to existing NVAs requires sufficient available IP addresses.

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

@@ -48,6 +48,19 @@ To deploy a Network Virtual Appliance in a Virtual WAN Hub, the user or service
 
 These permissions need to be granted to the Azure Marketplace Managed Application to ensure deployments succeed. Other permissions may be required based on the implementation of the deployment workflow developed by your NVA partner.
 
+## Hub address space
+
+Each Virtual WAN hub has a fixed subnet size used for NVA deployments. The number of IP addresses available for consumption is statically defined for all hub address sizes.
+
+Ensure your Virtual WAN hub has sufficient IP addresses to allow for scalability and future network deployment updates:
+
+* Deploy additional NVAs (more than one) in the hub.
+* Add additional IP configurations to your NVA interfaces.
+* Re-size your NVA (increase scale unit).
+
+For more information on how Virtual WAN allocates IP addresses to NVAs in the hub, see [hub address space for NVAs documentation](about-nva-hub.md#hub-address-space).
+
+
 ## Assigning Permissions to Azure Managed Application
 
 Network Virtual Appliances that are deployed via Azure Marketplace Managed Application are deployed in a special resource group in your Azure tenant called the **managed resource group**. When you create a Managed Application in your subscription, a corresponding and separate **managed resource group** is created in your subscription. All Azure resources created by the Managed Application (including the Network Virtual Appliance) are deployed into the **managed resource group**.