Merge pull request #250368 from duongau/patch-14

ExpressRoute - BGP community (Remove pre-req about vWAN)

Author: prmerger-automator[bot]

articles/expressroute/how-to-configure-custom-bgp-communities.md

@@ -6,7 +6,7 @@ author: duongau
 ms.service: expressroute
 ms.custom: devx-track-azurepowershell
 ms.topic: how-to
-ms.date: 12/27/2022
+ms.date: 09/05/2023
 ms.author: duau
 ---
 
@@ -18,7 +18,7 @@ BGP communities are groupings of IP prefixes tagged with a community value. This
 
 * Review the [prerequisites](expressroute-prerequisites.md), [routing requirements](expressroute-routing.md), and [workflows](expressroute-workflows.md) before you begin configuration.
 
-* You must have an active ExpressRoute circuit in a **non-vWAN environment**. This feature isn't supported for ExpressRoute with vWAN. 
+* You must have an active ExpressRoute circuit.
   * Follow the instructions to [create an ExpressRoute circuit](expressroute-howto-circuit-arm.md) and have the circuit enabled by your connectivity provider. 
   * Ensure that you have Azure private peering configured for your circuit. See the [configure routing](expressroute-howto-routing-arm.md) article for routing instructions. 
   * Ensure that Azure private peering gets configured and establishes BGP peering between your network and Microsoft for end-to-end connectivity.