Merge pull request #308294 from MicrosoftDocs/main

[Publishing] [Out of Band Publish] azure-docs-pr - 11/13 @ 10:00AM

Author: Albertyang0

articles/azure-netapp-files/TOC.yml

@@ -387,6 +387,8 @@
         href: dynamic-change-volume-service-level.md
       - name: Manage default and individual user and group quotas for a volume
         href: manage-default-individual-user-group-quotas.md
+      - name: Generate user and group quota reports for a volume 
+        href: generate-user-group-quota-reports.md 
       - name: Manage storage with cool access 
         href: manage-cool-access.md
       - name: Manage file access logs 

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

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: overview
-ms.date: 10/14/2025
+ms.date: 10/28/2025
 ms.author: anfdocs
 # Customer intent: As a cloud architect, I want to evaluate Azure NetApp Files for high-performance file storage, so that I can efficiently manage enterprise workloads while ensuring data availability, scalability, and security in the cloud.
 ---
@@ -39,13 +39,14 @@ Azure NetApp Files is designed to provide high-performance file storage for ente
 | Functionality | Description | Benefit |
 | - | - | - | 
 | In-Azure bare-metal flash performance | Fast and reliable all-flash performance with submillisecond latency. | Run performance-intensive workloads in the cloud with on-premises infrastructure-level performance.
-| Multi-protocol support | Supports multiple protocols, including NFSv3, NFSv4.1, SMB 3.0, SMB 3.1.1, and simultaneous dual-protocol. Also supports integration with S3. | Seamlessly integrate with existing infrastructure and workflows without compatibility issues or complex configurations. Azure Netapp Files also integrates with S3 using the [object REST API](object-rest-api-introduction.md). |
+| Multi-protocol support | Supports multiple protocols, including NFSv3, NFSv4.1, SMB 3.0, SMB 3.1.1, and simultaneous dual-protocol. Also supports integration with S3. | Seamlessly integrate with existing infrastructure and workflows without compatibility issues or complex configurations. Azure NetApp Files also integrates with S3 using the [object REST API](object-rest-api-introduction.md). |
 | Four adaptable performance tiers (Flexible, Standard, Premium, Ultra) | Four performance tiers with dynamic service-level change capability based on workload needs, including cool access for cold data. | Choose the right performance level for workloads and dynamically adjust performance without overspending on resources.
 | Small-to-large volumes | Easily resize file volumes from 100 GiB up to 100 TiB without downtime. | Scale storage as business needs grow without over-provisioning, avoiding upfront cost.
 | Small-to-large volumes | Easily resize file volumes from 50 GiB up to 100 TiB without downtime. | Scale storage as business needs grow without over-provisioning, avoiding upfront cost.
 | 1-TiB minimum capacity pool size | 1-TiB capacity pool is a reduced-size storage pool compared to the initial 4-TiB minimum. | Save money by starting with a smaller storage footprint and lower entry point, without sacrificing performance or availability. Scale storage based on growth without high upfront costs.
 | 2,048-TiB maximum capacity pool | 2048-TiB capacity pool is an increased storage pool compared to the initial 500-TiB maximum. | Reduce waste by creating larger, pooled capacity and performance budget, and share and distribute across volumes.
 | 50-1,024 TiB large volumes | Store large volumes of data up to 1,024 TiB in a single volume. | Manage large datasets and high-performance workloads with ease.
+| 7.2 PiB large volumes with cool access | With cool access, extend the size of your large volumes to 7.2 PiB | Manage large datasets with infrequently accessed data with cost efficiency in mind. 
 | User and group quotas | Set quotas on storage usage for individual users and groups. | Control storage usage and optimize resource allocation.
 | Virtual machine (VM) networked storage performance | Higher VM network throughput compared to disk IO limits enable more demanding workloads on smaller Azure VMs. | Improve application performance at a smaller VM footprint, improving overall efficiency and lowering application license cost.
 | Deep workload readiness | Seamless deployment and migration of any-size workload with well-documented deployment guides. | Easily migrate any workload of any size to the platform. Enjoy a seamless, cost-effective deployment and migration experience.

articles/azure-netapp-files/azure-netapp-files-resource-limits.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: concept-article
-ms.date: 11/05/2025
+ms.date: 11/11/2025
 ms.author: anfdocs
 # Customer intent: As an IT administrator managing Azure NetApp Files, I want to understand the resource limits and how to request limit increases, so that I can effectively plan and allocate storage resources for my organization’s needs.
 ---
@@ -32,10 +32,11 @@ The following table describes resource limits for Azure NetApp Files:
 | Maximum throughput of a Flexible service level capacity pool | [5 x 128 MiB/second/TiB x Size of capacity pool in TiB](azure-netapp-files-set-up-capacity-pool.md#considerations) | No |
 |  Minimum size of a single regular volume    |    50 GiB    |    No    |
 |  Maximum size of a single regular volume     |    100 TiB    |    No    |
-|  Minimum size of a single [large volume](large-volumes-requirements-considerations.md) | 50 TiB |     No |
+|  Minimum size of a single [large volume](large-volumes-requirements-considerations.md) | 50 TiB | No |
 | Large volume size increase | 30% of lowest provisioned size | Yes |
-|  Maximum size of a single [large volume](large-volumes-requirements-considerations.md)    | 1,024 TiB |    Yes**    |
+|  Maximum size of a single [large volume](large-volumes-requirements-considerations.md) | 1 PiB | Yes** |
 | Maximum size of a single large volume with breakthrough mode (preview) | 2,400 TiB | No |
+| Maximum size of a large volume up to 7.2 PiB** | 7.2 PiB | Yes** |
 |  Maximum size of a single file     |    16 TiB    |    No    |    
 |  Maximum size of directory metadata in a single directory      |    320 MB    |    No    |    
 |  Maximum number of files in a single directory  | *Approximately* 4 million. <br> See [Determine if a directory is approaching the limit size](directory-sizes-concept.md#directory-limit).  |    No    |   
@@ -56,7 +57,9 @@ The following table describes resource limits for Azure NetApp Files:
 
 \* [!INCLUDE [Limitations for capacity pool minimum of 1 TiB](includes/2-tib-capacity-pool.md)]
 
-\** You can increase the size of your large volume with [breakthrough mode](large-volumes-requirements-considerations.md#requirements-and-considerations-for-breakthrough-mode-preview).
+\** Extended sizes for [large volumes](large-volumes-requirements-considerations.md) are available on request depending on regional dedicated capacity availability. To explore availability, contact your account team. 
+
+\*** This feature is available [when cool access is enabled and by request](large-volumes-requirements-considerations.md#requirements-and-considerations-for-large-volumes-up-to-72-pib-preview). When enabled, the minimum size of the volume is 2,400 GiB.
 
 For more information, see [Capacity management FAQs](faq-capacity-management.md).
 

articles/azure-netapp-files/azure-netapp-files-understand-storage-hierarchy.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: overview
-ms.date: 11/05/2025
+ms.date: 11/11/2025
 ms.author: anfdocs
 # Customer intent: "As a cloud architect, I want to understand the storage hierarchy of Azure NetApp Files, so that I can effectively set up and manage capacity pools and volumes to meet our storage needs."
 ---
@@ -80,7 +80,9 @@ When you use a manual QoS capacity pool with, for example, an SAP HANA system, a
 
 ## Large volumes
 
-Azure NetApp Files allows you to create [large volumes](large-volumes.md) up to 1 PiB in size. Large volumes begin at a capacity of 50 TiB and scale up to 1 PiB (or [2 PiB as special requests](large-volumes-requirements-considerations.md#requirements-and-considerations-for-breakthrough-mode-preview)). Regular Azure NetApp Files volumes are offered between 50 GiB and 102,400 GiB.
+Azure NetApp Files allows you to create [large volumes](large-volumes.md) up to 1 PiB. In contrast, regular Azure NetApp Files volumes are offered between 50 GiB and 102,400 GiB. 
+
+Large volumes begin at a capacity of 50 TiB and scale up to 1 PiB (or [2 PiB as special requests](large-volumes-requirements-considerations.md#requirements-and-considerations-for-breakthrough-mode-preview)). With cool access enabled, large volumes can grow to 7.2 PiB. 
 
 For more information, see [Requirements and considerations for large volumes](large-volumes-requirements-considerations.md).
 

articles/azure-netapp-files/configure-customer-managed-keys-hardware.md

@@ -7,7 +7,7 @@ ms.service: azure-netapp-files
 ms.workload: storage
 ms.topic: how-to
 ms.custom: references_regions
-ms.date: 05/20/2025
+ms.date: 11/12/2025
 ms.author: anfdocs
 # Customer intent: As a cloud storage administrator, I want to configure data encryption using customer-managed keys and a managed Hardware Security Module for Azure NetApp Files, so that I can ensure secure management of encryption keys in compliance with regulatory standards.
 ---
@@ -51,6 +51,7 @@ Azure NetApp Files volume encryption with customer-managed keys with the managed
 * Japan West
 * Korea Central
 * Korea South
+* New Zealand North
 * North Central US
 * North Europe
 * Norway East

articles/azure-netapp-files/double-encryption-at-rest.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: concept-article
-ms.date: 08/01/2025
+ms.date: 11/12/2025
 ms.author: anfdocs
 ms.custom: references_regions
 # Customer intent: "As a cloud administrator, I want to implement double encryption at rest for Azure NetApp Files, so that I can safeguard sensitive data from breaches and ensure compliance with security regulations."
@@ -50,6 +50,7 @@ Azure NetApp Files double encryption at rest is supported for the following regi
 * Japan East  
 * Korea Central 
 * Korea South 
+* New Zealand North
 * North Central US
 * North Europe 
 * Norway East 

articles/azure-netapp-files/generate-user-group-quota-reports.md

@@ -0,0 +1,110 @@
+---
+title: Generate user and group quota reports for Azure NetApp Files volumes 
+description: Learn how to generate user and group quota reports for Azure NetApp Files volumes.
+services: azure-netapp-files
+author: netapp-manishc
+ms.author: anfdocs
+ms.service: azure-netapp-files
+ms.topic: how-to
+ms.date: 11/11/2025
+# Customer intent: As a cloud storage administrator, I want to generate  user and group quota reports for Azure NetApp Files volumes.
+---
+# Generate user and group quota reports for a volume (preview)
+
+To help with capacity management on volumes shared among multiple users, individual user and group quotas restrict capacity usage on NFS, SMB, and dual-protocol volumes. 
+
+Quota reporting in Azure NetApp Files allows administrators to generate usage reports for an existing volume with quota rules, independent of host-based tooling and without having to mount the volume.
+
+For more information and considerations related to capacity management, see [Understand default and individual user and group quotas](default-individual-user-group-quotas-introduction.md).
+
+## Considerations 
+
+* Quota reporting is specific to the volume and its quota rules.
+* Quota reports are supported on regular and large volumes.
+* Quota reports are compiled on demand. They aren't persisted.
+* Entries in the quota report are sorted by percentage used in descending order.
+* The number of entries in the quota report is currently capped at 1,000 entries.
+* The number of entries in the quota report can be larger than the number of quota rules on the volume. Users that are subjected to default quota are reported as individual quota report entries.
+* When using quota reporting on data protection volumes:
+	* Quota report is unavailable for data protection volumes when the mirror state of the replication is in a mirrored state. You can run a quota report on the source volume instead.
+	* Quota reports become available when the replication relation is broken.
+* On volumes without a default user/group quota, users that aren't mapped to any rules and are accessing the volume will show 0 for total disk limit and percentage used in the quota report. In this instance, consider creating a default user/group quota rule.
+* When requesting quota reports for multiple volumes in the same subscription, these quota report requests are processed sequentially. When using the API, check responses (specifically percentComplete) for status. The quota report slide out in the Azure portal automatically retrieves the quota report in the background. Stay on the page until the quota report is successfully retrieved.
+* Quota reports take five seconds on average to generate.
+* If the quota report is an empty list or the quota report API calls fail on a volume with quota rules, retry generating the quota report after five minutes.
+* If quota rules aren't aligned with 4 KiB, the quota limit is incorrectly reported in the quota report. This happens because the field is always rounded up to the nearest multiple of 4 KiB to match disk space limits, which are translated into 4-KiB chunks. 
+
+## Register  the feature
+
+The feature must be registered on your subscription before using it for the first time. After confirmation by the product team, the feature is enabled on your subscription. 
+
+1. Register the feature:
+
+	```azurepowershell-interactive
+	Register-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFFetchQuotaReport
+	```
+
+2. Check the status of the feature registration: 
+
+	> [!NOTE]
+	> The **RegistrationState** can remain 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 ANFFetchQuotaReport
+	```
+
+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.
+
+## Generate a quota report for a volume
+
+1. From the Azure portal, select the volume for which you want to generate a quota report.
+2. Navigate to **User and group quotas**. Select the **Quota Report and Management** tab from the actions menu to generate the report. 
+
+	![Screenshot that shows the generate quota report and management option.](./media/manage-default-individual-user-group-quotas/generate-quota-reports.png) 
+
+	The quota report is retrieved in the background. Remain on the page  until the quota report has been successfully retrieved. Retrieval takes an average of five seconds, but can take longer. The quota report lists one entry per user. The following fields are available:
+
+	* **Quota Type**      
+
+		Indicates which type of quota rule caused this user or group entry in the report. Possible types are default or individual quotas for users or groups.
+
+	* **Derived Quota**
+
+		If a user or group is subject to an explicit quota rule, this field displays "No." Conversely, if a user or group is implicitly subject to a quota rule such as a default user or group quota rule, this field displays "Yes."
+
+	* **Quota Target**
+
+		UID/SID/GID for user/group
+
+	* **Quota Used**
+
+		Total disk limit used by the user/group
+
+	* **Quota Limit**
+
+		Total disk limit allocated by the user/group in kilobyte
+
+	* **% Used**
+	
+		Displays information with quota usage equal to or greater than the percentage used
+
+3. You can apply filters for **Quota Target**, **Quota Type**, and **% Used** to view a specific subset of the quota report.
+
+> [!IMPORTANT]
+> When using the quota target filter, you must first select a quota type value. The quota target is dependent on the quota type and can't be applied independently.
+
+> [!NOTE]
+> You can add a new quota only for derived quotas. You can only edit non-derived quotas.
+
+4. To edit a quota, select `…` at the end of the quota rule row, then select **Edit**.
+
+![Screenshot that shows the edit option for non-derived quotas.](./media/manage-default-individual-user-group-quotas/edit-report-quota.png) 
+
+5. To add a new quota for the default user and group quota, select `…` at the end of the quota rule row then **Add**.
+
+![Screenshot that shows the add option for derived quotas.](./media/manage-default-individual-user-group-quotas/add-derived-quota.png) 
+
+## Next steps
+
+* [Understand default and individual user and group quotas](default-individual-user-group-quotas-introduction.md)
+* [Manage default and individual user and group quotas for a volume](manage-default-individual-user-group-quotas.md)

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

@@ -2,7 +2,7 @@
 author: b-ahibbard
 ms.service: azure-netapp-files
 ms.topic: include
-ms.date: 11/05/2025
+ms.date: 11/11/2025
 ms.author: anfdocs
 ms.custom: include file
 
@@ -13,15 +13,20 @@ ms.custom: include file
 # Customer intent: As a cloud administrator, I want to understand the volume quota options for Azure NetApp Files, so that I can select the appropriate volume size and ensure compliance with regional capacity requirements.
 ---
 
-Regular volumes quotas are between 50 GiB and 100 TiB. Large volume quotas range from 50 TiB to 1 PiB in size. If you intend for the volume quota to fall in the large volume range, select **Yes**. Volume quotas are entered in GiB.
+Regular volumes quotas are between 50 GiB and 100 TiB. Large volume quotas range from 50 TiB to 1 PiB in size. To create a volume in this size range, select **Yes**. Volume quotas are entered in GiB.
 
 >[!IMPORTANT]
 > Before using large volumes, you must first [register the feature](../large-volumes-requirements-considerations.md#register-the-feature) and request [an increase in regional capacity quota](../azure-netapp-files-resource-limits.md#request-limit-increase).
 >
 >Regular volumes cannot be converted to large volumes. Large volumes can't be resized to less than 50 TiB. To understand the requirements and considerations of large volumes, see [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).
 
+* **Large volume type**
+
+    * To create a volume between 50 TiB and 1 PiB, select **Large volume**.
+    * If you plan to enable cool access and want to scale to 7.2 PiB, select **Extra-large volume 7.2 PiB**. Ensure you meet the [requirements for large volumes up to 7.2 PiB](../large-volumes-requirements-considerations.md#requirements-and-considerations-for-large-volumes-up-to-72-pib-preview).
+
 * **Breakthrough mode**
 
-    If you're using breakthrough mode to increase throughput, select the box.
+    If you're using breakthrough mode to increase throughput and quota, select the box.
 
-    You must first be registered to use breakthrough mode. For registration and other considerations, see [breakthrough mode](../large-volumes-requirements-considerations.md#register-for-breakthrough-mode).
+    You must first be registered to use breakthrough mode. For registration and other considerations, see [breakthrough mode](../large-volumes-requirements-considerations.md#register-for-breakthrough-mode).

articles/azure-netapp-files/includes/region-pairs.md

@@ -2,7 +2,7 @@
 author: b-ahibbard
 ms.service: azure-netapp-files
 ms.topic: include
-ms.date: 09/25/2025
+ms.date: 11/12/2025
 ms.author: anfdocs
 ms.custom: include file, references_regions
 
@@ -43,6 +43,7 @@ Azure NetApp Files volume replication is supported between various [Azure region
 | Geography | Regional Pair A | Regional Pair B  |
 |:--- |:--- |:--- |
 | Australia/Southeast Asia | Australia East | Southeast Asia |
+| New Zealand/Australia | New Zealand North | Australia East |
 | Israel/Sweden | Israel Central | Sweden Central | 
 | Qatar/Europe | Qatar Central | West Europe |
 | France/Europe | France Central | West Europe |