In the previous section of this guide, we focused on pre-work along with with deployment of AVS and Everpure Cloud Dedicated themselves. If both of those items are not in an available state, please wait for the deployments to complete and/or revisit the first section of this guide as you will not be able to complete this section until AVS and Everpure Cloud Dedicated are both deployed and available.
The Azure Virtual Network Gateway is the key component for connecting AVS and Everpure Cloud Dedicated. Azure Virtual Network Gateways are available in multiple SKUs that are primarily differentiated by the level of network bandwidth, performance and Availability Zone affinity.
To provide maximum network bandwidth between AVS and Everpure Cloud Dedicated, it is strongly recommend selecting the ErGw3AZ SKU for the Virtual Network Gateway as this SKU provides the Ultra SKU performance, allows you to deploy it into the same Azure Availability Zones as Everpure Cloud Dedicated and AVS and lastly offers another unique important capability called: FastPath. This section will cover requirements and steps for deployment of such a Virtual Network Gateway.
More information about the FastPath feature can be found at this link. The key reason it is beneficial for the AVS and Everpure Cloud Dedicated connection is that it allows virtual machine traffic from AVS to go directly to the Azure VNet Everpure Cloud Dedicated is attached to, bypassing the gateway.
GatewaySubnet Deployment
To begin the Ultra Virtual Network Gateway deployment, you first need to add a Gateway Subnet to the Azure VNet that Everpure Cloud Dedicated is utilizing.
Navigate to the Azure VNet that Everpure Cloud Dedicated is leveraging, select the Subnets sub-menu and then select the + Gateway subnet button.
From the Add subnet wizard, the subnet address range will be pre-populated with an available range but you may optionally input a CIDR block range for the Gateway subnet. Click on Save when finished.
After successful deployment, inspect your VNet subnets to confirm that the GatewaySubnet exists.
Azure Ultra Virtual Network Gateway Deployment
After successfully adding a Virtual Network Gateway subnet to your Azure VNet, you can next deploy the Virtual Network Gateway itself. To begin, search for virtual network gateway in the Azure Marketplace and then click on the create button on the appropriate tile.
From the creation wizard, please see the below screenshot and itemized list of fields to fill out for using the virtual network gateway with AVS.
For Virtual Network Gateway resources deployed starting in August 2025 or later, you no longer need to manually create an Azure Public IP resource. Azure automatically creates and manages this resource in the background, and Public IP resources are now zone-redundant by default.
If you deployed a Virtual Network Gateway resource before this change, please consider migrating. For details, see Migration guidance on Microsoft Learn.
- Subscription: Select the subscription you will be using for AVS and Everpure Cloud Dedicated.
- Name: Select a descriptive name for the Azure Virtual Network Gateway.
- Region: The region selection should be the same as where AVS and Everpure Cloud Dedicated are deployed.
- Gateway Type: The ExpressRoute option is required. The VPN Gateway type will not work with this solution.
- Gateway SKU: For optimal performance, the ErGw3AZ SKU is strongly recommended.
- Azure Virtual Network: Select the same Azure virtual network you deployed Everpure Cloud Dedicated with.
- Gateway Subnet: The GatewaySubnet field should be automatically filled in when the Azure VNet is selected. If a Gateway subnet is not populated, see the previous section of this article for how to create a GatewaySubnet as this is required for virtual network gateway deployment to succeed.
- Review the configuration selections made for the virtual network gateway. If everything is correct, click on the Create button to begin the deployment. Note that this deployment can take anywhere from thirty minutes to an hour to complete.