Skip to content

Commit 79452e5

Browse files
committed
add table and note
1 parent 83a196e commit 79452e5

File tree

1 file changed

+16
-2
lines changed

1 file changed

+16
-2
lines changed

articles/expressroute/how-to-move-peering.md

Lines changed: 16 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,17 +5,31 @@ services: expressroute
55
author: duongau
66
ms.service: expressroute
77
ms.topic: how-to
8-
ms.date: 04/28/2021
8+
ms.date: 04/07/2023
99
ms.author: duau
10-
1110
---
1211

1312
# Move a public peering to Microsoft peering
1413

1514
This article helps you move a public peering configuration to Microsoft peering with no downtime. ExpressRoute supports using Microsoft peering with route filters for Azure PaaS services, such as Azure storage and Azure SQL Database. You now need only one routing domain to access Microsoft PaaS and SaaS services. You can use route filters to selectively advertise the PaaS service prefixes for Azure regions you want to consume.
1615

16+
> [!IMPORTANT]
17+
> 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/).
18+
19+
1720
Azure public peering has 1 NAT IP address associated to each BGP session. Microsoft peering allows you to configure your own NAT allocations, as well as use route filters for selective prefix advertisements. Public Peering is a unidirectional service using which Connectivity is always initiated from your WAN to Microsoft Azure services. Microsoft Azure services will not be able to initiate connections into your network through this routing domain.
1821

22+
## Peering comparison
23+
24+
| Aspect | Public peering | Microsoft peering |
25+
| --- | --- | --- |
26+
| Number of NAT IP addresses | 1 (not scalable) | Per scale*** |
27+
| Call initiation direction | Unidirectional: on-premises to Microsoft | Bidirectional |
28+
| Prefix advertisement | Non-selectable | Advertisement of Microsoft prefixes is controlled by route filters |
29+
| Support | No new public peering deployments. Public peering will be retired on March 31, 2024. | Fully supported |
30+
31+
*** BYOIP: you can scale the number of NAT IP addresses assigned depending on your call volume. To get NAT IP addresses, work with your service provider.
32+
1933
Once public peering is enabled, you can connect to all Azure services. We do not allow you to selectively pick services for which we advertise routes to. While Microsoft peering is a bi-directional connectivity where connection can be initiated from Microsoft Azure service along with your WAN. For more information about routing domains and peering, see [ExpressRoute circuits and routing domains](expressroute-circuit-peerings.md).
2034

2135
## <a name="before"></a>Before you begin

0 commit comments

Comments
 (0)