Skip to content

Commit 220a8cb

Browse files
Merge pull request #263928 from asudbring/nat-freshness
Freshness review and update for region move article for Azure NAT gateway
2 parents 8c76572 + af7861f commit 220a8cb

File tree

1 file changed

+11
-9
lines changed

1 file changed

+11
-9
lines changed

articles/nat-gateway/region-move-nat-gateway.md

Lines changed: 11 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,19 @@
11
---
2-
title: Create and configure NAT gateway after moving resources to another region
3-
description: Learn how to configure a new NAT gateway for resources moved to another region.
2+
title: Deploy a NAT gateway after moving resources between regions
3+
titleSuffix: Azure NAT gateway
4+
description: Get started learning how to deploy and configure a new Azure NAT Gateway for resources moved to another region.
45
author: asudbring
56
ms.author: allensu
67
ms.service: nat-gateway
78
ms.topic: how-to
8-
ms.date: 01/04/2022
9+
ms.date: 01/22/2024
910
ms.custom: template-how-to
11+
# Customer intent: As a network administrator, I want to create and configure a Azure NAT Gateway after moving resources to another region.
1012
---
1113

1214
# Create and configure NAT gateway after moving resources to another region
1315

14-
In this article, learn how to configure a NAT gateway after moving resources to a different region. You might want to move resources to take advantage of a new Azure region that is better suited to your customers' geographical presence, other needs, or to meet internal policy and governance requirements, or to take advantage of your organization’s infrastructure.
16+
In this article, you'll learn how to set up a NAT gateway after moving resources to a different region. You might want to move resources to a new Azure region that better suits your customers' location or meets your organization's needs and policies.
1517

1618
> [!NOTE]
1719
> NAT gateway instances can't directly be moved from one region to another. A workaround is to use Azure Resource Mover to move all the resources associated with the existing NAT gateway to the new region. You then create a new instance of NAT gateway in the new region and then associate the moved resources with the new instance. After the new NAT gateway is functional in the new region, you delete the old instance in the previous region.
@@ -26,7 +28,7 @@ In this article, learn how to configure a NAT gateway after moving resources to
2628

2729
## Create a new NAT gateway
2830

29-
After you have moved all the resources associated with the original instance of NAT gateway to the new region and verified them, the following steps will enable you to create a new instance of NAT gateway. This new NAT gateway can then be associated with the moved resources.
31+
After you move all the resources associated with the original NAT gateway instance to the new region and verify them, you can create a new NAT gateway instance. Then, you can associate the moved resources with the new NAT gateway.
3032

3133
1. In the search box at the top of the portal, enter **NAT gateway**. Select **NAT gateways**.
3234

@@ -38,9 +40,9 @@ After you have moved all the resources associated with the original instance of
3840
| ------- | ----- |
3941
| **Project details** | |
4042
| Subscription | Select your subscription. |
41-
| Resource group | Select **Create new**. </br> Enter **myResourceGroup** in **Name**. </br> Select **OK**. </br> Instead, you can select the existing resource group associated with the moved resources in the subscription. |
43+
| Resource group | Select **Create new**. </br> Enter **test-rg** in **Name**. </br> Select **OK**. </br> Instead, you can select the existing resource group associated with the moved resources in the subscription. |
4244
| **Instance details** | |
43-
| Name | Enter **myNATgateway**. |
45+
| Name | Enter **nat-gateway**. |
4446
| Region | Select the name of the new region. |
4547
| Availability Zone | Select **None**. Instead, you can select the zone of the moved resources if applicable. |
4648
| Idle timeout (minutes) | Enter **10**. |
@@ -51,7 +53,7 @@ After you have moved all the resources associated with the original instance of
5153

5254
| Setting | Value |
5355
| ------- | ----- |
54-
| Public IP addresses | Select **Create a new public IP address**. </br> Enter **myNATPublicIP** in **Name**. </br> Select **OK**. </br> Instead, you can select an existing public IP in your subscription if applicable. |
56+
| Public IP addresses | Select **Create a new public IP address**. </br> Enter **public-ip-nat** in **Name**. </br> Select **OK**. </br> Instead, you can select an existing public IP in your subscription if applicable. |
5557

5658
6. Select the **Subnet** tab, or select **Next: Subnet** at the bottom of the page.
5759

@@ -69,7 +71,7 @@ For steps on how to test the NAT gateway, see [Quickstart: Create a NAT gateway
6971

7072
## Delete old instance of NAT gateway
7173

72-
After you have created new NAT gateway and have tested it, you can delete the source resources from the old region. This step will automatically delete the original NAT gateway.
74+
After you create the new NAT gateway and test the deployment, you can delete the source resources from the old region including the old NAT gateway instance.
7375

7476
## Next steps
7577

0 commit comments

Comments
 (0)