Skip to content

Commit b87c648

Browse files
authored
Update expressroute-nat.md
1 parent 6e5aa29 commit b87c648

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/expressroute/expressroute-nat.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: conceptual
8-
ms.date: 06/30/2023
8+
ms.date: 06/14/2024
99
ms.author: duau
1010
---
1111

@@ -27,7 +27,7 @@ The Microsoft peering path lets you connect to Microsoft cloud services. The lis
2727
* IP addresses used for the Microsoft peering setup and other ExpressRoute circuits must not be advertised to Microsoft through the BGP session. There's no restriction on the length of the NAT IP prefix advertised through this peering.
2828

2929
> [!IMPORTANT]
30-
> The NAT IP pool advertised to Microsoft must not be advertised to the Internet. This will break connectivity to other Microsoft services.
30+
> The NAT IP pool advertised to Microsoft must not be advertised to the Internet. This will break connectivity to other Microsoft services. We advise against a public IP address from the range assigned to primary or secondary link. Instead, you should use a different range of public IP addresses that has been assigned to you and registered in a Regional Internet Registry (RIR) or Internet Routing Registry (IRR). Depending on your call volume, this range can be as small as a single IP address (represented as '/32' for IPv4 or '/128' for IPv6).
3131
>
3232
3333
### Traffic originating from Microsoft destined to your network

0 commit comments

Comments
 (0)