Azure Files is a distributed cloud file system serving file system SMB and REST protocols generally available since 2015. Customers love how Azure Files enables them to easily lift and shift their legacy workloads to the cloud without any modifications or changes in technology. SMB works great on both Windows and UNIX operating systems for most use cases. However, because some applications are written for POSIX compliant file systems, our customers wanted to have the same great experience on a fully POSIX compatible NFS file system. Today, it’s our pleasure to announce Azure Files support for NFS v4.1 protocol!
NFS 4.1 support for Azure Files will provide our users with a fully managed NFS file system as a service. This offer is built on a truly distributed resilient storage platform that serves Azure Blobs, Disks, and Queues, to name just a few components of Azure Storage. It is by nature highly available and highly durable. Azure Files also supports full file system access semantics such as strong consistency and advisory byte range locking, and can efficiently serve frequent in-place updates to your data.
Common use cases
Azure Files NFS v4.1 has a broad range of use cases. Most applications
As businesses look to the cloud to ensure business resiliency and to spur innovation, we continue to see customer migrations to Azure accelerate. Increasingly, we’ve heard from business leaders preparing to migrate that they could learn from our best practices and want general help thinking about migration, and we started a blog series to help share those even more broadly. In our kick-off blog for this series, we shared that landing zones are a key component to anticipating and mitigating complexities as part of your migration. In this blog, we will cover what landing zones are and the importance of getting cloud destinations ready in advance of the physical migration, as that generates significant benefit in the long-term.
IT and business leaders often ask us about how they can both enable their teams to innovate with agility in Azure and remain compliant within organizational governance, security, and efficiency guardrails. Getting this balance right is critical to cloud migration success. One of the most important questions to getting it right is how to set up destination Azure environments we call landing zones.
At Microsoft, we believe that cloud agility isn’t at odds with setting up the right foundation for migration initiatives—in fact,