|
1 | 1 | ---
|
2 | 2 | title: Control what a user can do at the directory and file level - Azure Files
|
3 |
| -description: Learn how to configure Windows ACLs for directory and file level permissions for AD DS authentication to Azure file shares, allowing you to take advantage of granular access control. |
| 3 | +description: Learn how to configure Windows ACLs for directory and file level permissions for Active Directory authentication to Azure file shares, allowing you to take advantage of granular access control. |
4 | 4 | author: khdownie
|
5 | 5 | ms.service: storage
|
6 | 6 | ms.subservice: files
|
7 | 7 | ms.topic: how-to
|
8 |
| -ms.date: 11/08/2022 |
| 8 | +ms.date: 11/09/2022 |
9 | 9 | ms.author: kendownie
|
| 10 | +ms.custom: engagement-fy23 |
10 | 11 | ---
|
11 | 12 |
|
12 |
| -# Part three: configure directory and file level permissions over SMB |
| 13 | +# Configure directory and file-level permissions over SMB |
13 | 14 |
|
14 |
| -Before you begin this article, make sure you've completed the previous article, [Assign share-level permissions to an identity](storage-files-identity-ad-ds-assign-permissions.md), to ensure that your share-level permissions are in place with Azure role-based access control (RBAC). |
| 15 | +Before you begin this article, make sure you've read [Assign share-level permissions to an identity](storage-files-identity-ad-ds-assign-permissions.md) to ensure that your share-level permissions are in place with Azure role-based access control (RBAC). |
15 | 16 |
|
16 | 17 | After you assign share-level permissions, you must first connect to the Azure file share using the storage account key and then configure Windows access control lists (ACLs), also known as NTFS permissions, at the root, directory, or file level. While share-level permissions act as a high-level gatekeeper that determines whether a user can access the share, Windows ACLs operate at a more granular level to control what operations the user can do at the directory or file level.
|
17 | 18 |
|
18 |
| -Both share-level and file/directory level permissions are enforced when a user attempts to access a file/directory, so if there's a difference between either of them, only the most restrictive one will be applied. For example, if a user has read/write access at the file level, but only read at a share level, then they can only read that file. The same would be true if it was reversed: if a user had read/write access at the share-level, but only read at the file-level, they can still only read the file. |
| 19 | +Both share-level and file/directory-level permissions are enforced when a user attempts to access a file/directory, so if there's a difference between either of them, only the most restrictive one will be applied. For example, if a user has read/write access at the file level, but only read at a share level, then they can only read that file. The same would be true if it was reversed: if a user had read/write access at the share-level, but only read at the file-level, they can still only read the file. |
19 | 20 |
|
20 | 21 | ## Applies to
|
21 | 22 | | File share type | SMB | NFS |
|
@@ -111,6 +112,4 @@ Use Windows File Explorer to grant full permission to all directories and files
|
111 | 112 |
|
112 | 113 | ## Next steps
|
113 | 114 |
|
114 |
| -Now that the feature is enabled and configured, continue to the next article to learn how to mount your Azure file share from a domain-joined VM. |
115 |
| - |
116 |
| -[Part four: mount a file share from a domain-joined VM](storage-files-identity-ad-ds-mount-file-share.md) |
| 115 | +Now that the feature is enabled and configured, you can [mount a file share from a domain-joined VM](storage-files-identity-ad-ds-mount-file-share.md). |
0 commit comments