Skip to content

Commit cb6e6a0

Browse files
authored
Update storage-files-identity-configure-file-level-permissions.md
1 parent a8346dd commit cb6e6a0

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/storage/files/storage-files-identity-configure-file-level-permissions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ Azure Files supports the full set of basic and advanced Windows ACLs.
3838
|`BUILTIN\Administrators`|Built-in security group representing administrators of the file server. This group is empty, and no one can be added to it.
3939
|`BUILTIN\Users`|Built-in security group representing users of the file server. It includes `NT AUTHORITY\Authenticated Users` by default. For a traditional file server, you can configure the membership definition per server. For Azure Files, there isn't a hosting server, hence `BUILTIN\Users` includes the same set of users as `NT AUTHORITY\Authenticated Users`.|
4040
|`NT AUTHORITY\SYSTEM`|The service account of the operating system of the file server. Such service account doesn't apply in Azure Files context. It is included in the root directory to be consistent with Windows Files Server experience for hybrid scenarios.|
41-
|`NT AUTHORITY\Authenticated Users`|All users in AD that can get a valid Kerberos token.|
41+
|`NT AUTHORITY\Authenticated Users`|All users in AD that can get a valid Kerberos ticket.|
4242
|`CREATOR OWNER`|Each object either directory or file has an owner for that object. If there are ACLs assigned to `CREATOR OWNER` on that object, then the user that is the owner of this object has the permissions to the object defined by the ACL.|
4343

4444
The following permissions are included on the root directory of a file share:

0 commit comments

Comments
 (0)