| title | description | ms.service | ms.workload | ms.topic | author | ms.author | ms.date |
|---|---|---|---|---|---|---|---|
Networking FAQs for Azure NetApp Files | Microsoft Docs |
Answers frequently asked questions (FAQs) about Azure NetApp Files networking. |
azure-netapp-files |
storage |
conceptual |
b-hchen |
anfdocs |
11/08/2021 |
This article answers frequently asked questions (FAQs) about Azure NetApp Files networking.
No. The data path for NFS or SMB does not 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.
Yes, you can connect VNets that you created to the service.
See Guidelines for Azure NetApp Files network planning for details.
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.
No. IP assignment to Azure NetApp Files volumes is dynamic. Static IP assignment is not supported.
No, Azure NetApp Files does not 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.
No. Azure VMware Solutions is behind an ER gateway, which makes it behave similar to on-premises systems. The number of AVS "Hosts" and "Guests" is not visible to Azure NetApp Files, and the 1000 IP address limit is not applicable.