Skip to content

Commit 62de3fd

Browse files
committed
file path uniqueness GA
1 parent 529a456 commit 62de3fd

File tree

5 files changed

+10
-8
lines changed

5 files changed

+10
-8
lines changed

articles/azure-netapp-files/azure-netapp-files-create-volumes-smb.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: azure-netapp-files
55
author: b-hchen
66
ms.service: azure-netapp-files
77
ms.topic: how-to
8-
ms.date: 09/17/2024
8+
ms.date: 11/08/2024
99
ms.author: anfdocs
1010
---
1111
# Create an SMB volume for Azure NetApp Files
@@ -96,7 +96,7 @@ Before creating an SMB volume, you need to create an Active Directory connection
9696

9797
* Specify a unique **share name** for the volume. This share name is used when you create mount targets. The requirements for the share name are as follows:
9898
- For volumes not in an availability zone or volumes in the same availability zone, it must be unique within each subnet in the region.
99-
- For volumes in availability zones, it must be unique within each availability zone. This feature is currently in **preview** and requires you to register the feature. For more information, see [Manage availability zone volume placement](manage-availability-zone-volume-placement.md#file-path-uniqueness).
99+
- For volumes in availability zones, it must be unique within each availability zone. You must register the feature. For more information, see [Manage availability zone volume placement](manage-availability-zone-volume-placement.md#file-path-uniqueness).
100100
- It can contain only letters, numbers, or dashes (`-`).
101101
- The length must not exceed 80 characters.
102102

articles/azure-netapp-files/azure-netapp-files-create-volumes.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -112,7 +112,7 @@ This article shows you how to create an NFS volume. For SMB volumes, see [Create
112112

113113
* Specify a unique **file path** for the volume. This path is used when you create mount targets. The requirements for the path are as follows:
114114
- For volumes not in an availability zone or volumes in the same availability zone, it must be unique within each subnet in the region.
115-
- For volumes in availability zones, it must be unique within each availability zone. This feature is currently in **preview** and requires you to register the feature. For more information, see [Manage availability zone volume placement](manage-availability-zone-volume-placement.md#file-path-uniqueness).
115+
- For volumes in availability zones, it must be unique within each availability zone. You must register the feature. For more information, see [Manage availability zone volume placement](manage-availability-zone-volume-placement.md#file-path-uniqueness).
116116
- It must start with an alphabetical character.
117117
- It can contain only letters, numbers, or dashes (`-`).
118118
- The length must not exceed 80 characters.

articles/azure-netapp-files/create-volumes-dual-protocol.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: azure-netapp-files
55
author: b-hchen
66
ms.service: azure-netapp-files
77
ms.topic: how-to
8-
ms.date: 09/17/2024
8+
ms.date: 11/08/2024
99
ms.author: anfdocs
1010
---
1111
# Create a dual-protocol volume for Azure NetApp Files
@@ -130,7 +130,7 @@ To create NFS volumes, see [Create an NFS volume](azure-netapp-files-create-volu
130130
* Specify a unique **Volume Path**. This path is used when you create mount targets. The requirements for the path are as follows:
131131

132132
- For volumes not in an availability zone or volumes in the same availability zone, the volume path must be unique within each subnet in the region.
133-
- For volumes in availability zones, the volume path must be unique within each availability zone. This feature is currently in **preview** and requires you to register the feature. For more information, see [Manage availability zone volume placement](manage-availability-zone-volume-placement.md#file-path-uniqueness).
133+
- For volumes in availability zones, the volume path must be unique within each availability zone. You must register the feature. For more information, see [Manage availability zone volume placement](manage-availability-zone-volume-placement.md#file-path-uniqueness).
134134
- It must start with an alphabetical character.
135135
- It can contain only letters, numbers, or dashes (`-`).
136136
- The length must not exceed 80 characters.

articles/azure-netapp-files/manage-availability-zone-volume-placement.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ You can deploy new volumes in the logical availability zone of your choice. You
3030

3131
* VMs and Azure NetApp Files volumes are to be deployed separately, within the same logical availability zone to create zone alignment between VMs and Azure NetApp Files. The availability zone volume placement feature doesn't create zonal VMs upon volume creation, or vice versa.
3232

33-
* <a name="file-path-uniqueness"></a> For volumes in different availability zones, Azure NetApp Files allows you to create volumes with the same file path (NFS), share name (SMB), or volume path (dual-protocol). This feature is currently in preview.
33+
* <a name="file-path-uniqueness"></a> For volumes in different availability zones, Azure NetApp Files allows you to create volumes with the same file path (NFS), share name (SMB), or volume path (dual-protocol).
3434

3535
>[!IMPORTANT]
3636
>Once a volume is created with the same file path as another volume in a different availability zone, the volume has the same level of support as other volumes deployed in the subscription without this feature enabled. For example, if there's an issue with other generally available features on the volume such as snapshots, it's supported because the problem is unrelated to the ability to create volumes with the same file path in different availability zones.

articles/azure-netapp-files/whats-new.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,14 +6,16 @@ author: b-hchen
66
ms.service: azure-netapp-files
77
ms.custom: linux-related-content
88
ms.topic: overview
9-
ms.date: 10/24/2024
9+
ms.date: 11/08/2024
1010
ms.author: anfdocs
1111
---
1212

1313
# What's new in Azure NetApp Files
1414

1515
Azure NetApp Files is updated regularly. This article provides a summary about the latest new features and enhancements.
16-
16+
17+
* [Volume enhancement: creating volumes with the same file path, share name, or volume path in different availability zones](manage-availability-zone-volume-placement.md#file-path-uniqueness) is now generally available (GA)
18+
1719
## October 2024
1820

1921
* [Edit network features enhancement: no downtime](configure-network-features.md#no-downtime) (Preview)

0 commit comments

Comments
 (0)