Merge pull request #216534 from b-ahibbard/issue-100629

issue #100629

Author: prmerger-automator[bot]

articles/azure-netapp-files/use-availability-zones.md

@@ -12,10 +12,10 @@ ms.service: azure-netapp-files
 ms.workload: storage
 ms.tgt_pltfrm: na
 ms.topic: conceptual
-ms.date: 10/25/2022
+ms.date: 10/31/2022
 ms.author: anfdocs
 ---
-# Use availability zones for high availability in Azure NetApp Files
+# Use availability zones for high availability in Azure NetApp Files (preview)
 
 Azure [availability zones](../availability-zones/az-overview.md#availability-zones) are physically separate locations within each supporting Azure region that are tolerant to local failures. Failures can range from software and hardware failures to events such as earthquakes, floods, and fires. Tolerance to failures is achieved because of redundancy and logical isolation of Azure services. To ensure resiliency, a minimum of three separate availability zones are present in all [availability zone-enabled regions](../availability-zones/az-overview.md#azure-regions-with-availability-zones). 
 
@@ -41,6 +41,9 @@ You can co-locate your compute, storage, networking, and data resources across a
 
 Latency is subject to availability zone latency for within availability zone access and the regional latency envelope for cross-availability zone access.
 
+>[!IMPORTANT]
+>Availability zone volume placement in Azure NetApp Files is currently in preview. Refer to [Manage availability zone volume placement](manage-availability-zone-volume-placement.md#register-the-feature) for details on registering the feature. 
+
 ## Azure regions with availability zones
 
 For a list of regions that that currently support availability zones, refer to [Azure regions with availability zones](../availability-zones/az-overview.md#azure-regions-with-availability-zones).