remove afec

Author: b-ahibbard

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

@@ -96,7 +96,7 @@ Before creating an SMB volume, you need to create an Active Directory connection
 
     * 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:   
         - 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. You must register the feature. For more information, see [Manage availability zone volume placement](manage-availability-zone-volume-placement.md#file-path-uniqueness).
+        - For volumes in availability zones, it must be unique within each availability zone. 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.   
 

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

@@ -112,7 +112,7 @@ This article shows you how to create an NFS volume. For SMB volumes, see [Create
 
     * 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:   
         - 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. You must register the feature. For more information, see [Manage availability zone volume placement](manage-availability-zone-volume-placement.md#file-path-uniqueness). 
+        - For volumes in availability zones, it must be unique within each availability zone. 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

@@ -130,7 +130,7 @@ To create NFS volumes, see [Create an NFS volume](azure-netapp-files-create-volu
     * Specify a unique **Volume Path**. This path is used when you create mount targets. The requirements for the path are as follows:  
 
         - 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. You must register the feature. For more information, see [Manage availability zone volume placement](manage-availability-zone-volume-placement.md#file-path-uniqueness).
+        - For volumes in availability zones, the volume path must be unique within each availability zone. 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/manage-availability-zone-volume-placement.md

@@ -31,28 +31,7 @@ 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). 
-
-    >[!IMPORTANT]
-    >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.
-
-    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. 
-
+ 
 >[!IMPORTANT]
 >It's not recommended that you use availability zones for Terraform-managed volumes. If you do, you must [add the zone property to your volume](#populate-availability-zone-for-terraform-managed-volumes).