microsoft / microsoft/AzureStorageExplorer
It would be better to show a clear error when uploading files to one SAS (generated by access policy) attached file share without sufficient permissions
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.17.0
Build Number: 20210202.9
Branch: main
Platform/OS: Windows 10/ CentOS 7.6.1810 (Core)/ MacOS Catalina
Architecture: ia32/x64
Regression From: Not a regression
Steps to Reproduce
- Expand one storage account -> File Shares.
- Create a file share -> Right click the file share.
- Click 'Manage Access Policies...' -> Add one access policy with permissions 'Read & List' and save it.
- Generate a SAS for the file share with the access policy.
- Attach the file share with the SAS -> Upload one file to the SAS attached file share.
- Check whether the error is clear.
Expected Experience
It would be better to show a clear error. Like 'Insufficient credentials'.
Actual Experience
Show the error 'UnexpectedCancel' in the failed activity log.

Error details:
{
"message": "\"UnexpectedCancel\""
}
Additional Context
- This issue also reproduces for Blob Containers.
- This issue also reproduces for Clone/ Copy & Paste actions.
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 by reproducing the failed upload with a SAS limited to Read and List permissions, then compare the failed activity log with the issue's reported "UnexpectedCancel" error. Trace the error handling for file-share and blob-container uploads, as well as Clone/Copy and Paste actions; done means insufficient permissions produce a clear user-facing error instead of "UnexpectedCancel".
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100