You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/storage/files/storage-files-authorization-overview.md
+10-11Lines changed: 10 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,41 +9,40 @@ ms.author: kendownie
9
9
# Customer intent: As a cloud administrator, I want to configure authorization and access control for SMB Azure file shares, so that I can manage user permissions at both the share and directory/file levels effectively.
10
10
---
11
11
12
-
13
12
# Overview of Azure Files authorization and access control
Regardless of which identity source you choose for [identity-based authentication](storage-files-active-directory-overview.md) on your storage account, you'll need to configure authorization and access control. Azure Files enforces authorization on user access at both the share level and the directory/file levels.
16
+
Regardless of which identity source you choose for [identity-based authentication](storage-files-active-directory-overview.md) on your storage account, you need to configure authorization and access control. Azure Files enforces authorization on user access at both the share level and the directory/file level.
18
17
19
18
You can assign share-level permissions to Microsoft Entra users or groups that are managed through [Azure RBAC](/azure/role-based-access-control/overview). With Azure RBAC, the credentials you use for file access should be available or synced to Microsoft Entra ID. You can assign Azure built-in roles like **Storage File Data SMB Share Reader** to users or groups in Microsoft Entra ID to grant access to a file share.
20
19
21
-
At the directory/file level, Azure Files supports preserving, inheriting, and enforcing [Windows ACLs](/windows/win32/secauthz/access-control-lists). You can choose to keep Windows ACLs when copying data over SMB between your existing file share and your Azure file shares. Whether you plan to enforce authorization or not, you can use Azure file shares to back up ACLs along with your data.
20
+
At the directory and file level, Azure Files supports preserving, inheriting, and enforcing [Windows ACLs](/windows/win32/secauthz/access-control-lists). You can choose to keep Windows ACLs when copying data over SMB between your existing file share and your Azure file shares. Whether you plan to enforce authorization or not, you can use Azure Files to back up ACLs along with your data.
22
21
23
22
## Configure share-level permissions
24
23
25
-
Once you've enabled an identity source on your storage account, you must do one of the following to access the file share:
24
+
After you enable an identity source on your storage account, you must do one of the following to access the file share:
26
25
27
-
- Set a [default share-level permission](storage-files-identity-assign-share-level-permissions.md#share-level-permissions-for-all-authenticated-identities) that applies to all authenticated users and groups
28
-
- Assign built-in Azure RBAC roles to users and groups, or
29
-
- Configure custom roles for Microsoft Entra identities and assign access rights to file shares in your storage account.
26
+
- Set a [default share-level permission](storage-files-identity-assign-share-level-permissions.md#share-level-permissions-for-all-authenticated-identities) that applies to all authenticated users and groups.
27
+
- Assign built-in Azure RBAC roles to users and groups.
28
+
- Configure custom roles for Entra identities and assign access rights to file shares in your storage account.
30
29
31
-
The assigned share-level permission allows the granted identity to get access to the share only, nothing else, not even the root directory. You still need to separately configure directory and file-level permissions.
30
+
The assigned share-level permission grants the identity access to the share only, nothing else, not even the root directory. You still need to separately configure directory and file-level permissions.
32
31
33
32
For more information, see [Assign share-level permissions](storage-files-identity-assign-share-level-permissions.md).
34
33
35
34
> [!NOTE]
36
-
> You can't assign share-level permissions to computer accounts (machine accounts) using Azure RBAC, because computer accounts can't be synced to an identity in Microsoft Entra ID. If you want to allow a computer account to access Azure file shares using identity-based authentication, [use a default share-level permission](storage-files-identity-assign-share-level-permissions.md#share-level-permissions-for-all-authenticated-identities) or consider using a service logon account instead.
35
+
> You can't assign share-level permissions to computer accounts (machine accounts) by using Azure RBAC, because computer accounts can't sync to an identity in Microsoft Entra ID. If you want to allow a computer account to access Azure file shares by using identity-based authentication, [use a default share-level permission](storage-files-identity-assign-share-level-permissions.md#share-level-permissions-for-all-authenticated-identities) or consider using a service logon account instead.
37
36
38
37
## Configure directory and file-level permissions
39
38
40
-
Azure file shares enforce standard Windows ACLs at both the directory and file level, including the root directory. Configuration of directory or file-level permissions is supported over both SMB and REST.
39
+
Azure Files enforces standard Windows ACLs at both the directory and file level, including the root directory. You can configure directory or file-level permissions over both SMB and REST.
41
40
42
41
For more information, see [Configure directory and file-level permissions](storage-files-identity-configure-file-level-permissions.md).
43
42
44
43
### Preserve directory and file ACLs when importing data to Azure Files
45
44
46
-
Azure Files supports preserving directory or file-level ACLs when copying data to Azure file shares. You can copy ACLs on a directory or file to Azure file shares using either Azure File Sync or common file movement toolsets. For example, you can use [robocopy](/windows-server/administration/windows-commands/robocopy) with the `/copy:s` flag to copy data as well as ACLs to an Azure file share. ACLs are preserved by default, so you don't need to enable identity-based authentication on your storage account to preserve ACLs.
45
+
Azure Files supports preserving directory or file-level ACLs when copying data to Azure file shares. You can copy ACLs on a directory or file to Azure file shares by using either Azure File Sync or common file movement toolsets. For example, you can use [robocopy](/windows-server/administration/windows-commands/robocopy) with the `/copy:s` flag to copy data as well as ACLs to an Azure file share. ACLs are preserved by default, so you don't need to enable identity-based authentication on your storage account to preserve ACLs.
0 commit comments