microsoft / microsoft/AzureStorageExplorer

It would be helpful if the Move Files dialog description also included the behavior when a directory with the same name already exists at the destination

Open
#9,070 1 comment 0 reactions 1 assignee View on GitHub

@craxal is already working on this.

Since Jun 15, 2026.

:eye_speech_bubble: ui :gear: adls gen2 :gear: data transfer :gear: files :gear: usability :test_tube: testing :triumph: easy
Dominant language
No language data
Stars
452
Forks
92
Avg merge
15h 20m
Merged PRs (30d)
3

Description

Storage Explorer Version

1.43.0

Regression From

Not a regression

Architecture

arm64

Storage Explorer Build Number

20260513.1

Platform

All

OS Version

Windows 11 arm64/MacOS Tahoe 26.4.3 /Linux Ubuntu 22.04

Bug Description

the Move Files dialog explains that files with the same name at the destination will be overwritten, but it does not mention the behavior for directories.

For ADLS Gen2 blobs and file shares:

Moving a file to a destination where a file with the same name exists succeeds and overwrites the existing file.
Moving a directory to a destination where a directory with the same name exists may fail (for example, in Azure Files, or when the destination directory is non-empty in ADLS Gen2).

Resource Types

ADLS Gen2 blobs/File shares

Authentication Method

None

Connection Type

None

Steps to Reproduce
  1. Expand one ADLS Gen2 storage account-> Blob Containers.
  2. Create a blob container -> Create a folder.
  3. Select the folder and click Move.
  4. Observer the move dialog description,
Actual Experience

The dialog description only states that files with the same name at the destination will be overwritten.

Expected Experience

It would be helpful if the Move Files dialog description also included the behavior when a directory with the same name already exists at the destination.

Additional Context

Here is the move dialog:

Image

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.