Merge pull request #308778 from netapp-manishc/patch-69

Update cache volume configuration details

Author: prmerger-automator[bot]

articles/azure-netapp-files/configure-cache-volumes.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: netapp-manishc
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 11/10/2025
+ms.date: 11/26/2025
 ms.author: anfdocs
 ms.custom: sfi-image-nochange
 # Customer intent: As a cloud administrator, I want to create a cache volume in Azure NetApp Files, so that I can leverage scalable storage solutions and reduce cost.
@@ -25,6 +25,8 @@ Write-back allows the write to be committed to stable storage at the cache and a
 * When creating a cache volume, ensure that there's sufficient space in the capacity pool to accommodate the new cache volume.
 * You should ensure that the protocol type is the same for the cache volume and origin volume. The security style and the Unix permissions are inherited from the origin volume. For example, creating a cache volume with NFSv3 or NFSv4 when origin is UNIX, and SMB when the origin is NTFS.
 * You should enable encryption on the origin volume.
+* The source cluster must be running ONTAP 9.15.1 or later version.
+* The minimum supported ONTAP version without write-back is 9.12.1 or later version.
 * You should configure an Active Directory (AD) or LDAP connection within the NetApp account to create an LDAP-enabled cache volume.
 * You can't move a cache volume to another capacity pool.
 * The `globalFileLocking` parameter value must be the same on all cache volumes that share the same origin volume. Global file locking can be enabled when creating the first cache volume by setting `globalFileLocking` to true. The subsequent cache volumes from the same origin volume must have this setting set to true. To change the global file locking setting on existing cache volumes, you must update the origin volume first. After updating the origin volume, the change propagates to all the cache volumes associated with that origin volume. The `volume flexcache origin config modify -is-global-file-locking-enabled` command should be executed on the source cluster to change the setting on the origin volume.