Skip to content

Commit 14a5d63

Browse files
Merge pull request #225695 from halkazwini/vpn-nat
Tweak
2 parents d544e07 + 86ca6c2 commit 14a5d63

File tree

2 files changed

+8
-8
lines changed

2 files changed

+8
-8
lines changed

articles/vpn-gateway/nat-overview.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,10 +4,10 @@ titleSuffix: Azure VPN Gateway
44
description: Learn about NAT (Network Address Translation) in Azure VPN to connect networks with overlapping address spaces.
55
author: cherylmc
66
ms.service: vpn-gateway
7-
ms.topic: article
7+
ms.topic: conceptual
88
ms.date: 05/11/2022
99
ms.author: cherylmc
10-
10+
ms.custom: template-concept
1111
---
1212
# About NAT on Azure VPN Gateway
1313

@@ -52,9 +52,9 @@ Each NAT rule defines an address mapping or translating relationship for the cor
5252

5353
For each NAT rule, the following two fields specify the address spaces before and after the translation:
5454

55-
* **Internal Mappings**: This is the address space **before** the translation. For an ingress rule, this field corresponds to the original address space of the on-premises network. For an egress rule, this is the original VNet address space.
55+
* **Internal Mappings**: The address space **before** the translation. For an ingress rule, this field corresponds to the original address space of the on-premises network. For an egress rule, this is the original VNet address space.
5656

57-
* **External Mappings**: This is the address space **after** the translation for on-premises networks (ingress) or VNet (egress). For different networks connected to an Azure VPN gateway, the address spaces for all **External Mappings** must not overlap with each other and with the networks connected without NAT.
57+
* **External Mappings**: The address space **after** the translation for on-premises networks (ingress) or VNet (egress). For different networks connected to an Azure VPN gateway, the address spaces for all **External Mappings** must not overlap with each other and with the networks connected without NAT.
5858

5959
## <a name="routing"></a>NAT and routing
6060

includes/vpn-gateway-faq-nat-include.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ You can create up to 100 NAT rules (Ingress and Egress rules combined) on a VPN
1919

2020
### Can I use / in a NAT rule name?
2121

22-
No. You will receive an error.
22+
No. You'll receive an error.
2323

2424
### Is NAT applied to all connections on a VPN gateway?
2525

@@ -70,7 +70,7 @@ You can use any suitable IP range that you want for External Mapping, including
7070

7171
### Can I use different EgressSNAT rules to translate my VNet address space to different prefixes to different on-premises networks?
7272

73-
Yes, you can create multiple EgressSNAT rules for the same VNet address space, and apply the EgressSNAT rules to different connections. For the connections without an EgressSNAT rule,
73+
Yes, you can create multiple EgressSNAT rules for the same VNet address space, and apply the EgressSNAT rules to different connections.
7474

7575
### Can I use the same IngressSNAT rule on different connections?
7676

@@ -80,6 +80,6 @@ Yes, this is typically used when the connections are for the same on-premises ne
8080

8181
You need both Ingress and Egress rules on the same connection when the on-premises network address space overlaps with the VNet address space. If the VNet address space is unique among all connected networks, you don't need the EgressSNAT rule on those connections. You can use the Ingress rules to avoid address overlap among the on-premises networks.
8282

83-
### What do I choose as "IP configuration ID" ?
83+
### What do I choose as "IP configuration ID"?
8484

85-
"IP configuration ID" is simply the name of the IP configuration object you want the NAT rule to use. With this setting, you are simply choosing which gateway public IP address applies to the NAT rule. If you haven't specified any custom name at gateway creation time, the gateway's primary IP address is assigned to the "default" IPconfiguration and the secondary IP is assigned to the "activeActive" IPconfiguration.
85+
"IP configuration ID" is simply the name of the IP configuration object you want the NAT rule to use. With this setting, you're simply choosing which gateway public IP address applies to the NAT rule. If you haven't specified any custom name at gateway creation time, the gateway's primary IP address is assigned to the "default" IPconfiguration, and the secondary IP is assigned to the "activeActive" IPconfiguration.

0 commit comments

Comments
 (0)