Merge pull request #126522 from cfields475/patch-6

Update route-maps-about.md

Author: v-regandowner

articles/virtual-wan/route-maps-about.md

@@ -58,7 +58,6 @@ Before using Route-maps, take into consideration the following limitations:
   *  65517:12001, 65517:12002, 65517:12003, 65517:12005, 65517:12006, 65518:65518, 65517:65517, 65517:12076, 65518:12076, 65515:10000, 65515:20000
 * You can't apply Route-maps to connections between on-premises and SD-WAN/Firewall NVAs in the virtual hub. You can still apply route-maps to other supported connections when an NVA in the virtual hub is deployed. This doesn't apply to the Azure Firewall, as the routing for Azure Firewall is provided through Virtual WAN [routing intent features](how-to-routing-policies.md).
 * Route-maps only supports 2-byte ASN numbers.
-* The point-to-site (P2S) Multipool feature isn't currently supported with Route-maps.
 * Modifying the *Default* route is only supported when the default route is learned from on-premises or an NVA.
 * A prefix can be modified either by Route-maps, or by NAT, but not both.
 * Route-maps won't be applied to the [hub address space](virtual-wan-site-to-site-portal.md#hub).