Azure NetApp Files (ANF) Complete Guide: Service Levels, Capacity Pools, SnapMirror, and SAP HANA Certification

Azure NetApp Files (ANF) is a high-performance enterprise storage service that brings NetApp's ONTAP storage technology to Microsoft Azure. It supports NFSv3/4.1 and SMB 2.1/3.x protocols, with extremely low latency (sub-1ms), very high IOPS (450,000+), and large capacity (up to 1 PB per Capacity Pool). Performance characteristics exceed Azure Files Premium, making it suitable for workloads that demand top-tier storage performance, such as SAP HANA, Oracle Database, HPC workloads, and large-scale ML datasets. Because NetApp operates the platform behind the scenes, ONTAP features like Snapshot, Cross-region Replication, and SnapMirror are available in the cloud. Starting at around 300,000 JPY per month, it is designed exclusively for serious enterprise workloads.

Azure Files Premium: Microsoft-managed general-purpose file shares, SMB / NFS 4.1, up to 100 TB per share and 100,000 IOPS, costing tens of thousands to hundreds of thousands of JPY per month. ANF: NetApp ONTAP-based dedicated storage, NFS 3/4.1 and SMB 2.1/3.x, up to 1 PB per Pool, 450,000+ IOPS, sub-1ms latency, starting at 300,000 JPY per month. Decision criteria: 1) Need sub-1ms latency + 450k+ IOPS → ANF; 2) Need volumes larger than 100 TB → ANF; 3) Need ONTAP features like Cross-region Replication (SnapMirror) → ANF; 4) SAP HANA Certified Storage requirement → ANF; 5) Otherwise sufficient performance → Azure Files Premium. Because the cost difference is significant, carefully analyze requirements before choosing.

ANF Service Levels are performance tiers assigned per Capacity Pool. Standard: 16 MiB/s per TiB, general-purpose where throughput is not critical, cheapest. Premium: 64 MiB/s per TiB, mainstream production use, cost-effective, most widely adopted. Ultra: 128 MiB/s per TiB, top performance for SAP HANA Production and similar workloads. Throughput scales with Capacity Pool size (e.g., a Premium 10 TiB Pool delivers 640 MiB/s), and capacity and performance cannot be tuned independently. A common pattern is to host multiple Capacity Pools with different Service Levels under the same NetApp Account and split them by workload. Cool Access (Standard only, lowest cost) supports archive-like usage, allowing large datasets that do not need throughput to be moved to Cool Access for major cost savings.

ANF uses a three-tier hierarchy: NetApp Account → Capacity Pool → Volume. NetApp Account: the parent ANF resource, one per region. Capacity Pool: assigned a Service Level (Standard/Premium/Ultra) and capacity (4-500 TiB), hosts multiple Volumes within the Pool. Volume: the actual file share endpoint, dynamically resizable inside the Pool, with NFS / SMB protocol choice and QoS (throughput limits). The typical enterprise pattern is one NetApp Account + multiple Capacity Pools (split by Service Level) + many Volumes inside each Pool (split by application). Pool Service Levels can be changed (dynamic upgrade), and Volumes can be moved to a different Pool, enabling flexible operations.

ANF Snapshot: NetApp ONTAP's snapshot feature provides point-in-time copies of volumes with no additional storage consumption (Copy-on-Write), up to 255 snapshots per volume. Snapshot Policy automates regular captures (hourly, daily, weekly) with retention settings. SnapMirror Cross-region Replication: asynchronously replicates volumes to another region with RPO in minutes and RTO in minutes, forming a Disaster Recovery configuration. Available only for Premium / Ultra. Typical DR scenario: SnapMirror from Japan East ANF to Japan West ANF, with failover to Japan West within 15 minutes when the Japan East region fails. Combining Snapshot for point-in-time restore and SnapMirror for disaster recovery is the enterprise standard pattern. Long-term retention is also possible by integrating with Backup vault.

ANF provides enterprise-grade security features: 1) Delegated Subnet for dedicated subnet placement (cannot be shared with other resources); 2) Active Directory integration (Kerberos auth for SMB and NFSv4.1 with Kerberos); 3) Customer-Managed Key (CMK) encryption (Azure Key Vault integration); 4) NFS Export Policy with IP / CIDR-based control; 5) SMB ACL for fine-grained permissions; 6) Encrypted Cross-region Replication traffic (TLS); 7) FIPS 140-2 Level 1 compliance; 8) Microsoft Entra ID auth integration (RBAC); 9) Audit log forwarding to Microsoft Sentinel; 10) Azure Policy integration. To support workloads with the highest security requirements such as SAP HANA Production, financial-institution databases, and healthcare data, production deployments combine the required features appropriately.

ANF cost is determined by Capacity Pool size × Service Level unit price. Standard: about 0.10 USD/GiB/month, Premium: about 0.20 USD/GiB/month, Ultra: about 0.27 USD/GiB/month (Japan East reference pricing). Minimum Pool size is 4 TiB, so Premium 4 TiB costs about 110,000 JPY per month. Reserved Capacity (1-3 year contracts) offers up to 34% off, and Reserved is essential for production. Cost-reduction tactics: 1) Cool Access (Standard only; isolate archive-like data for an extra 0.02 USD/GiB/month); 2) Capacity optimization at the Volume level; 3) Shorter Snapshot retention; 4) Use Standard for non-production environments; 5) Full use of Reserved Capacity. ANF targets serious enterprise use cases with a baseline of around 300,000 JPY per month, so cost expectations differ significantly from other storage options.

AZ-104 (Administrator) covers storage broadly in Domain 2; AZ-305 (Solutions Architect Expert) addresses architecture-level selection (Files vs ANF); AZ-120 (SAP on Azure Specialty) tests ANF deeply as the SAP HANA certified storage and a primary scenario in this area; DP-300 (DBA) covers high-performance storage for Oracle / SQL Server on Azure; AZ-140 (AVD Specialty) covers high-performance FSLogix Profile Container use. ANF is highly specialized storage and a valuable knowledge area for enterprise Azure infrastructure engineers.