Merge pull request #313606 from wtnlee/somebugfixes

hello

Author: prmerger-automator[bot]

articles/virtual-wan/about-virtual-hub-routing-preference.md

@@ -43,7 +43,7 @@ You can select one of the three possible virtual hub routing preference configur
 * **AS Path**
 
    1. Prefer routes with the shortest BGP AS-Path length irrespective of the source of the route advertisements.
-      * Note: In vWANs with multiple remote virtual hubs, remote ExpressRoute routes will be selected last. This behavior is true regardless of AS-Path length.
+      * Note: All routes learnt from ExpressRoute circuits connected to remote hub(s) are selected last by the local hub. This behavior is true regardless of remote route AS-Path length.
 
    1. Prefer routes from local virtual hub connections over routes learned from remote virtual hub.
    1. If there are routes from both ExpressRoute and Site-to-site VPN connections:

articles/virtual-wan/whats-new.md

@@ -101,7 +101,7 @@ The following features are currently in gated public preview. After working with
 |2| Default routes (0/0) won't propagate inter-hub |0/0 routes won't propagate between two virtual WAN hubs. | June 2020 |  None. Note: While the Virtual WAN team has fixed the issue, wherein static routes defined in the static route section of the Virtual Network peering page propagate to route tables listed in "propagate to route tables" or the labels listed in "propagate to route tables" on the Virtual Network connection page, default routes (0/0) won't propagate inter-hub. |
 |3| Two ExpressRoute circuits in the same peering location connected to multiple hubs |If you have two ExpressRoute circuits in the same peering location, and both of these circuits are connected to multiple virtual hubs in the same Virtual WAN, then connectivity to your Azure resources might be impacted. | July 2023 | Make sure each virtual hub has at least 1 virtual network connected to it. This ensures connectivity to your Azure resources. The Virtual WAN team is also working on a fix for this issue. |
 |4| ExpressRoute ECMP Support | Today, ExpressRoute ECMP isn't enabled by default for virtual hub deployments. When 1 or more ExpressRoute circuits are connected to a Virtual WAN hub, ECMP enables traffic from spoke virtual networks to on-premises over ExpressRoute to be distributed across 2 ExpressRoute circuits (corresponding to up to 4 ExpressRoute links) advertising the same on-premises routes. | To enable ECMP for your environment, you can create a [route-map](route-maps-how-to.md) for your virtual hub. When you create a route-map, your virtual hub will automatically be upgraded to the latest software version that supports ECMP, regardless of whether this route-map is applied on any connections. As a result, you only need to follow steps 1-7 [here](route-maps-how-to.md#configuration-workflow). If you do not plan to use the route-map, you can delete the route-map after step 7 is complete, as hubs with a route-map will incur additional cost. It is also recommended to first try creating a route-map in your test environment and validating routing and connectivity before creating a route-map in your production environment.  |
-| 5| Virtual WAN hub address prefixes aren't advertised to other Virtual WAN hubs in the same Virtual WAN.| You can't leverage Virtual WAN hub-to-hub full mesh routing capabilities to provide connectivity between  NVA orchestration software deployed in a virtual network or on-premises connected to a Virtual WAN hub to an Integrated NVA or SaaS solution deployed in a different Virtual WAN hub.  | | If your NVA or SaaS orchestrator is deployed on-premises, connect that on-premises site to all Virtual WAN hubs with NVAs or SaaS solutions deployed in them. If your orchestrator is in an Azure virtual network, manage NVAs or SaaS solutions using public IP. Support for Azure virtual network orchestrators is on the roadmap.|
+| 5| Virtual WAN hub address prefixes aren't advertised to other Virtual WAN hubs in the same Virtual WAN.| You can't always leverage Virtual WAN hub-to-hub full mesh routing capabilities to provide connectivity between  NVA orchestration software deployed in a virtual network or on-premises connected to a Virtual WAN hub to an Integrated NVA or SaaS solution deployed in a different Virtual WAN hub (see mitigation of this known issue for exceptions). | | If your NVA or SaaS orchestrator is deployed on-premises, connect that on-premises site to all Virtual WAN hubs with NVAs or SaaS solutions deployed in them. If your orchestrator is deployed in a Virtual Network connected to a Virtual WAN hub with routing intent private policies, the orchestrator will be able to reach NVA or SaaS solution deployed in a different hub. Otherwise, manage NVAs or SaaS solutions using public IP. Full support for Azure virtual network orchestrators is on the roadmap.|
 |6| Configuring routing intent to route between connectivity and firewall NVAs in the same Virtual WAN hub| Virtual WAN routing intent private routing policy doesn't support routing between an SD-WAN NVA and a Firewall NVA (or SaaS solution) deployed in the same Virtual hub.| | Deploy the connectivity and firewall integrated NVAs in two different hubs in the same Azure region. Alternatively, deploy the connectivity NVA to a spoke Virtual Network connected to your Virtual WAN hub and leverage the [BGP peering](scenario-bgp-peering-hub.md).|
 | 7| BGP between the Virtual WAN hub router and NVAs deployed in the Virtual WAN hub doesn't come up if the ASN used for BGP peering is updated post-deployment.|Virtual hub router expects NVA in the hub to use the ASN that was configured on the router when the NVA was first deployed. Updating the ASN associated with the NVA on the NVA resource doesn't properly register the new ASN with the Virtual hub router so the router rejects BGP sessions from the NVA if the NVA OS is configured to use the new ASN. | |Delete and recreate the NVA in the Virtual WAN hub with the correct ASN.|
 |8| Routing intent update operations fail in deployments where private routing policy next hop resource is an NVA or SaaS solution.| In deployments where private routing policy is configured with next hop NVA or SaaS solutions alongside additional private prefixes, modifying routing intent fails. Examples of operations that fail are adding or removing internet or private routing policies. This known issue doesn't impact deployments with no additional private prefixes configured. | |Remove any additional private prefixes, update routing intent and then reconfigure additional private prefixes.|