Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article answers frequently asked questions (FAQs) about Azure NetApp Files networking.
Generic FAQs
This section answers generic questions 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 virtual network.
See Guidelines for Azure NetApp Files network planning for details.
Can I connect a virtual network that I already created to the Azure NetApp Files service?
Yes, you can connect virtual networks 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 other 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 of Azure NetApp Files volumes is automatic. Manual IP assignment isn't supported.
Does Azure NetApp Files support dual stack (IPv4 and IPv6) virtual network?
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) virtual network.
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.
FAQs about Standard network features
This section answers questions about Azure NetApp Files Standard network features.
What is changing with Basic Networking in Azure NetApp Files?
All new Azure NetApp Files volumes will use Standard networking by default. Basic network features will no longer be an option. Existing volumes are unaffected, and no customer action is required.
What actions are required from the customer?
No Action is required from the customer.
Will my existing Azure NetApp Files volumes be impacted?
No. Existing volumes using Basic Networking aren't impacted and will continue to operate normally.
Can I still create new volumes using Basic Networking?
No. After the enforcement date, new volumes can't be created with Basic Networking via the Portal, CLI, or APIs.
Is there a cost difference between Basic and Standard networking?
There is no difference when moving from Basic to Standard networking unless you choose other Azure networking features, which involve costs like peering.
Will this change affect the functionality of my scripts or ARM template?
Your scripts and ARM templates remain operational as currently implemented. All requests for basic networking will be set up using Standard networking configurations.
Why do I see an "insufficient resources" error when creating a Standard networking volume?
This can occur if the selected virtual network contains volumes using Basic networking, and the region or availability zone has limited Azure NetApp Files capacity.
How can I fix the "insufficient resources" error when creating a Standard networking volume?
Create the volume in a different virtual network, or upgrade all existing volumes in the virtual network to Standard networking and retry. Contact Microsoft Support if assistance is needed.
How can I avoid the "insufficient resources" error?
Use Standard networking for all new Azure NetApp Files volumes and avoid mixing Basic and Standard networking in the same virtual network and transition existing volumes to Standard networking.
Do I need to migrate my existing volumes to Standard networking now?
No immediate action is required. However, we recommend you to transition existing environments to Standard networking over time as part of normal lifecycle management.
How does this retirement affect future volume creation?
There's no impact on your workload or volume creation ability. With the upgrade to Standard networking, you'll get NSGs on Azure NetApp Files, UDRs on Azure NetApp Files subnet, and many other features.
What is Microsoft’s recommendation going forward?
Use Standard networking for all new deployments and plan to transition existing environments over time as part of normal lifecycle management.