Skip to content

Commit 5bd84fa

Browse files
Merge pull request #106052 from vishalk9040/patch-1
Update data-lake-storage-access-control.md
2 parents d6d1b92 + a550a47 commit 5bd84fa

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
@@ -309,7 +309,7 @@ The owning user can change the permissions of the file to give themselves any RW
309309

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

312-
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).
312+
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.
313313

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

0 commit comments

Comments
 (0)