Merge pull request #311077 from MicrosoftDocs/main

Auto Publish – main to live - 2026-01-29 18:00 UTC

Author: learn-build-service-prod[bot]

articles/azure-netapp-files/.openpublishing.redirection.azure-netapp-files.json

@@ -79,6 +79,11 @@
             "source_path_from_root":"/articles/azure-netapp-files/snapshots-edit-hide-path.md",
             "redirect_url": "/azure/azure-netapp-files/snapshots-manage-policy#edit-the-hide-snapshot-path-option",
             "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-netapp-files/elastic-resource-limits.md",
+            "redirect_url": "/azure/azure-netapp-files/azure-netapp-files-resource-limits",
+            "redirect_document_id": false
         }
     ]
 }

articles/azure-netapp-files/TOC.yml

@@ -27,6 +27,7 @@ All [Azure NetApp Files features](whats-new.md) available on Azure public cloud
 |:--- |:--- |:--- |
 | Advanced ransomware protection | Preview | No |
 | Customer-managed keys with managed Hardware Security Module | Generally available | No |
+| Elastic zone-redundant storage | Preview | No |
 | File access logs | Generally available | [Partial support](manage-file-access-logs.md#supported-regions) |
 
 ## Portal access

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

@@ -15,6 +15,8 @@ Understanding the cost model for Azure NetApp Files helps you manage your expens
 
 For cost model specific to cross-region replication, see [Cost model for cross-region replication](replication.md#cost-model-for-cross-region-replication).
 
+<!-- ZRS update -->
+
 ## Calculation of capacity consumption
 
 Azure NetApp Files is billed on provisioned storage capacity, which is allocated by creating capacity pools. Capacity pools are billed monthly based on a set cost per allocated GiB per hour. Capacity pool allocation is measured hourly.  
@@ -76,6 +78,8 @@ In this case, when costs are billed at $0.000202 per GiB/hour (Standard), $0.000
 
 This scenario constitutes a monthly savings of $3,965.39 compared to static provisioning.
 
+#### Example 3: Elastic zone-redundant storage
+
 ## Capacity consumption of snapshots 
 
 The capacity consumption of snapshots in Azure NetApp Files is charged against the quota of the parent volume.  As a result, it shares the same billing rate as the capacity pool to which the volume belongs.  However, unlike the active volume, snapshot consumption is measured based on the incremental capacity consumed.  Azure NetApp Files snapshots are differential in nature. Depending on the change rate of the data, the snapshots often consume much less capacity than the logical capacity of the active volume. For example, assume that you have a snapshot of a 500-GiB volume that only contains 10 GiB of differential data. 

articles/azure-netapp-files/azure-netapp-files-cost-model.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 02/04/2025
+ms.date: 06/25/2025
 ms.author: anfdocs
 # Customer intent: As an IT administrator, I want to create a NetApp account in Azure NetApp Files, so that I can set up a capacity pool and manage storage volumes effectively.
 ---
@@ -16,11 +16,12 @@ Creating a NetApp account enables you to set up a capacity pool so that you can
 
 ## Before you begin
 
-You must register your subscription for using the NetApp Resource Provider. For more information, see [Register the NetApp Resource Provider](azure-netapp-files-register.md).
+* You must register your subscription for using the NetApp Resource Provider. For more information, see [Register the NetApp Resource Provider](azure-netapp-files-register.md).
+* There are two types of NetApp accounts. If you plan to use Elastic zone-redundant storage, you must use a [NetApp Elastic account](elastic-zone-redundant-concept.md).
 
 ## Steps
 
-1. Log into the Azure portal.
+1. Log in to the Azure portal.
 1. Access the Azure NetApp Files pane by using one of the following methods:
    * Search for **Azure NetApp Files** in the Azure portal search box.
    * Select **All services** in the navigation, and then filter to Azure NetApp Files.
@@ -35,6 +36,7 @@ You must register your subscription for using the NetApp Resource Provider. For
    * **Subscription**: Select a subscription from your existing subscriptions.
    * **Resource group**: Use an existing resource group or create a new one.
    * **Location**: Select the region where you want the account and its child resources to be located.
+   * **Service tier**: For standard Azure NetApp Files storage, select **Other**. For zone-redundant, select **Zone redundant**. 
 
      ![Screenshot that shows New NetApp account.](./media/azure-netapp-files-create-netapp-account/azure-netapp-files-new-netapp-account.png)
 

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

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 06/11/2025
+ms.date: 11/12/2025
 ms.author: anfdocs
 ms.custom: sfi-image-nochange
 # Customer intent: As a cloud administrator, I want to create an SMB volume in Azure NetApp Files, so that I can leverage scalable storage solutions that meet my organization’s data management and sharing requirements.
@@ -14,7 +14,10 @@ ms.custom: sfi-image-nochange
 
 Azure NetApp Files supports creating volumes using NFS (NFSv3 or NFSv4.1), SMB3, or dual protocol (NFSv3 and SMB, or NFSv4.1 and SMB). A volume's capacity consumption counts against its pool's provisioned capacity. 
 
-This article shows you how to create an SMB3 volume. For NFS volumes, see [Create an NFS volume](azure-netapp-files-create-volumes.md). For dual-protocol volumes, see [Create a dual-protocol volume](create-volumes-dual-protocol.md).
+This article shows you how to create an SMB3 volume. For NFS volumes, see [Create an NFS volume](azure-netapp-files-create-volumes.md). For dual-protocol volumes, see [Create a dual-protocol volume](create-volumes-dual-protocol.md). 
+
+>[!IMPORTANT]
+>For Elastic zone-redundant storage, see [Create an Elastic zone-redundant SMB volume](elastic-volume-server-message-block.md).
 
 ## Before you begin 
 

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

@@ -15,6 +15,9 @@ Azure NetApp Files supports creating volumes using NFS (NFSv3 or NFSv4.1), SMB3,
 
 This article shows you how to create an NFS volume. For SMB volumes, see [Create an SMB volume](azure-netapp-files-create-volumes-smb.md). For dual-protocol volumes, see [Create a dual-protocol volume](create-volumes-dual-protocol.md).
 
+>[!IMPORTANT]
+>For Elastic zone-redundant storage, see [Create an Elastic zone-redundant NFS volume](elastic-volume.md).
+
 ## Before you begin 
 
 [!INCLUDE [Delegated subnet permission](includes/create-volume-permission.md)]
@@ -83,13 +86,13 @@ This article shows you how to create an NFS volume. For SMB volumes, see [Create
     * **Virtual network**  
         Specify the Microsoft Azure Virtual Network from which you want to access the volume.  
 
-        The Virtual Network you specify must have a subnet delegated to Azure NetApp Files. The Azure NetApp Files service can be accessed only from the same Virtual Network or from a virtual network that's in the same region as the volume through virtual network peering. You can also access the volume from your on-premises network through Express Route.   
+        The Virtual Network you specify must have a subnet delegated to Azure NetApp Files. The Azure NetApp Files service can be accessed only from the same Virtual Network or from a virtual network that's in the same region as the volume through virtual network peering. You can also access the volume from your on-premises network through Express Route.  
 
     * **Subnet**  
         Specify the subnet that you want to use for the volume.  
         The subnet you specify must be delegated to Azure NetApp Files. 
         
-        If you have not delegated a subnet, you can click **Create new** on the Create a Volume page. Then in the Create Subnet page, specify the subnet information, and select **Microsoft.NetApp/volumes** to delegate the subnet for Azure NetApp Files. In each VNet, only one subnet can be delegated to Azure NetApp Files.   
+        If you have not delegated a subnet, select **Create new** on the Create a Volume page. Then in the Create Subnet page, specify the subnet information, and select **Microsoft.NetApp/volumes** to delegate the subnet for Azure NetApp Files. In each VNet, only one subnet can be delegated to Azure NetApp Files.   
 
         :::image type="content" source="../media/azure-netapp-files/azure-netapp-files-new-volume.png" alt-text="Screenshot of create new volume interface." lightbox="../media/azure-netapp-files/azure-netapp-files-new-volume.png":::
 

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

@@ -25,16 +25,21 @@ You must delegate a subnet to Azure NetApp Files. When you create a volume, you
 
     Once the delegated network is created, its network mask cannot be altered. Thus it's essential to thoughtfully plan your virtual network (VNet) and delegated subnet sizes with an eye toward the future.
 
-* When creating the delegated subnet, an specific route will be programmed for the subnet range, apart from the route for the entire Virtual Network space.
+* When creating the delegated subnet, a specific route will be programmed for the subnet range, apart from the route for the entire Virtual Network space.
 
 * In each VNet, only one subnet can be delegated to Azure NetApp Files.   
-   Azure enables you to create multiple delegated subnets in a VNet.  However, any attempts to create a new volume would fail if you use more than one delegated subnet.  
+   Azure enables you to create multiple delegated subnets in a VNet. However, any attempts to create a new volume would fail if you use more than one delegated subnet.  
    You can have only a single delegated subnet in a VNet. A NetApp account can deploy volumes into multiple VNets, each having its own delegated subnet.  
 * If you're using Basic network features, you can't designate a network security group (NSG) or service endpoint in the delegated subnet. Doing so causes the subnet delegation to fail. To designate an NSG or service endpoint, [upgrade to Standard network features](configure-network-features.md).
 * Access to a volume from a globally peered virtual network isn't currently supported using Basic networks features. Global VNet peering is supported with Standard network features. For more information, see [Supported network topologies](azure-netapp-files-network-topologies.md#supported-network-topologies).
 * For Azure NetApp Files support of [User-defined routes](../virtual-network/virtual-networks-udr-overview.md#custom-routes) (UDRs) and Network security groups (NSGs), see [Constraints in Guidelines for Azure NetApp Files network planning](azure-netapp-files-network-topologies.md#constraints).   
    To establish routing or access control ***to*** the Azure NetApp Files delegated subnet, you can apply UDRs and NSGs to other subnets, even within the same VNet as the subnet delegated to Azure NetApp Files.  
 
+### Considerations for Elastic zone-redundant storage 
+<!-- ZRS --> 
+* The subnet size should be large enough to accommodate placement of all your resources; in most cases, /24 works, however you should assess based on your specific needs. You can't update the subnet after creating the capacity pool.  
+* The subnet must be delegated to the `Microsoft.NetApp/elasticVolumes` service.
+
 ## Steps
 
 1.	Navigate to **Virtual networks** in the Azure portal. Select the virtual network that you want to use for Azure NetApp Files.    

articles/azure-netapp-files/azure-netapp-files-delegate-subnet.md

@@ -16,16 +16,16 @@ Azure NetApp Files is an Azure native, first-party, enterprise-class, high-perfo
 
 Key attributes of Azure NetApp Files are:
 
-- Performance, cost optimization, and scale.
-- Simplicity and availability.
-- Data management and security.
+- Performance, cost optimization, and scale
+- Simplicity and availability
+- Data management and security
 
 Azure NetApp Files supports SMB, NFS, and dual protocols volumes and can be used for use cases such as:
 
-- File sharing.
-- Home directories.
-- Databases.
-- High-performance computing.
+- File sharing
+- Home directories
+- Databases
+- High-performance computing
 
 >[!NOTE]
 >Azure NetApp Files also supports integrations with S3. For more information, see [Understand object REST API](object-rest-api-introduction.md).
@@ -40,7 +40,7 @@ Azure NetApp Files is designed to provide high-performance file storage for ente
 | - | - | - | 
 | 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 object REST API based on S3 protocol. | Seamlessly integrate with existing infrastructure and workflows without compatibility issues or complex configurations. Azure NetApp Files also integrates with Microsoft Fabric through OneLake, and object-based services 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.
+| Five adaptable performance tiers (Elastic zone-redundant, Flexible, Standard, Premium, Ultra) | Five 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.
@@ -53,22 +53,26 @@ Azure NetApp Files is designed to provide high-performance file storage for ente
 | Datastores for Azure VMware Solution | Use Azure NetApp Files as a storage solution for VMware workloads in Azure, reducing the need for superfluous compute nodes normally included with Azure VMware Solution expansions. | Save money by eliminating the need for unnecessary compute nodes when you expand storage, resulting in significant cost savings.
 | Cool access | Use the cool access option of Azure NetApp Files to move inactive data transparently from Azure NetApp Files storage (the hot tier) to an Azure Storage account (the cool tier). | Save money by transitioning data that resides within Azure NetApp Files volumes (the hot tier) by moving blocks to the lower-cost storage (the cool tier). |
 
+\* To understand specifics about service level changes, see [Azure NetApp Files service levels](azure-netapp-files-service-levels.md).
+
 These features work together to provide a high-performance file storage solution for the demands of enterprise workloads. They help to ensure that your workloads experience optimal (low) storage latency, cost, and scale.
 
 ## Simplicity and availability
 
+<!-- ZRS storage update -->
+
 Azure NetApp Files is designed to provide simplicity and high availability for your file storage needs. Key features include:
 
 | Functionality | Description | Benefit | 
 | - | - | - | 
 | Volumes as a service | Provision and manage volumes in minutes with a few clicks like any other Azure service. | Enables businesses to quickly and easily provision and manage volumes without the need for dedicated hardware or complex configurations.
 | Native Azure integration | Integration with the Azure portal, REST, CLI, billing, monitoring, and security. | Simplifies management and ensures consistency with other Azure services while providing a familiar interface and integration with existing tools and workflows.
-| High availability | Azure NetApp Files provides a [high-availability SLA](https://azure.microsoft.com/support/legal/sla/netapp/) with automatic failover. | Ensures that data is always available and accessible, avoiding downtime and disruption to business operations.
+| High availability | Azure NetApp Files provides a [high-availability SLA](https://azure.microsoft.com/support/legal/sla/netapp/) with automatic failover. | Ensures that data is always available and accessible, avoiding downtime and disruption to business operations. |
 | Application migration | Migrate applications to Azure without refactoring. | Enables businesses to move their workloads to Azure quickly and easily without the need for costly and time-consuming application refactoring or redesign.
 | Cross-region and cross-zone replication | Replicate data between regions or zones. | Provides disaster recovery capabilities and ensures data availability and redundancy across different Azure regions or availability zones.
 | Application volume groups | Application volume groups enable you to deploy all application volumes according to best practices in a single one-step and optimized workflow. | Simplified multi-volume deployment for applications ensures volumes and mount points are optimized and adhere to best practices in a single step, saving time and effort.
-| Programmatic deployment | Automate deployment and management with APIs and SDKs. | Enables businesses to integrate Azure NetApp Files with their existing automation and management tools, reducing the need for manual intervention and improving efficiency.
-| Fault-tolerant bare metal | Built on a fault-tolerant bare-metal fleet powered by ONTAP. | Ensures high performance and reliability by using a robust, fault-tolerant storage platform and powerful data management capabilities provided by ONTAP.
+| Programmatic deployment | Automate deployment and management with APIs and SDKs. | Enables businesses to integrate Azure NetApp Files with their existing automation and management tools, reducing the need for manual intervention and improving efficiency. |
+| Fault-tolerant bare metal | Built on a fault-tolerant bare-metal fleet powered by ONTAP. | Ensures high performance and reliability by using a robust, fault-tolerant storage platform and powerful data management capabilities provided by ONTAP. |
 | Azure native billing | Integrates natively with Azure billing, providing a seamless and easy-to-use billing experience, based on hourly usage. | Easily and accurately manage and track the cost of using the service for seamless budgeting and cost control. Easily track usage and expenses directly from the Azure portal for a unified experience for billing and management. |
 
 These features work together to provide a simple-to-use and highly available file storage solution. This solution ensures that your data is easy to manage and always available, recoverable, and accessible to your applications, even in an outage.