Merge pull request #310740 from khdownie/kendownie012126-3

Update Files Storage Mover article for NFS support

Author: AnnaMHuff

articles/storage/files/TOC.yml

@@ -91,7 +91,7 @@
     href: migrate-files-between-shares.md
   - name: Target a cloud-only deployment
     items:
-    - name: Use Azure Storage Mover to migrate to SMB Azure file shares
+    - name: Use Azure Storage Mover to migrate to Azure file shares
       href: migrate-files-storage-mover.md
     - name: Use Robocopy to migrate to SMB Azure file shares
       href: storage-files-migration-robocopy.md

articles/storage/files/migrate-files-storage-mover.md

@@ -1,19 +1,19 @@
 ---
 title: Migrate to Azure Files using Azure Storage Mover
-description: Learn how to migrate on-premises file shares to SMB Azure file shares with full fidelity using Azure Storage Mover, a fully managed migration service.
+description: Learn how to migrate on-premises SMB or NFS file shares to Azure file shares with full fidelity using Azure Storage Mover, a fully managed migration service.
 ms.service: azure-file-storage
 ms.topic: how-to
 ms.date: 01/21/2026
 ms.author: kendownie
 author: khdownie
-# Customer intent: "As an IT administrator, I want to migrate on-premises SMB file shares to SMB Azure file shares using a managed service, so that I can ensure full fidelity transfer and streamline my data management in the cloud."
+# Customer intent: "As an IT administrator, I want to migrate on-premises file shares to Azure file shares using a managed service, so that I can ensure full fidelity transfer and streamline my data management in the cloud."
 ---
 
-# Use Azure Storage Mover to migrate to SMB Azure file shares
+# Use Azure Storage Mover to migrate to Azure file shares
 
-**Applies to:** :heavy_check_mark: SMB Azure file shares
+**Applies to:** :heavy_check_mark: SMB and NFS Azure file shares
 
-This migration guide describes how to migrate on-premises files to SMB Azure file shares with full fidelity using [Azure Storage Mover](../../storage-mover/service-overview.md), a fully managed migration service. You can use Storage Mover to migrate from any SMB source share, including Windows Server, Linux, or NAS. You don't need an SMB connection to your Azure file share because Storage Mover uses the FileREST API to move the data instead of SMB.
+This migration guide describes how to migrate on-premises files to Azure file shares with full fidelity using [Azure Storage Mover](../../storage-mover/service-overview.md), a fully managed migration service. You can use Storage Mover to migrate from SMB or NFS source shares, including Windows Server, Linux, or NAS. Storage Mover uses the FileREST API to move the data.
 
 Storage Mover isn't currently available in Azure Government clouds.
 
@@ -22,22 +22,22 @@ Storage Mover isn't currently available in Azure Government clouds.
 
 ## Why use Storage Mover to migrate to Azure file shares?
 
-There are several reasons to use Storage Mover to migrate your on-premises SMB file shares to Azure file shares.
+There are several reasons to use Storage Mover to migrate your on-premises file shares to Azure file shares.
 
 - It's faster than other methods such as Robocopy that depend on SMB to move the data to the cloud.
-- [Supported file metadata](storage-files-migration-overview.md#supported-metadata) is copied with full fidelity. Unlike object storage in Azure Blobs, an Azure file share can natively store file metadata, and it's important to make sure metadata gets copied from source to target during a migration.
+- [Supported file metadata](storage-files-migration-overview.md#supported-metadata) is copied with full fidelity. Unlike object storage in Azure Blobs, an Azure file share can natively store file metadata, and it's important to make sure metadata gets copied from source to target during a migration. When migrating from an SMB source, folder structure and metadata values such as file and folder timestamps, ACLs, and file attributes are maintained.
+- Storage Mover supports both SMB and NFS source shares, giving you flexibility when migrating from different storage systems.
 - It scales well, having been tested with 100 million namespace items (files and folders) from an SMB mount to Azure file shares.
 
 ## Prerequisites
 
-To use Storage Mover to migrate your SMB file shares, the following are required:
+To use Storage Mover to migrate your file shares, the following are required:
 
 - An Azure subscription and resource group. [Review required permissions](../../storage-mover/deployment-planning.md#permissions).
-- An Azure storage account with at least one SMB Azure file share.
+- An Azure storage account with at least one Azure file share.
 - Your local network must allow the Storage Mover agent to communicate with Azure. Port 443 (TLS) must be open outbound, and your firewall rules shouldn't limit traffic to Azure. Use the connectivity checker on the Storage Mover agent console to learn about the endpoint URLs in Azure that you must allow.
-
-> [!NOTE]
-> Storage Mover supports using an SMB mount as the source and an SMB Azure file share as the target. Migrating data between other source-target pairs, such as source data on an NFS share to an Azure file share target, isn't currently supported.
+- For SMB source shares: Credentials (username and password) with read access to the source share.
+- For NFS source shares: The NFS export must be accessible from the Storage Mover agent VM.
 
 ## Migrate files and metadata using Storage Mover
 
@@ -49,13 +49,13 @@ To migrate your data, follow these steps.
 
 1. To utilize your agent for a migration and manage it from the cloud, you need to [register the agent VM(s) with your Storage Mover resource](../../storage-mover/agent-register.md). You need to connect locally over SSH to the agent for registration, and all subsequent steps are managed from the Azure portal, Azure PowerShell, or Azure CLI.
 
-1. Now you must [define your source and target endpoints](../../storage-mover/endpoint-manage.md) in preparation for migrating your data. When creating the target endpoint, select **File share** for **Target type**.
+1. Now you must [define your source and target endpoints](../../storage-mover/endpoint-manage.md) in preparation for migrating your data. When creating the source endpoint, select either **SMB share** or **NFS share** depending on your source protocol. When creating the target endpoint, select **File share** for **Target type**.
 
 1. [Create a project](../../storage-mover/project-manage.md) to collate the shares that need to be migrated together.
 
-1. [Create an Azure Key Vault](/azure/key-vault/general/quick-create-portal) and place two secrets in it: one for the username and one for the password the agent can use to access the source SMB share.
+1. **For SMB source shares only:** [Create an Azure Key Vault](/azure/key-vault/general/quick-create-portal) and place two secrets in it: one for the username and one for the password the agent can use to access the source SMB share. NFS source shares don't require Key Vault credentials.
 
-1. [Define your first migration job](../../storage-mover/job-definition-create.md) in your Storage Mover project, using the source and target pair you've created. For the first migration job, it's best to use the Azure portal. You'll create multiple resources within your Storage Mover resource. There will be a source endpoint and a target endpoint, as well as a few migration settings you should review carefully. In addition, you'll reference the Azure Key Vault secrets when creating your migration job.
+1. [Define your first migration job](../../storage-mover/job-definition-create.md) in your Storage Mover project, using the source and target pair you've created. For the first migration job, it's best to use the Azure portal. You'll create multiple resources within your Storage Mover resource. There will be a source endpoint and a target endpoint, as well as a few migration settings you should review carefully. For SMB sources, you'll reference the Azure Key Vault secrets when creating your migration job.
 
 1. Once your migration job and its settings are as you want them, you can start the job. Telemetry and copy logs will help you monitor the progress and success of your migration job. If you want to estimate the time required to perform your migration job, see [Storage Mover scale and performance targets](../../storage-mover/performance-targets.md#performance-baselines).
 
@@ -65,7 +65,7 @@ When the migration job is complete, you should find all the files and folders in
 
 ## Next steps
 
-Make sure you've [enabled backup](../../backup/azure-file-share-backup-overview.md) for your Azure file shares.
+Make sure you've [enabled backup](../../backup/azure-file-share-backup-overview.md) for your SMB Azure file shares.
 
 ## See also