Networking FAQs for Azure NetApp Files
This article answers frequently asked questions (FAQs) about Azure NetApp Files networking.
Does the data path for NFS or SMB go over the Internet?
No. The data path for NFS or SMB doesn't go over the Internet. Azure NetApp Files is an Azure native service that is deployed into the Azure Virtual Network (VNet) where the service is available. Azure NetApp Files uses a delegated subnet and provisions a network interface directly on the VNet.
See Guidelines for Azure NetApp Files network planning for details.
Can I connect a VNet that I already created to the Azure NetApp Files service?
Yes, you can connect VNets that you created to the service.
See Guidelines for Azure NetApp Files network planning for details.
Can I mount an NFS volume of Azure NetApp Files using DNS FQDN name?
Yes, you can, if you create the required DNS entries. Azure NetApp Files supplies the service IP for the provisioned volume.
Note
Azure NetApp Files can deploy additional IPs for the service as needed. DNS entries may need to be updated periodically.
Can I set or select my own IP address for an Azure NetApp Files volume?
No. IP assignment to Azure NetApp Files volumes is dynamic. Static IP assignment isn't supported.
Does Azure NetApp Files support dual stack (IPv4 and IPv6) VNet?
No. Azure NetApp Files doesn't currently support deploying volumes in a dual-stack (IPv4 and IPv6) delegated subnet. The delegated subnet for the Azure NetApp Files service must be an IPv4-only subnet. However, Azure NetApp Files is accessible over IPv4 through a dual-stack subnet or (peered) VNet.
Is the number of the IP addresses using Azure VMware Solution for Guest OS mounts limited to 1000?
No. Azure VMware Solution is behind an ER gateway, which makes it behave similar to on-premises systems. The number of AVS "Hosts" and "Guests" is n visible to Azure NetApp Files, and the 1000 IP address limit isn't applicable.
Can I use DNS A/AAAA records or CNAME records to connect to Azure NetApp Files volumes?
Azure NetApp Files provides full support for using both A/AAAA (hostname) and CNAME (alias) records in DNS when connecting to NFS and SMB shares. Both types of records can be used for hostname to IP resolution, load balancing, preserving legacy mount paths when data has been migrated, and more.
For further flexibility, see How to use DFS Namespaces with Azure NetApp Files.