Release notes for the Azure Storage Mover service

Azure Storage Mover is a hybrid service, which continuously introduces new features and improvements to its cloud service and agent components. New features often require a matching agent version that supports them. This article provides a summary of key improvements for each service and agent version combination that is released. The article also points out limitations and if possible, workarounds for identified issues.

Supported agent versions

The following Azure Storage Mover agent versions are supported:

Milestone	Version number	Release date	Status
Support for data transfers from NFS source to Azure Files NFS target and OS update	4.0.902	October 22, 2025	Current. Release is available for VM image only and existing agents cannot update to this.
Enhanced Network checks and OS update	3.4.846	Jul 30, 2025	Latest update for existing agents
Enhanced Network checks and support for data transfers from SMB source to Azure Blob target	3.3.760	April 8, 2025	Supported. Downloading latest agent from Microsoft Download Center is recommended.
Refresh release	3.3.708	January 28, 2025	No longer supported. Decommission and download latest agent from Microsoft Download Center.
Bandwidth Management and general improvements	3.1.613	July 10, 2024	No longer supported. Decommission and download latest agent from Microsoft Download Center.
Performance and security improvements	3.1.593	June 16, 2024	No longer supported. Decommission and download latest agent from Microsoft Download Center.
Agent registration and private networking improvements	3.0.500	April 2, 2024	No longer supported. Decommission and download latest agent from Microsoft Download Center.
Important security release	3.0.412	November 30, 2023	No longer supported. Decommission and download latest agent from Microsoft Download Center.
Major refresh release	2.0.358	November 6, 2023	No longer supported. Decommission and download latest agent from Microsoft Download Center.
Refresh release	2.0.287	August 5, 2023	No longer supported. Decommission and download latest agent from Microsoft Download Center.
Refresh release	1.1.256	June 14, 2023	No longer supported. Decommission and download latest agent from Microsoft Download Center.
General availability release	1.0.229	April 17, 2023	No longer supported. Decommission and download latest agent from Microsoft Download Center.
Public preview release	0.1.116	September 15, 2022	No longer supported. Decommission and download latest agent from Microsoft Download Center.

Azure Storage Mover update policy

Preview agents aren't automatically updated. Beginning with the general availability release of service and agent, all GA Azure Storage Mover agents are automatically updated to future versions. GA and newer agents automatically download and apply new functionality and bug fixes. If you need to deploy another Storage Mover agent, you can find the latest available agent version on Microsoft Download Center. Be sure to register your newly deployed agent before you can utilize them for your migrations.

The automatic agent update doesn't affect running migration jobs. Running jobs are allowed to complete before the update is locally applied on the agent. Any errors during the update process result in the automatic use of the previous agent version. In parallel, a new update attempt is started automatically. This behavior ensures an uninterrupted migration experience.

Tip

Always download the latest agent version from Microsoft Download Center. https://aka.ms/StorageMover/agent. Redistributing previously downloaded images might no longer be supported (check the Supported agent versions table), or they might need to update themselves before for use. Speed up your deployments by always obtaining the latest image from Microsoft Download Center.

Lifecycle and change management guarantees

Azure Storage Mover is a hybrid service, which continuously introduces new features and improvements. Azure Storage Mover agent versions can only be supported for a limited time. Agents automatically update themselves to the latest version. There's no need to manage any part of the self-update process. However, agents need to be running and connected to the internet to check for updates. To facilitate updates to agents that haven't been running for a while:

• Major versions are supported for at least six months from the date of initial release.
• We guarantee there's an overlap of at least three months between the support of major agent versions.
• The Supported agent versions table lists expiration dates. Expired agent versions, might still be able to update themselves to a supported version but there are no guarantees.

Important

Preview versions of the Storage Mover agent can't update themselves. You must replace them manually by deploying the latest available agent.

2025 October 22

Refresh release notes for:

• Service version: Sep 30, 2025
• Agent version: 4.0.902

What's new

• Ability to migrate data from NFS source to Azure Files NFS target
• Upgraded Mover VM Linux version to 6.8.0-1031-azure

2025 Jul 30

Refresh release notes for:

• Service version: Jul 30, 2025
• Agent version: 3.4.846

What's new

• Ability to test HTTP endpoint connectivity using Curl and Traceroute
• Upgraded Mover VM Linux version to 6.8.0

2025 May 30

Refresh release notes for:

• Service version: May 30, 2025
• Agent version: 3.3.760

What's new

• Support for migrations from SMB shares to Azure Blob targets

2025 April 8

Major refresh release notes for:

• Service version: April 8, 2025
• Agent version: 3.3.760

What's new

• Network check during registration
• Bug fix to show system configuration correctly for CPU speed

2025 January 28

Major refresh release notes for:

• Service version: January 28, 2025
• Agent version: 3.3.708

What's new

• Proxy-related improvements and bug fixes
• Security and performance improvements and bug fixes
• Ability to collect and diagnose SMB mount related issues
• Ability to use included network diagnostics tools - ping, nslookup
• Improved Unicode character handling for SMB source

2024 August 30

Major refresh release notes for:

• Service version: August 30, 2024
• Agent version: 3.1.636

What's new

• Stricter password restrictions.
• Security improvements and bug fixes.

2024 July 10

Major refresh release notes for:

• Service version: July 2, 2024
• Agent version: 3.1.613

What's new

• Supports WAN link bandwidth management schedules. (see documentation)
• Performance optimizations.
• Security improvements and bug fixes.

2024 June 16

Refresh release notes for:

• Service version: June 10, 2024
• Agent version: 3.1.593

What's new

• You can now collect support bundles from the agent VM even if a part of it isn't running.
• The agent can now handle data migration from SMB shares that don't support INodes.
• Improved agent registration reliability.
• Security improvements and bug fixes.

2024 April 2

Refresh release notes for:

• Service version: April 2, 2024
• Agent version: 3.0.500

What's new

• Improved agent registration: You can now add tags to the ARC machine that the agent creates.
• Improved network connectivity testing: The Storage Mover agent now utilizes the Azure ARC CLI azcmagent tool and a curl GET command to verify the ARC and Storage Mover endpoints with the 'Test Network Connectivity' option in the agent console.
• A new option, 'Test Network Connectivity Verbosely' can help diagnose local network problems more easily.
• Improved user experience to error conditions during agent registration and unregistration processes.
• Storage Mover depends on Azure ARC and a Managed Identity. Extra safeguards were added that ensure seamless registration: The ARC Hybrid Compute resource is now created in the same region as the storage mover resource and the Azure Arc Private Link Scope (if applicable).
• Improved instructions during agent registration when using private networking.
• Security improvements and bug fixes.

2023 December 1

Major refresh release notes for:

• Service version: December 1, 2023
• Agent version: 3.0.412

What's new

• Extended support to the SMB 2.0 protocol (vs. previously SMB 2.1+)
• Security improvements and bug fixes.

Limitations

Important

Based on the previously described Azure Storage Mover update policy, agents are automatically updated to the latest version. However, some improvements require a download and provisioning of a new agent VM, using the latest agent image from Microsoft Download Center. This action is recommended for all customers with agent deployments earlier than this release date.

2023 November 6

Major refresh release notes for:

• Service version: November 6, 2023
• Agent version: 2.0.358

Migration scenarios

• Migrating your SMB shares to Azure file shares became generally available.
• The Storage Mover agent is now supported on VMware ESXi 6.7 hypervisors, as a public preview.
• Migrating NFS shares to Azure Data Lake Gen2 storage is now available as a public preview.

Service

• Migrations from NFS shares to Azure storage accounts with the hierarchical namespace service feature (HNS) enabled, are now supported and automatically apply the ADLS Gen2 REST APIs for migration. This API allows the migration of files and folders in a Data Lake compliant way. Full fidelity is preserved in just the same way as with the previously existing blob container migration path.
• Error codes and messages were improved.

Agent

• Changes required for the previously mentioned migration paths.
• Changes to improve handling and logging of files that fail migration when they contain invalid characters or are in use during a migration.
• Support for file and folder security descriptors larger than 8 KiB. (ACLs)
• Ability to avoid a job error condition when the source is an empty SMB share.
• Improvements to agent-local network configuration like applying a static IP to the agent, or an error listing certain network configuration.
• Security improvements.
• The same agent version is now supported to run across Hyper-V and VMware ESXi 6.7 hypervisors.

Limitations

Important

Based on the previously described Azure Storage Mover update policy, agents are automatically updated to the latest version. However, some improvements require a download and provisioning of a new agent VM, using the latest agent image from Microsoft Download Center.

2023 August 5

Refresh release notes for:

• Service version: August 5, 2023
• Agent version: 2.0.287

Migration scenarios

Azure Storage mover can migrate your SMB share to Azure file shares (in public preview).

Service

• Two new endpoints were introduced.
• Error messages were improved.

Agent

• Changes to include handling of SMB sources and the data plane transfer to Az Files
• Handling SMB credentials via Azure Key Vault.

Limitations

• Folder ACLs aren't updated on incremental transfers.
• Last modified dates on folders aren't preserved.

2023 June 14

Refresh release notes for:

• Service version: June 12, 2023
• Agent version: 1.1.256

Migration scenarios

Existing migration scenarios from the GA release remain unchanged. This release contains fixes to small issues and feature optimizations.

Service

• Fixed a corner-case issue where the mirror copy mode might miss changes made in the source since the job was last ran.
• Fixed an issue when moving a Storage Mover resource to a different resource group. It was possible for some properties to be left behind.
• Improved error messages.

Agent

• Fixed an issue with registration failing sometimes when a proxy server connection and a private link scope were configured at the same time.
• Improved the security stance by omitting to transmit a specific user input to the service that is no longer necessary.

2023 April 17

General availability release notes for:

• Service version: April 17, 2023
• Agent version: 1.0.229

Migration scenarios

Support for a migration from an NFS (v3 / v4) source share to an Azure blob container (not HNS enabled).

Migration options

In addition to merging content from the source to the target (public preview), the service now supports another migration option: Mirror content from source to target.

• Files in the target are deleted if they don’t exist in the source.
• Files and folders in the target are updated to match the source.
• Folder renames between copies lead to the deletion of the cloud content and reupload of data contained in the renamed folder on the source.

Service

The service now supports viewing copy logs and job logs in the Azure portal. An Azure Log Analytics workspace must be configured to receive the logs. This configuration is done once for a Storage Mover resource and applies to all agents and migration jobs in that Storage Mover resource. To configure an existing Storage Mover resource or learn how to create a new Storage Mover resource with this configuration, follow the steps in the article: How to enable Azure Storage Mover copy and job logs.

It's possible to send the logs to a non-Microsoft monitoring solution and even into a raw file in a storage account. However, the Storage Mover migration job pane in the Azure portal can only query a Log Analytics workspace for the logs. To get an integrated experience, be sure to select a Log Analytics workspace as a target.

Agent

Private link connections from the agent into Azure are supported. Data that is migrated can travel from the agent over a private link connection to the target storage account in Azure. Agent registration can also be accomplished over a private link connection. Agent control messages (jobs, logs) can only be sent over the public endpoint of the Storage Mover agent gateway. If using a firewall or proxy server to restrict public access, make sure the following URL isn't blocked: *.agentgateway.prd.azsm.azure.com. The Azure region in which the Storage Mover resource's registered agents exist is used to determine the concrete URL.

2022 September 15

Initial public preview release notes for:

• Service version: September 15, 2022
• Agent version: 0.1.116

Migration scenarios

Support for a migration from an NFS (v3 / v4) source share to an Azure blob container (not HNS enabled).

Migration options

Supports merging content from the source to the target:

• Files are kept in the target, even if they don’t exist in the source.
• Files with matching names and paths are updated to match the source.
• Folder renames between copies might lead to duplicate content in the target.

Service

• When a job is started w/o the agent having permissions to the target storage and the job is immediately canceled, the job might not close down gracefully and remain in the Cancel requested state indefinitely. The only mitigation at the moment is to delete the job definition and recreate it.
• The Storage Mover service is currently not resilient to a zonal outage within the selected region. Appropriate configuration steps to achieve zonal redundancy are underway.

Agent

• The storage mover agent appliance VM is currently only tested and supported as a Version 1 Windows Hyper-V VM.
• Re-registration of a previously registered agent is currently not supported. Download a new agent image instead.
• When you register an agent, a hybrid compute resource is also deployed into the same resource group as the storage mover resides in. In some cases, unregistering the server doesn't remove the agent's hybrid compute resource. Admins must manually remove it to complete unregistration of the agent and remove all permissions to target storage the agent previously held.
• Copy logs aren't configurable to be emitted to Azure and must be accessed locally.

To access copy logs on the agent:

1. Connect to the agent's administrative shell

From a machine on the same subnet as the agent, run an ssh command:

ssh <AgentIpAddress> -l admin

Important

A newly deployed Storage Mover agent has a default password:
Local user: admin
Default password: admin

You're prompted to change the default password immediately after you first connect to a newly deployed agent. Note down the new password, there's no process to recover it. Losing your password locks you out from the administrative shell. Cloud management doesn't require this local admin password. If the agent was previously registered, you can still use it for migration jobs. Agents are disposable. They hold little value beyond the current migration job they're executing. You can always deploy a new agent and use that instead to run the next migration job.

1. Select option 3) Service and job status
2. Select option 2) Job summary
3. A list of jobs that previously ran on the agent is shown. Copy the ID in the format Job definition id: Job run id that represents the job you want to retrieve the copy logs for. You can confirm the selection of the correct job by looking at the details of your selected job by pasting it into menu option 3) Job details
4. Retrieve the copy logs by selecting option 4) Job copylogs and providing the same ID from the previous step.