I have a vMX deployed into an Azure vWAN environment. EBGP has been configured on the vMX to the vWAN Hub. iBGP is formed on top of Auto VPN directly from the Branch to the vMX in the Azure cloud. I also have a MX Hub on our primary site, and MX Spokes at various branch sites. On the Spoke sites, neither the vMX nor the primary site MX Hub have the IPv4 default route checked On the primary site MX Hub, no Exit hubs have been added.   The Azure vHub is learning a default route (0/0) from a connected ExpressRoute When the vMX eBGP is configured, the remote Hub & Spoke sites learn the default route via iBGP of the vWAN. The iBGP learnt default route is taking precedence over the Default WAN Route, therefore all unknown traffic traverses the auto-vpn up to the Azure vWAN and down the ExpressRoute.   For the MX Spokes, the precedence of the default route can be changed back to the Default WAN Route by adding a VPN exclusion rule under the Local internet breakout. But Local internet breakout option doesn't show for the MX Hub.   Is there a way on the MX Hub for the Default WAN Route to have the higher precedence?     ... View more