Azure Blob Storage

Connections

Create a new connection and choose Azure Blob Storage as its type.

Provide a Connection Label so you can identify the connection in a list. This is especially important if you need more than one connection of the same type.

Account Details

Account - The name of your Azure Storage Account, as shown in your Microsoft Azure web portal > Home > Storage Accounts page.

Container - The name of your Azure Container, as shown in your Microsoft Azure web portal > Home > Storage Accounts > selected storage account > Data Storage > Containers page.

Check the box for Use Hierarchical Namespace (Azure Data Lake Storage Gen2) only if you have enabled the hierarchical namespace option for your Azure Container.

Credentials

Mover can authenticate to Azure Blob Storage using either an Access Key or SAS Token. If you're using Access Key, copy the value from your Microsoft Azure web portal > Home > Storage Accounts > selected storage account > Access Keys. For the SAS Token, copy the value from your Microsoft Azure web portal > Home > Storage Accounts > selected storage account > Shared Access Signature page.

Advanced Settings

If your credentials do not have access to the entire container, or are restricted to specific subfolders only, then Mover may not be able to verify the connection works.

When you do not have access to the entire container, use the advanced setting for Can these credentials access the root of this remote or are they restricted to a subfolder? to specify a subfolder that can be used instead.

Azure Blob Storage is Case Sensitive

Check how the source and destination handle letter case before starting a migration. On a case-sensitive system, MyFile.txt and myfile.txt can be two different files. A case-insensitive system treats those names as the same file.

Mover compares paths without regard to case or accents. When several source or destination items have the same case-insensitive name, Mover skips the duplicates and records the conflict in the run log. A single source file can overwrite a destination file whose name differs only by case when their reported sizes differ. Review the dry-run results and remove case-only duplicates before executing the migration.