Skip to content

Commit 742cfc3

Browse files
committed
created draft of new plsnat article.
1 parent bb0f61b commit 742cfc3

File tree

1 file changed

+49
-0
lines changed

1 file changed

+49
-0
lines changed
Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
---
2+
title: Enable SNAT Bypass for Private Endpoint Traffic through NVA
3+
description: Learn how to enable SNAT bypass for private endpoint traffic passing through a network virtual appliance (NVA) in Azure.
4+
author: abell
5+
ms.author: abell
6+
ms.service: azure-private-link
7+
ms.topic: how-to #Don't change
8+
ms.date: 02/05/2025
9+
10+
#customer intent: As a network administrator, I want to enable SNAT bypass for private endpoint traffic through NVA so that I can ensure symmetric routing and comply with internal logging standards.
11+
12+
---
13+
14+
# How to Guide: Enable SNAT Bypass for Private Endpoint Traffic through NVA
15+
16+
Source network address translation (SNAT) is no longer required for private endpoint destined traffic passing through a network virtual appliance (NVA). You can now configure a tag on your NVA VMs to notify the Microsoft platform that you wish to opt into this feature. This means SNATing will no longer be necessary for private endpoint destined traffic traversing through your NVA.
17+
18+
Enabling this feature provides a more streamlined experience for guaranteeing symmetric routing without impacting non-private endpoint traffic. It also allows you to follow internal compliance standards where the source of traffic origination needs to be available during logging. This feature is available in all regions.
19+
20+
21+
> [!NOTE]
22+
> Enabling SNAT bypass for private endpoint traffic through a Network Virtual Appliance (NVA) will cause a one-time reset of all long-running private endpoint connections established through the NVA. To minimize disruption, it is recommended to enable this feature during a maintenance window. This update will only impact traffic passing through your NVA; private endpoint traffic that bypasses the NVA will not be affected.
23+
24+
25+
## Prerequisites
26+
27+
* An active Azure account with a subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
28+
* A configured private endpoint in your subscription. For more information on how to create a private endpoint, see [Create a private endpoint](https://docs.microsoft.com/azure/private-link/create-private-endpoint).
29+
* A network virtual appliance (NVA) deployed in your subscription. For the example in this article, a virtual machine (VM) is used as the NVA. For more information on how to deploy a VM, see [Create a Windows virtual machine in the Azure portal](https://docs.microsoft.com/azure/virtual-machines/windows/quick-create-portal).
30+
31+
32+
### Enable SNAT Bypass for Private Endpoint Traffic through NVA
33+
34+
1. **Confirm the type of NVA you are using (VM or VMSS based).**
35+
36+
1. **Add Tag to your relevant resource:**
37+
- **VM Based:** Add the Resource Tag with a key of `disableSnatOnPL` and a value of `true` to the VM NIC.
38+
- **VMSS Based:** Add the Resource Tag with a key of `disableSnatOnPL` and a value of `true` to the VM instance.
39+
40+
1. **Validate Scenario.**
41+
42+
## Next Step
43+
44+
> [!div class="nextstepaction"]
45+
> [Create a private endpoint](https://docs.microsoft.com/azure/private-link/create-private-endpoint)
46+
47+
48+
49+

0 commit comments

Comments
 (0)