Skip to content

Commit 9e3ffc5

Browse files
Merge pull request #222493 from duongau/erbgpps
ExpressRoute BGP communities - PowerShell - freshness review
2 parents ead7aa3 + f81f7d7 commit 9e3ffc5

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: expressroute
55
author: duongau
66
ms.service: expressroute
77
ms.topic: how-to
8-
ms.date: 10/18/2021
8+
ms.date: 12/27/2022
99
ms.author: duau
1010
---
1111

@@ -17,7 +17,7 @@ BGP communities are groupings of IP prefixes tagged with a community value. This
1717

1818
* Review the [prerequisites](expressroute-prerequisites.md), [routing requirements](expressroute-routing.md), and [workflows](expressroute-workflows.md) before you begin configuration.
1919

20-
* You must have an active ExpressRoute circuit in a **non-vWAN environment**. This feature is not supported for ExpressRoute with vWAN.
20+
* You must have an active ExpressRoute circuit in a **non-vWAN environment**. This feature isn't supported for ExpressRoute with vWAN.
2121
* Follow the instructions to [create an ExpressRoute circuit](expressroute-howto-circuit-arm.md) and have the circuit enabled by your connectivity provider.
2222
* Ensure that you have Azure private peering configured for your circuit. See the [configure routing](expressroute-howto-routing-arm.md) article for routing instructions.
2323
* Ensure that Azure private peering gets configured and establishes BGP peering between your network and Microsoft for end-to-end connectivity.

0 commit comments

Comments
 (0)