Skip to content

Commit 2eb9d35

Browse files
committed
update information about public peering
1 parent c61df1c commit 2eb9d35

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

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

0 commit comments

Comments
 (0)