Skip to content

Commit a550a47

Browse files
authored
To clean up the ACLs, manually delete these GUID entries.
To clean up the ACLs, manually delete these GUID entries.
1 parent 3709fb5 commit a550a47

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/storage/blobs/data-lake-storage-access-control.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -308,7 +308,7 @@ The owning user can change the permissions of the file to give themselves any RW
308308

309309
### Why do I sometimes see GUIDs in ACLs?
310310

311-
A GUID is shown if the entry represents a user and that user doesn't exist in Azure AD anymore. Usually this happens when the user has left the company or if their account has been deleted in Azure AD. Additionally, service principals and security groups do not have a User Principal Name (UPN) to identify them and so they are represented by their OID attribute (a guid). A manual clean up needs to be done to remove these GUID.
311+
A GUID is shown if the entry represents a user and that user doesn't exist in Azure AD anymore. Usually this happens when the user has left the company or if their account has been deleted in Azure AD. Additionally, service principals and security groups do not have a User Principal Name (UPN) to identify them and so they are represented by their OID attribute (a guid). To clean up the ACLs, manually delete these GUID entries.
312312

313313
### How do I set ACLs correctly for a service principal?
314314

0 commit comments

Comments
 (0)