large volumes GA update

Author: b-ahibbard

articles/azure-netapp-files/azure-government.md

@@ -26,7 +26,7 @@ All [Azure NetApp Files features](whats-new.md) available on Azure public cloud
 |:--- |:--- |:--- |
 | Azure NetApp Files backup | Generally available (GA) | No |
 | Azure NetApp Files customer-managed keys | Generally available (GA) | No | 
-| Azure NetApp Files large volumes | Public preview | Public preview [(select regions)](large-volumes-requirements-considerations.md#supported-regions) |
+| Azure NetApp Files large volumes | Generally available (GA) | Public preview [(select regions)](large-volumes-requirements-considerations.md#supported-regions) |
 
 ## Portal access
 

articles/azure-netapp-files/backup-restore-new-volume.md

@@ -24,7 +24,7 @@ Restoring a backup creates a new volume with the same protocol type. This articl
 
 * You should trigger the restore operation when there are no baseline backups. Otherwise, the restore might increase the load on the Azure Blob account where your data is backed up. 
 
-* For large volumes (greater than 10 TB), it can take multiple hours to transfer all the data from the backup media.
+* For volumes greater than 10 TiB, it can take multiple hours to transfer all the data from the backup media.
 
 * Restoring a backup to a new volume is not dependent on the networking type used by the source volume. You can restore the backup of a volume configured with Basic networking to a volume configured with Standard networking and vice versa.
 

articles/azure-netapp-files/cross-zone-replication-requirements-considerations.md

@@ -32,7 +32,7 @@ This article describes requirements and considerations about [using the volume c
 * You can delete manual snapshots on the source volume of a replication relationship when the replication relationship is active or broken, and also after you've deleted replication relationship. You cannot delete manual snapshots for the destination volume until you break the replication relationship.
 * When reverting a source volume with an active volume replication relationship, only snapshots that are more recent than the SnapMirror snapshot can be used in the revert operation. For more information, see [Revert a volume using snapshot revert with Azure NetApp Files](snapshots-revert-volume.md).
 * Data replication volumes support [customer-managed keys](configure-customer-managed-keys.md).
-* You can't currently use cross-zone replication with [large volumes](azure-netapp-files-understand-storage-hierarchy.md#large-volumes) (larger than 100 TiB).
+* You can't currently use cross-zone replication with [large volumes](azure-netapp-files-understand-storage-hierarchy.md#large-volumes).
 
 
 ## Next steps

articles/azure-netapp-files/includes/large-volumes-notice.md

@@ -12,6 +12,6 @@ ms.custom: include file
 ---
 
 >[!IMPORTANT]
-> Large volumes are currently in preview. If this is your first time using large volumes, you must first [register the feature](../azure-netapp-files-understand-storage-hierarchy.md#large-volumes) and request [an increase in regional capacity quota](../azure-netapp-files-resource-limits.md#request-limit-increase).
+> If this is your first time using large volumes, you must first [register the feature](../azure-netapp-files-understand-storage-hierarchy.md#large-volumes) and request [an increase in regional capacity quota](../azure-netapp-files-resource-limits.md#request-limit-increase).
 >
 >Volumes are considered large if they are between 50 TiB and 500 TiB in size. Regular volumes cannot be converted to large volumes. Large volumes cannot be resized to less than 50 TiB. To understand the requirements and considerations of large volumes, refer to for using [Requirements and considerations for large volumes](../large-volumes-requirements-considerations.md). For other limits, see [Resource limits](../azure-netapp-files-resource-limits.md#resource-limits).

articles/azure-netapp-files/large-volumes-requirements-considerations.md

@@ -9,14 +9,14 @@ ms.topic: conceptual
 ms.date: 11/02/2023
 ms.author: anfdocs
 ---
-# Requirements and considerations for large volumes (preview)
+# Requirements and considerations for large volumes
 
 This article describes the requirements and considerations you need to be aware of before using [large volumes](azure-netapp-files-understand-storage-hierarchy.md#large-volumes) on Azure NetApp Files.
 
 ## Register the feature 
 
-The large volumes feature for Azure NetApp Files is currently in public preview. This preview is offered under the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) and is controlled via Azure Feature Exposure Control (AFEC) settings on a per subscription basis. 
 
+<!-- TBD for GA -->
 To enroll in the preview for large volumes, use the [large volumes preview sign-up form](https://aka.ms/anflargevolumespreviewsignup).
 
 ## Requirements and considerations
@@ -30,8 +30,8 @@ The following requirements and considerations apply to large volumes. For perfor
     A large volume cannot be resized to less than 30% of its lowest provisioned size. This limit is adjustable via [a support request](azure-netapp-files-resource-limits.md#resource-limits).
 * Large volumes are currently not supported with Azure NetApp Files backup.
 * Large volumes aren't currently supported with cross-region replication.
-* You can't create a large volume with application volume groups.
 * Large volumes aren't currently supported with cross-zone replication.
+* You can't create a large volume with application volume groups.
 * Currently, large volumes aren't suited for database (HANA, Oracle, SQL Server, etc.) data and log volumes. For database workloads requiring more than a single volume’s throughput limit, consider deploying multiple regular volumes.
 * Throughput ceilings for the three performance tiers (Standard, Premium, and Ultra) of large volumes are based on the existing 100-TiB maximum capacity targets. You're able to grow to 500 TiB with the throughput ceiling per the following table:  
 

articles/azure-netapp-files/manage-default-individual-user-group-quotas.md

@@ -29,7 +29,7 @@ Quota rules only come into effect on the CRR/CZR destination volume after the re
 * In a CRR/CZR setting:
     * You can't create, update, or delete quota rules on the destination volume until you [delete the replication](cross-region-replication-delete.md).  
     * If a quota rule is in the error state after you delete the replication relationship, you need to delete and re-create the quota rule on the destination volume. 
-* If you're using [large volumes](large-volumes-requirements-considerations.md) (volumes larger than 100 TiB):    
+* If you're using [large volumes](large-volumes-requirements-considerations.md):    
     * The space and file usage in a large volume might exceed as much as five percent more than the configured hard limit before the quota limit is enforced and rejects traffic.   
     * To provide optimal performance, the space consumption may exceed configured hard limit before the quota is enforced. The additional space consumption won't exceed either the lower of 1 GB or five percent of the configured hard limit.    
     * After reaching the quota limit, if a user or administrator deletes files or directories to reduce quota usage under the limit, subsequent quota-consuming file operations may resume with a delay of up to five seconds.

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

@@ -16,6 +16,8 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
 
 ## May 2024
 
+* [Large volumes](large-volumes-requirements-considerations.md) are now generally available (GA).
+
 * [Support for one Active Directory connection per NetApp account](create-active-directory-connections.md#multi-ad) (Preview)
 
     The Azure NetApp Files support for one Active Directory (AD) connection per NetApp account feature now allows each NetApp account to connect to its own AD Forest and Domain, providing the ability to manage more than one AD connections within a single region under a subscription. This enhancement enables distinct AD connections for each NetApp account, facilitating operational isolation and specialized hosting scenarios. AD connections can be configured multiple times for multiple NetApp accounts to make use of it. With the creation of SMB volumes in Azure NetApp Files now tied to AD connections in the NetApp account, the management of AD environments becomes more scalable, streamlined and efficient. This feature is in preview.