You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/nat-gateway/region-move-nat-gateway.md
+11-9Lines changed: 11 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,17 +1,19 @@
1
1
---
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.
4
5
author: asudbring
5
6
ms.author: allensu
6
7
ms.service: nat-gateway
7
8
ms.topic: how-to
8
-
ms.date: 01/04/2022
9
+
ms.date: 01/22/2024
9
10
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.
10
12
---
11
13
12
14
# Create and configure NAT gateway after moving resources to another region
13
15
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.
15
17
16
18
> [!NOTE]
17
19
> 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
26
28
27
29
## Create a new NAT gateway
28
30
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.
30
32
31
33
1. In the search box at the top of the portal, enter **NAT gateway**. Select **NAT gateways**.
32
34
@@ -38,9 +40,9 @@ After you have moved all the resources associated with the original instance of
38
40
| ------- | ----- |
39
41
|**Project details**||
40
42
| 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. |
42
44
|**Instance details**||
43
-
| Name | Enter **myNATgateway**. |
45
+
| Name | Enter **nat-gateway**. |
44
46
| Region | Select the name of the new region. |
45
47
| Availability Zone | Select **None**. Instead, you can select the zone of the moved resources if applicable. |
46
48
| Idle timeout (minutes) | Enter **10**. |
@@ -51,7 +53,7 @@ After you have moved all the resources associated with the original instance of
51
53
52
54
| Setting | Value |
53
55
| ------- | ----- |
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. |
55
57
56
58
6. Select the **Subnet** tab, or select **Next: Subnet** at the bottom of the page.
57
59
@@ -69,7 +71,7 @@ For steps on how to test the NAT gateway, see [Quickstart: Create a NAT gateway
69
71
70
72
## Delete old instance of NAT gateway
71
73
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.
0 commit comments