Check deployment eligibility before proposing a High Bandwidth VPN gateway upgrade

Source facts

Microsoft’s High Bandwidth tunnel guidance lists no migration path from existing gateways. It describes the capability as operating over ExpressRoute private peering and requires FastPath on the ExpressRoute connection. The documented limitations also exclude point-to-site connections, APIPA BGP addresses, NAT, IPv6 and Virtual WAN interoperability. Microsoft Learn.

Applicability

Use this review when assessing whether Advanced Connectivity fits an existing network. Identify current gateway functions, ExpressRoute configuration and target region. Read the latest regional and feature limitations directly before approving a design; this article does not establish eligibility for a particular deployment.

DSE recommendation

DSE recommends a requirement matrix that marks each current dependency against the documented limitations. Treat the absence of a migration path as a planning issue requiring an explicit replacement design. Assign owners for application continuity, address changes and recovery, and reject a simple in-place-upgrade assumption until the complete deployment plan is reviewed.

Verification

Validate the proposed configuration in an approved isolated environment that meets the documented prerequisites. Check each required tunnel, route and application path, and record any unsupported dependency as an unresolved design issue. Keep observed throughput or connectivity separate from proof that all former gateway functions have an accepted replacement.

Official references

Microsoft Learn: Create site-to-site high bandwidth tunnels in the Azure portal.