Using static routes adds more fixed configuration to the border and to ToR devices. Static routes require thorough analysis before you make any change. Issues that are caused by a configuration error might take more time to roll back depending on the changes you made. We do not recommend static routing, but it is supported.
To integrate Microsoft Azure Stack Hub into your networking environment by using this method, the border device must be configured with static routes pointing to the ToR devices for traffic that is destined for external networks or public VIPs.
Configure the ToR devices with a static default route that sends all traffic to the border devices. The one traffic exception to this rule is for the private space, which is blocked using an ACL that is applied on the ToR to the border connection.
The remaining configuration is the same as it is for BGP routing. The BGP dynamic routing is still used inside the rack. It is an essential tool for the SLB and other components and cannot be disabled or removed.
Figure 53. Static routing for Microsoft Azure Stack Hub cloud network