Skip to content

Commit 55ec551

Browse files
committed
edit
1 parent 5d0150f commit 55ec551

File tree

4 files changed

+12
-12
lines changed

4 files changed

+12
-12
lines changed

articles/azure-netapp-files/TOC.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -439,8 +439,8 @@
439439
href: develop-rest-api-powershell.md
440440
- name: SDKs, CLI tools, and ARM templates
441441
href: azure-netapp-files-sdk-cli.md
442-
- name: Relocate to a another region
443-
href: ../operational-excellence/relocation-net-app.md?toc=/azure/azure-netapp-files/toc.json
442+
- name: Relocate to another region
443+
href: ../operational-excellence/relocation-netapp.md?toc=/azure/azure-netapp-files/toc.json
444444
- name: Troubleshoot
445445
items:
446446
- name: Troubleshoot using diagnose and solve problems tool

articles/operational-excellence/TOC.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -89,7 +89,7 @@
8989
- name: Azure IoT Hub
9090
href: ../iot-hub/iot-hub-how-to-clone.md?toc=/azure/operational-excellence/toc.json
9191
- name: Azure NetApp Files
92-
href: relocation-net-app.md
92+
href: relocation-netapp.md
9393
- name: Power BI
9494
href: /power-bi/admin/service-admin-region-move?toc=/azure/operational-excellence/toc.json
9595

articles/operational-excellence/overview-relocation.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -85,7 +85,7 @@ The following tables provide links to each Azure service relocation document. Th
8585
| --- | --- | --- | ---|
8686
[Azure Automation](./relocation-automation.md)| ✅ | ✅| ❌ |
8787
[Azure IoT Hub](/azure/iot-hub/iot-hub-how-to-clone?toc=/azure/operational-excellence/toc.json)| ✅ | ✅| ❌ |
88-
[Azure NetApps Files](./relocation-net-app.md)| ✅ | ✅| ❌ |
88+
[Azure NetApp Files](./relocation-netapp.md)| ✅ | ✅| ❌ |
8989
[Power BI](/power-bi/admin/service-admin-region-move?toc=/azure/operational-excellence/toc.json)| ✅ |❌ | ❌ |
9090

9191

articles/operational-excellence/relocation-net-app.md renamed to articles/operational-excellence/relocation-netapp.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Relocate Azure Net App Files to another region
3-
description: Learn how to relocate an Azure Net App Files to a another region
2+
title: Relocate AzureNetApp Files to another region
3+
description: Learn how to relocate an Azure NetApp Files to nother region
44
author: anaharris-ms
55
ms.author: anaharris
66
ms.reviewer: anaharris
@@ -11,9 +11,9 @@ ms.custom:
1111
- subject-relocation
1212
---
1313

14-
# Relocate Azure Net App Files to another region
14+
# Relocate Azure NetApp Files to another region
1515

16-
This article cover guidance for relocating [Azure Net App Files](../azure-netapp-files/azure-netapp-files-introduction.md) resources to another region.
16+
This article cover guidance for relocating [Azure NetApp Files](../azure-netapp-files/azure-netapp-files-introduction.md) resources to another region.
1717

1818
[!INCLUDE [relocate-reasons](./includes/service-relocation-reason-include.md)]
1919

@@ -24,7 +24,7 @@ Before you begin the relocation planning stage, first review the following prere
2424

2525
- The target NetApp account instance should already be created.
2626

27-
- Source and target regions must be paired regions. To see if they are paired, see [Supported cross-region replication pairs](../azure-netapp-files/cross-region-replication-introduction?#supported-region-pairs).
27+
- Source and target regions must be paired regions. To see if they are paired, see [Supported cross-region replication pairs](../azure-netapp-files/cross-region-replication-introduction.md?#supported-region-pairs).
2828

2929
- Understand all dependent resources. Some of the resources could be the following:
3030
- Azure Entra ID
@@ -50,13 +50,13 @@ Before you begin the relocation planning stage, first review the following prere
5050

5151
- Understand the following considerations in regards to replication:
5252

53-
- SMB volumes are supported along with NFS volumes. Replication of SMB volumes requires an Microsoft Entra ID connection in the source and target NetApp accounts.
53+
- SMB, NFS, and dual-protocol volumes are supported. Replication of SMB volumes requires an Microsoft Entra ID connection in the source and target NetApp accounts.
5454

5555
- The replication destination volume is read-only until the entire move is complete.
5656

5757
- Azure NetApp Files replication doesn't currently support multiple subscriptions. All replications must be performed under a single subscription.
5858

59-
- There can be resource limits for the maximum number of cross-region replication destination volumes. For more information, see [Resource limits for Azure NetApp Files](../azure-netapp-files/azure-netapp-files-resource-limits.md)
59+
- There are resource limits for the maximum number of cross-region replication destination volumes. For more information, see [Resource limits for Azure NetApp Files](../azure-netapp-files/azure-netapp-files-resource-limits.md)
6060

6161
## Redeploy
6262

@@ -75,7 +75,7 @@ Before you begin the relocation planning stage, first review the following prere
7575

7676
## Cleanup
7777

78-
Once the replication is complete, the replication peering, the source volume and replication can be deleted.
78+
Once the replication is complete, you can then safely delete the replication peering the source volume.
7979

8080
## Related content
8181

0 commit comments

Comments
 (0)