microsoft / microsoft/AzureStorageExplorer

Permissions inherited from Management Group are not Respected

Open
#3,438 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

:gear: rbac :grey_question: more info
Dominant language
No language data
Stars
452
Forks
92
Avg merge
15h 20m
Merged PRs (30d)
3

Description

Version: 1.14.2
AzCopy Version: 10.5.0

Platform: Windows
Architecture: ia32
Build Number: 20200715.2
Commit: c8e3bc3d2
Support ID: f5c27f32-53a6-5da6-6cf3-5dced4c7e2f1

Copyright © 2020 Microsoft. All rights reserved.

Bug Description

Permissions that are inherited from a Management Group are not respected.

Steps to Reproduce

  1. Find a Management Group that has multiple subscriptions beneath that have storage accounts in them.
  2. Assign Reader Role for the user at Management Group (with no other roles assigned).
  3. Connect in Microsoft Azure Storage Explorer using the 'Add an Azure Account' option.
  4. Not that no Subscriptions or Storage Accounts are visible.

Expected Experience

I would expect to see all the storage accounts and subscriptions that I can see through the Azure Portal.

Actual Experience

I don't see any subscriptions or storage accounts.

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.

Research direction

Start by reproducing the issue in Microsoft Azure Storage Explorer 1.14.2 on Windows with a Reader role assigned only at the Management Group level. Compare the subscriptions and storage accounts shown in Storage Explorer with those visible in the Azure Portal; done means inherited permissions expose the same resources.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
authorization, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.