Azure NetApp Files Config Builder

What This Tool Does

Build Azure NetApp Files capacity pools (Premium/Standard/Ultra service levels, each with a different guaranteed throughput-per-TiB ratio) and volumes with protocol-specific settings, NFS export policies with per-rule client CIDR scoping, and SMB settings requiring Active Directory integration. qosType Manual versus Auto on a capacity pool is a real operational choice: Auto lets each volume's throughput scale automatically with its allocated quota within the pool's service level, while Manual requires you to explicitly assign a throughputMibps ceiling per volume (as the SMB volume's throughputMibps: 128 shows), Manual gives predictable per-volume throughput isolation at the cost of needing deliberate capacity planning across every volume sharing the pool.

Technical Details

Common Use Cases

1. 1Choosing Premium service level for a latency-sensitive application-data volume (vol-nfs-appdata) versus Standard for a less performance-critical SMB file share (vol-smb-fileshare), matching each volume's actual performance requirement to the appropriate (and appropriately priced) capacity pool.
2. 2Scoping an NFS export policy rule's allowedClients to a specific CIDR range (10.1.0.0/16) rather than allowing broad access, so only the intended application subnet can mount the volume, not every client on a larger shared network.
3. 3Enabling coolAccess on the Standard capacity pool specifically, letting infrequently-accessed data automatically tier to cheaper cool storage, appropriate for a pool holding less performance-critical data where occasional higher-latency access on cool-tiered blocks is an acceptable tradeoff for lower storage cost.
4. 4Setting up cross-region dataProtection.replication for the NFS volume with an hourly replicationSchedule, so a regional outage has a recent, restorable replica in westus2 without needing a separate backup product layered on top.

Common Questions

What's the practical difference between qosType Auto and Manual on a capacity pool?

Auto QoS ties each volume's available throughput automatically to its allocated capacity quota within the pool's service level (a larger quota volume automatically gets proportionally more throughput), simpler to manage but less precise control per volume. Manual QoS requires explicitly setting throughputMibps per volume, giving predictable, isolated throughput guarantees per volume regardless of its capacity quota, at the cost of needing to actively plan and sum throughput allocations across every volume sharing the pool's total capacity.

Does rootSquash matter for the NFS export policy, and what does it actually do?

rootSquash, when enabled, maps the remote root user's UID/GID to a non-privileged, anonymous identity on the NFS server side, preventing a client machine's root user from automatically having root-equivalent access to the mounted volume's files. The example explicitly sets rootSquash: false, meaning root on an allowed client does retain root-level access to the volume, an important security consideration to verify matches actual intent, since the default expectation on many NFS deployments is the opposite (squashed root).

Can an SMB volume use Active Directory-based access control without domain-joining every client?

The volume itself needs the activeDirectory configuration (pointing at the DNS and domain) to authenticate SMB access, but this is configured once at the volume/NetApp account level, individual client machines connecting via SMB still need to be domain-joined (or otherwise able to authenticate against that AD domain) to actually access the share with their AD identity, it's not a way to avoid AD entirely for clients, just to centralize where the AD trust relationship is configured.

Expert Tips

Related Learning Guides

• Storage Account Types22 min read
• Cosmos DB Consistency Levels24 min read