Check Route Server peering locality before using an on-premises NVA address

Source facts

Microsoft’s Route Server peering tutorial supports NVAs in the same virtual network or a directly peered virtual network. It explicitly excludes BGP peering between Route Server and an on-premises NVA. The tutorial’s FRRouting VM is a demonstration appliance; Microsoft directs production deployments to supported network appliances from Azure Marketplace. Microsoft Learn.

Applicability

Apply this check when selecting the BGP peer endpoint for Route Server. Identify where the appliance is deployed and whether its virtual network is directly peered. Keep laboratory routing demonstrations separate from the production appliance selection.

DSE recommendation

DSE recommends recording both the peer address and its network placement in the design. Resolve an ineligible on-premises endpoint through an appropriate reviewed architecture rather than repeated firewall exceptions. Confirm the chosen appliance vendor’s guidance for the intended topology and preserve the expected peer and route list before the pilot.

Verification

Inspect actual VNet placement and peering, then verify the approved BGP session and intended learned prefixes in a test deployment. Check that workload routes reflect the expected advertisements. Record topology eligibility separately from connectivity results; a reachable TCP endpoint or successful laboratory session alone does not establish a supported production design.

Official references

Microsoft Learn: Tutorial: Configure BGP peering between Azure Route Server and NVA.