Thank you for asking this question on the Microsoft Q&A Platform.
What are the Pros in shifting to AFS?
According to the documentation these are some key benefits:
- Easy to use. When an Azure file share is mounted on your computer, you don't need to do anything special to access the data: just navigate to the path where the file share is mounted and open/modify a file.
- Shared access. Azure file shares support the industry standard SMB and NFS protocols, meaning you can seamlessly replace your on-premises file shares with Azure file shares without worrying about application compatibility. Being able to share a file system across multiple machines, applications, and application instances is a significant advantage for applications that need shareability.
- Fully managed. Azure file shares can be created without the need to manage hardware or an OS. This means you don't have to deal with patching the server OS with critical security upgrades or replacing faulty hard disks.
- Scripting and tooling. PowerShell cmdlets and Azure CLI can be used to create, mount, and manage Azure file shares as part of the administration of Azure applications. You can create and manage Azure file shares using Azure portal and Azure Storage Explorer.
- Resiliency. Azure Files has been built from the ground up to be always available. Replacing on-premises file shares with Azure Files means you no longer have to wake up to deal with local power outages or network issues.
- Familiar programmability. Applications running in Azure can access data in the share via file system I/O APIs. Developers can therefore leverage their existing code and skills to migrate existing applications. In addition to System IO APIs, you can use Azure Storage Client Libraries or the Azure Files REST API.
More info: https://learn.microsoft.com/en-us/azure/storage/files/storage-files-introduction#key-benefits
Incase If we shift to AFS, NFS server which we currently have 2 servers can that be decommissioned ?
Yes.
Do AFS require any separate servers ?
AFS doesn't use a server, AFES is a service in Azure. However, to work with identity-based authentication for Windows file shares over Server Message Block (SMB), you will need to "join to domain" your Azure File (More info: https://learn.microsoft.com/en-us/azure/storage/files/storage-files-identity-auth-active-directory-enable)
Hope this helps!
Accept Answer and Upvote, if any of the above helped, this thread can help others in the community looking for remediation for similar issues.
NOTE: To answer you as quickly as possible, please mention me in your reply.