microsoft / microsoft/AzureStorageExplorer
Attach Directory doesn't navigate to the parent directory when opened from a blob SAS direct link
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 452
- Forks
- 92
- Avg merge
- 15h 20m
- Merged PRs (30d)
- 3
Description
Storage Explorer Version
1.46.0
Regression From
1.43.0
Architecture
arm64
Storage Explorer Build Number
20260918.10
Platform
All
OS Version
Windows 11 arm64/Windows 11 x64/MacOS Tahoe 26.7 /Linux Ubuntu 22.04
Bug Description
When opening a SAS direct link that points directly to a blob, selecting Attach Directory opens the blob file instead of its parent directory.
Resource Types
Blobs, ADLS Gen2 blobs
Authentication Method
Sign in
Connection Type
No response
Steps to Reproduce
- Launch storage explorer.
- Expand one storage account -> Blob Contaienrs.
- Create a blob container -> Upload one blob.
- Generate a SAS URL for the blob container.
- Convert it to a SAS direct link (storageexplorer://...) -> Add the blob name to it.
- Go to File -> Open Direct Link.
- Paste the SAS direct link.
- In the dialog, select Attach Directory.
- Observe the attached resource.
Actual Experience
The path remains at the blob level.
Expected Experience
Should attach to the directory folder instead of the blob.
Additional Context
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at File → Open Direct Link and trace the Attach Directory handling for a storageexplorer:// SAS link that targets a blob. Reproduce with a blob and its parent container, then verify that Attach Directory selects the parent directory rather than the blob for Blob and ADLS Gen2 resources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100