Merge pull request #263342 from b-ahibbard/file-path-uniqueness

update for unique file paths

Author: prmerger-automator[bot]

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

@@ -111,11 +111,11 @@ Before creating an SMB volume, you need to create an Active Directory connection
     * Select your **Active Directory** connection from the drop-down list.  
     
     * 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:   
-        - It must be unique within each subnet in the region. 
-        - It must start with an alphabetical character.
+        - For volumes not in an availability zone or volumes in the same availability zone, it must be unique within each subnet in the region.  
+        - 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).
         - It can contain only letters, numbers, or dashes (`-`). 
         - The length must not exceed 80 characters.   
-
+    
     * <a name="smb3-encryption"></a>If you want to enable encryption for SMB3, select **Enable SMB3 Protocol Encryption**.   
 
         This feature enables encryption for in-flight SMB3 data. SMB clients not using SMB3 encryption will not be able to access this volume.  Data at rest is encrypted regardless of this setting.   

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

@@ -106,7 +106,8 @@ This article shows you how to create an NFS volume. For SMB volumes, see [Create
     * Select **NFS** as the protocol type for the volume.   
 
     * 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:   
-        - It must be unique within each subnet in the region. 
+        - For volumes not in an availability zone or volumes in the same availability zone, it must be unique within each subnet in the region. 
+        - 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). 
         - It must start with an alphabetical character.
         - It can contain only letters, numbers, or dashes (`-`). 
         - The length must not exceed 80 characters.

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

@@ -138,18 +138,19 @@ You can also use [Azure CLI commands](/cli/azure/feature) `az feature register`
 
         ![Show advanced selection](./media/shared/volume-create-advanced-selection.png)
 
-3. Click the **Protocol** tab, and then complete the following actions:  
+3. Select the **Protocol** tab, and then complete the following actions:  
     * Select **Dual-protocol** as the protocol type for the volume.   
 
     * Specify the **Active Directory** connection to use.
 
     * Specify a unique **Volume Path**. This path is used when you create mount targets. The requirements for the path are as follows:  
 
-        - It must be unique within each subnet in the region. 
+        - 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. 
+        - 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).
         - It must start with an alphabetical character.
         - It can contain only letters, numbers, or dashes (`-`). 
         - The length must not exceed 80 characters.
-
+    
     * Specify the **versions** to use for dual protocol: **NFSv4.1 and SMB**, or **NFSv3 and SMB**.
 
     * Specify the **Security Style** to use: NTFS (default) or UNIX.

articles/azure-netapp-files/faq-nfs.md

@@ -36,9 +36,19 @@ To avoid any issues with clients mounting NFSv4.2 and to comply with supportabil
 
 You can specify whether the root account can access the volume or not by using the volume’s export policy. See [Configure export policy for an NFS volume](azure-netapp-files-configure-export-policy.md) for details.
 
-## Can I use the same file path (volume creation token) for multiple volumes?
+## Can I use the same file path for multiple volumes?
 
-Yes, you can. However, the file path must be unique within each subnet.     
+The same file path can be used for:
+* volumes deployed in different regions
+* volumes deployed to different availability zones within the same region
+
+If you are using:
+* regional volumes (without availability zones) or
+* volumes within the same availability zone,
+
+the same file path can be used, however the file path must be unique within each delegated subnet or assigned to different delegated subnets. 
+
+For more information, see [Create an NFS volume for Azure NetApp Files](azure-netapp-files-create-volumes.md) or [Create a dual-protocol volume for Azure NetApp Files](create-volumes-dual-protocol.md). 
 
 ## When I try to access NFS volumes through a Windows client, why does the client take a long time to search folders and subfolders?
 

articles/azure-netapp-files/faq-smb.md

@@ -79,6 +79,20 @@ See [Modify SMB share permissions](azure-netapp-files-create-volumes-smb.md#modi
 
 Azure NetApp Files also supports [access-based enumeration](azure-netapp-files-create-volumes-smb.md#access-based-enumeration) and [non-browsable shares](azure-netapp-files-create-volumes-smb.md#non-browsable-share) on SMB and dual-protocol volumes. You can enable these features during or after the creation of an SMB or dual-protocol volume.
 
+## Can I use the same share name for multiple volumes? 
+
+The same share name can be used for:
+* volumes deployed in different regions
+* volumes deployed to different availability zones within the same region 
+
+If you are using:
+* regional volumes (without availability zones) or
+* volumes within the same availability zone, 
+
+the same share name can be used, however the share name must be unique within each delegated subnet or assigned to different delegated subnets. 
+
+For more information, see [Create an SMB volume for Azure NetApp Files](azure-netapp-files-create-volumes-smb.md) or [Create a dual-protocol volume for Azure NetApp Files](create-volumes-dual-protocol.md). 
+
 ## Can I change the SMB share name after the SMB volume has been created?
 
 No. However, you can create a new SMB volume with the new share name from a snapshot of the SMB volume with the old share name.   

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

@@ -30,6 +30,27 @@ You can deploy new volumes in the logical availability zone of your choice. You
 
 * 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.
 
+* <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. 
+
+    You need to register the feature before using it for the first time. After registration, the feature is enabled and works in the background. No UI control is required.
+    
+    1. Register the feature: 
+    
+        ```azurepowershell-interactive
+        Register-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFFilePathUniquenessInAz
+        ```
+    
+    2. Check the status of the feature registration: 
+    
+        > [!NOTE]
+        > The **RegistrationState** may be in the `Registering` state for up to 60 minutes before changing to`Registered`. Wait until the status is **Registered** before continuing.
+    
+        ```azurepowershell-interactive
+        Get-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFFilePathUniquenessInAz
+        ```
+    You can also use [Azure CLI commands](/cli/azure/feature) `az feature register` and `az feature show` to register the feature and display the registration status. 
+
+
 [!INCLUDE [Availability Zone volumes have the same level of support as other volumes in the subscription](includes/availability-zone-service-callout.md)]
 
 >[!IMPORTANT]

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

@@ -14,6 +14,12 @@ ms.author: anfdocs
 
 Azure NetApp Files is updated regularly. This article provides a summary about the latest new features and enhancements.
 
+## March 2024
+
+* [Volume enhancement: create volumes with the same file path, share name, or volume path in different availability zones](manage-availability-zone-volume-placement.md#file-path-uniqueness) (Preview)
+
+    Azure NetApp Files now allows you to create volumes with the same file path (NFS), share name (SMB), or volume path (dual-protocol) as long as they are in different availability zones. For more information, see [Create an NFS volume for Azure NetApp Files](azure-netapp-files-create-volumes.md), [Create an SMB volume for Azure NetApp Files](azure-netapp-files-create-volumes-smb.md), or [Create a dual-protocol volume for Azure NetApp Files](create-volumes-dual-protocol.md). This enhancement is currently in preview. 
+    
 ## February 2024
 
 * [Volume and protocol enhancement](understand-volume-languages.md): extended language support for file and path names