+No. If **branch-to-branch** is enabled, then the NVA-advertised routes will be advertised to the ExpressRoute-connected on-premises. However, the NVA-advertised routes will be dropped by the second Route Server. To illustrate this, the diagram below shows the SDWAN on-premises advertising 10.3.0.0/16 to the SDWAN NVA. This route gets learned by the first Route Server, and so any workloads in VNet 1 (or peered to VNet 1) also learn this route. In addition, the ExpressRoute-connected on-premises learns the 10.3.0.0/16 route if **branch-to-branch** is enabled. However, the second Route Server (in VNet 2) does not learn the 10.3.0.0/16 route, and so this route will not be learned by any workloads in VNet 2. As a result, the 10.3.0.0/16 on-premises network will be unreachable from any workloads in VNet 2 and peered to VNet 2.
0 commit comments