Azure Storage Documentation

NFS Protocol Support in Azure Files

Azure Files offers native support for the Network File System (NFS) version 4.1 protocol. This allows you to mount Azure file shares from Linux, macOS, and Windows clients using standard NFS clients. This feature is ideal for traditional enterprise workloads that rely on shared file systems and require POSIX-compliant file access semantics.

Key Features of NFS Support

  • NFSv4.1 Protocol: Leverages the latest NFS protocol version for enhanced performance and security.
  • POSIX Compliance: Provides a fully POSIX-compliant file system experience.
  • High Availability and Durability: Built on the Azure Storage platform, offering the same durability and availability guarantees.
  • Scalability: Scales to meet the demands of various workloads.
  • Integration: Seamlessly integrates with other Azure services.

Benefits of Using NFS on Azure Files

  • Lift and Shift Legacy Applications: Migrate existing Linux/Unix applications that depend on NFS shares without significant code changes.
  • Development and Testing: Provide a shared development environment for teams working on Linux-based projects.
  • Containerized Workloads: Use Azure Files as persistent storage for containerized applications running on Azure Kubernetes Service (AKS) or other orchestrators.
  • Big Data Analytics: Support shared data access for big data processing frameworks.

Getting Started with NFS Shares

Prerequisites

  • An Azure subscription.
  • A Storage Account configured to support NFS.
  • A File Share within that storage account.

Creating an NFS-enabled File Share

When creating a file share, ensure you select the appropriate options for NFS support. This typically involves enabling the NFS protocol during the storage account creation or configuration.

Note: NFS shares are only available in specific Azure regions. Please consult the Azure documentation for the latest region availability.

Mounting an NFS Share

Once your NFS-enabled file share is created, you can mount it to your client machines. The mount command will vary slightly depending on your operating system.

Mounting from a Linux Client

Use the following command structure, replacing placeholders with your specific details:

sudo mount -o sec=sys,vers=4.1,nobrl <storage-account-name>.file.core.windows.net/<share-name> /mnt/<mount-point>

Where:

  • <storage-account-name> is the name of your storage account.
  • <share-name> is the name of your file share.
  • /mnt/<mount-point> is the local directory where you want to mount the share.

Mounting from a macOS Client

The process is similar to Linux. Ensure you have the necessary NFS client tools installed.

sudo mount -t nfs -o sec=sys,vers=4.1,nobrl <storage-account-name>.file.core.windows.net:/<storage-account-name>/<share-name> /Volumes/<mount-point>

Security Considerations

NFSv4.1 supports several security mechanisms. The sec=sys option uses Unix-style user authentication (UID/GID). For more advanced security, consider integrating with other Azure identity services.

Tip: For persistent mounts, consider adding an entry to your /etc/fstab file on Linux clients.

Limitations

While NFSv4.1 on Azure Files is powerful, there are some limitations to be aware of:

  • NFSv4.1 support is region-specific.
  • Certain NFS features or options might not be fully supported.
  • Performance can be influenced by network latency and client configuration.

Next Steps

Explore the following resources to learn more: