-
Notifications
You must be signed in to change notification settings - Fork 90
Description
Storage Explorer Version
1.40.2
Regression From
No response
Architecture
x64
Storage Explorer Build Number
110
Platform
All
OS Version
Windows 11
Bug Description
Whenever I drag-and-drop a file from Microsoft Outlook into Azure Storage Explorer (upload to a blob/container), Azure Storage Explorer renames the uploaded file by appending “(1)” to the filename, even when there is no existing blob with the same name.
Example:
report.pdf → report (1).pdf
This happens every time, making it difficult to preserve original filenames and causing downstream issues for workflows that rely on exact names.
Resource Types
No response
Authentication Method
None
Connection Type
None
Steps to Reproduce
- Open Microsoft Outlook (desktop app).
- Locate an email attachment (or an item you can drag as a file).
- Open Azure Storage Explorer.
- Navigate to a Blob Container (or relevant storage location).
- Drag the attachment/file from Outlook and drop it into Azure Storage Explorer to upload.
- Observe the uploaded blob name.
Actual Experience
Azure Storage Explorer uploads the file but renames it by appending “(1)” (e.g., report (1).pdf) every time, even when there’s no filename conflict.
Expected Experience
The uploaded blob should keep the original filename exactly (e.g., report.pdf) unless there is a true naming collision.
Additional Context
No response