Skip to content

Update Understanding access control and data lake configurations in A… #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
navba-MSFT wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update Understanding access control and data lake configurations in A… #3

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion Understanding access control and data lake configurations in ADLS Gen2.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@ Built-in Data Roles

Storage Blob Data Owner is considered a super-user and is granted full access to all mutating operations, including setting the owner of a directory or file as well as ACLs for directories and files for which they are not the owner. Super-user access is the only authorized manner to change the owner of a resource.

> **_Note:_** RBAC assignments can take up to 5 minutes to propagate and take affect.
> **_Note:_** RBAC assignments can take up to 30 minutes to propagate and take affect.

How data lake structure relates to access control
=================================================
Expand Down