The Azure Virtual Edge Deployment Guide provides instructions for deploying a virtual edge in Azure using an Azure Resource Manager (ARM) Template.

More customers are moving workloads to public cloud infrastructure to extend SD-WAN from remote sites to the public cloud and achieve guaranteed Service Level Agreements (SLAs). There are multiple options offered by VeloCloud SD-WAN, leveraging distributed VeloCloud Gateways to establish IPsec connections to a public cloud or private network, or to deploy the Virtual Edge directly in Azure.

For a small branch deployment that demands throughput less than 1G, a single virtual edge can be deployed in the private network (Azure vNets). For larger data center deployments that demand multi-gig throughput, Hub clustering can be deployed.

Note: In the VeloCloud Hub clustering design, a Layer 3 Instance is leveraged on the LAN side to run BGP between Hubs in the cluster and the Layer 3 Instance for route distribution in LAN. Since the Azure UDR does not support dynamic routing protocol, a third-party virtual router is required in the Azure infrastructure.