Events
May 19, 6 PM - May 23, 12 AM
Calling all developers, creators, and AI innovators to join us in Seattle @Microsoft Build May 19-22.
Register todayNote
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Regardless of which identity source you choose for identity-based authentication 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.
You can assign share-level permissions to Microsoft Entra users or groups that are managed through Azure RBAC. 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.
At the directory/file level, Azure Files supports preserving, inheriting, and enforcing Windows ACLs. 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.
| Management model | Billing model | Media tier | Redundancy | SMB | NFS |
|---|---|---|---|---|---|
| Microsoft.Storage | Provisioned v2 | HDD (standard) | Local (LRS) |  |
 |
| Microsoft.Storage | Provisioned v2 | HDD (standard) | Zone (ZRS) | |
|
| Microsoft.Storage | Provisioned v2 | HDD (standard) | Geo (GRS) | |
|
| Microsoft.Storage | Provisioned v2 | HDD (standard) | GeoZone (GZRS) | |
|
| Microsoft.Storage | Provisioned v1 | SSD (premium) | Local (LRS) | |
|
| Microsoft.Storage | Provisioned v1 | SSD (premium) | Zone (ZRS) | |
|
| Microsoft.Storage | Pay-as-you-go | HDD (standard) | Local (LRS) | |
|
| Microsoft.Storage | Pay-as-you-go | HDD (standard) | Zone (ZRS) | |
|
| Microsoft.Storage | Pay-as-you-go | HDD (standard) | Geo (GRS) | |
|
| Microsoft.Storage | Pay-as-you-go | HDD (standard) | GeoZone (GZRS) | |
|
Once you've enabled an identity source on your storage account, you must do one of the following to access the file share:
- Set a default share-level permission that applies to all authenticated users and groups
- Assign built-in Azure RBAC roles to users and groups, or
- Configure custom roles for Microsoft Entra identities and assign access rights to file shares in your storage account.
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.
Note
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 or consider using a service logon account instead.
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. Mount the target file share from your VM and configure permissions using Windows File Explorer, Windows icacls, or the Set-ACL command.
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 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.
For more information, see: