Build Route Server configs with BGP peerings to network virtual appliances, branch-to-branch traffic, and hub routing preferences.
Build Route Server configs with BGP peerings to network virtual appliances, branch-to-branch traffic, and hub routing preferences.
Required Fields
nameresourceGrouplocationvirtualNetwork.routeServerSubnet.addressPrefixbgpPeeringsbgpPeerings[0].peerAsnbgpPeerings[0].peerIpOutput will appear here...Build an Azure Route Server configuration establishing BGP peerings with network virtual appliances (firewalls, SD-WAN devices), letting NVAs exchange routes dynamically with the Azure VNet's routing infrastructure without manually maintaining User Defined Routes for every destination. hubRoutingPreference determines how Route Server resolves competing routes to the same destination learned from multiple sources (ExpressRoute, VPN, and NVA-advertised routes), setting it to ExpressRoute means ExpressRoute-learned routes win ties over equally-specific routes from other sources, a subtle but consequential choice for a hybrid network with multiple connectivity paths to the same on-prem destination.
Peer redundant NVA instances at the same ASN specifically to get automatic BGP-based failover, this is the actual mechanism providing resilience, not the Route Server's own redundancy alone (Route Server itself is deployed with built-in redundancy, but that doesn't cover an NVA instance failure).
hubRoutingPreference is a real design decision with traffic-path consequences, don't leave it at a default without considering which connectivity type (ExpressRoute, VPN, or NVA) should actually win when routes overlap in your specific hybrid topology.
The dedicated RouteServerSubnet has its own Azure-mandated naming and sizing requirements similar to Bastion's subnet, verify current requirements before assuming any subnet name/size will work.
The builder validates that name, resourceGroup, location, virtualNetwork.routeServerSubnet.addressPrefix, bgpPeerings, and the first peering's peerAsn/peerIp all resolve before accepting the JSON as a valid Route Server definition, the fields Azure needs to provision the service and establish its BGP peering relationships; it can't verify the referenced NVA's own BGP configuration actually matches (same ASN expectations, reachable peer IP), that's only confirmed once the BGP session actually attempts to establish.
Was this tool helpful?
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.