Skip to content

Commit f706059

Browse files
Merge pull request #233359 from duongau/erpubpeering
ExpressRoute - Public peering retirement notice and FAQ update
2 parents 6e334fe + ff6bcf8 commit f706059

File tree

3 files changed

+9
-2
lines changed

3 files changed

+9
-2
lines changed

articles/expressroute/expressroute-circuit-peerings.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,9 @@ ms.author: duau
1212
---
1313
# ExpressRoute circuits and peering
1414

15+
> [!IMPORTANT]
16+
> Public peering for ExpressRoute is being retired on **March 31, 2024**. For more information, see [**retirement notice**](https://azure.microsoft.com/updates/retirement-notice-migrate-from-public-peering-by-march-31-2024/).
17+
1518
ExpressRoute circuits connect your on-premises infrastructure to Microsoft through a connectivity provider. This article helps you understand ExpressRoute circuits and routing domains/peering. The following figure shows a logical representation of connectivity between your WAN and Microsoft.
1619

1720
![Diagram showing how ExpressRoute circuits connect your on-premises infrastructure to Microsoft through a connectivity provider.](./media/expressroute-circuit-peerings/expressroute-basic.png)

articles/expressroute/expressroute-faqs.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -104,9 +104,10 @@ If your ExpressRoute circuit is enabled for Azure Microsoft peering, you can acc
104104

105105
### Public peering
106106

107-
Public peering has been disabled on new ExpressRoute circuits. Azure services are now available on Microsoft peering. If you have a circuit that was created before public peering was deprecated, you can choose to use Microsoft peering or public peering, depending on the services that you want.
107+
Public peering is no longer available on new ExpressRoute circuits and is scheduled for retirement on March 31, 2024. Access to Azure services can be done through Microsoft peering. To avoid disruption to your services, you should migrate to Microsoft peering before the retirement date.
108108

109-
For more information and configuration steps for public peering, see [ExpressRoute public peering](about-public-peering.md).
109+
* For more information, see [Migrate from public peering to Microsoft peering](how-to-move-peering.md).
110+
* For a comparison between the different peering types, see [Peering comparison](about-public-peering.md#compare).
110111

111112
### Why I see 'Advertised public prefixes' status as 'Validation needed', while configuring Microsoft peering?
112113

articles/expressroute/expressroute-introduction.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,9 @@ ms.author: duau
1212

1313
# What is Azure ExpressRoute?
1414

15+
> [!IMPORTANT]
16+
> Public peering for ExpressRoute is being retired on **March 31, 2024**. For more information, see [**retirement notice**](https://azure.microsoft.com/updates/retirement-notice-migrate-from-public-peering-by-march-31-2024/).
17+
1518
ExpressRoute lets you extend your on-premises networks into the Microsoft cloud over a private connection with the help of a connectivity provider. With ExpressRoute, you can establish connections to Microsoft cloud services, such as Microsoft Azure and Microsoft 365.
1619

1720
Connectivity can be from an any-to-any (IP VPN) network, a point-to-point Ethernet network, or a virtual cross-connection through a connectivity provider at a colocation facility. ExpressRoute connections don't go over the public Internet. This allows ExpressRoute connections to offer more reliability, faster speeds, consistent latencies, and higher security than typical connections over the Internet. For information on how to connect your network to Microsoft using ExpressRoute, see [ExpressRoute connectivity models](expressroute-connectivity-models.md).

0 commit comments

Comments
 (0)