microsoft / microsoft/AzureStorageExplorer
Unable to retrieve child resources
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.32
Regression From
No response
Architecture
x64
Storage Explorer Build Number
No response
Platform
All
OS Version
Windows
Bug Description
{"shellProps":{"sessionId":"796d6fb9759c4d7fb3cf69780598bc9f","extName":"Microsoft_Azure_Storage","contentName":"BlobsBlade","resourceId":"/subscriptions/c759bb41-2cae-4a85-9d60-ea475a56a07b/resourceGroups/RG-SSEIBP-UATEST01/providers/Microsoft.Storage/storageAccounts/stsseibpuatest01","code":403},"error":{"message":"This request is not authorized to perform this operation.","code":403,"details":{"htmlTemplate":"
<ul data-bind="foreach: causes">
I cannot open any container from any subscription in any browser
Resource Types
Blobs, ADLBS Gen 2
Authentication Method
Sign in
Connection Type
Sign in (subscription)
Steps to Reproduce
launch exporer / open portal azure
go to storage
open container
get the erro
Actual Experience
Expected Experience
No response
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 by reproducing the failure in Azure Storage Explorer's BlobsBlade using a signed-in subscription and a storage account with the reported firewall settings. Check the reported 403 response and storage-account network access guidance; done means containers open successfully for the affected blob and ADLS Gen2 resources, with the authorization cause identified.
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
- Needs clarification
- Newbie friendliness
- 30/100