Skip to content

Commit 13da9a4

Browse files
Migrate tutorial to StandardV2 NAT Gateway
Updated tutorial to use StandardV2 NAT Gateway for outbound connectivity and clarified SKU requirements.
1 parent f5d245a commit 13da9a4

1 file changed

Lines changed: 8 additions & 3 deletions

File tree

articles/nat-gateway/tutorial-migrate-outbound-nat.md

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,12 @@ You learn how to change your outbound connectivity from load balancer outbound r
2121

2222
Azure NAT Gateway is the recommended method for outbound connectivity. A NAT gateway is a fully managed and highly resilient Network Address Translation (NAT) service. A NAT gateway doesn't have the same limitations of Source Network Address Translation (SNAT) port exhaustion as default outbound access. A NAT gateway replaces the need for outbound rules in a load balancer for outbound connectivity.
2323

24+
> [!NOTE]
25+
> For default outbound access replacement, StandardV2 NAT Gateway is deployed in the tutorial to ensure that you are using the zone-redundant version of NAT gateway (Standard SKU NAT Gateway is zonal). See [StandardV2 NAT Gateway](/azure/nat-gateway/nat-overview#standardv2-nat-gateway) for more details and see [known limitations](/azure/nat-gateway/nat-overview#key-limitations-of-standardv2-nat-gateway) for details on unsupported scenarios.
26+
27+
> [!NOTE]
28+
> For the Load balancer outbound rule replacement, Standard SKU NAT Gateway is deployed in this tutorial and the frontend IP of the Load balancer is moved to the Standard NAT Gateway. StandardV2 NAT Gateway can be used to replace Load balancer outbound rules but can't be used with the Load balancer frontend IP. StandardV2 NAT Gateway requires new creation of a StandardV2 SKU public IP.
29+
2430
For more information about Azure NAT Gateway, see [What is Azure NAT Gateway?](nat-overview.md)
2531

2632
In this tutorial, you learn how to:
@@ -79,8 +85,7 @@ In this section, you learn how to change your outbound connectivity method from
7985
| Region | Select a region. This example uses **East US 2**. |
8086
| Name | Enter **public-ip-nat**. |
8187
| IP version | Select **IPv4**. |
82-
| SKU | Select **Standard**. |
83-
| Availability zone | Select **Zone-redundant**. |
88+
| SKU | Select **StandardV2**. |
8489
| Tier | Select **Regional**. |
8590

8691
1. Select **Review + create** and then select **Create**.
@@ -99,7 +104,7 @@ In this section, you learn how to change your outbound connectivity method from
99104
| **Instance details** | |
100105
| NAT gateway name | Enter **nat-gateway**. |
101106
| Region | Select your region. This example uses **East US 2**. |
102-
| SKU | Select **Standard**. |
107+
| SKU | Select **StandardV2**. |
103108
| TCP idle timeout (minutes) | Leave the default of **4**. |
104109

105110
1. Select **Next**.

0 commit comments

Comments
 (0)