Overview - on-premises Active Directory Domain Services authentication over SMB for Azure file shares

Azure Files supports identity-based authentication over Server Message Block (SMB) using three different methods: on-premises Active Directory Domain Services (AD DS), Azure Active Directory Domain Services (Azure AD DS), and Azure Active Directory (Azure AD) Kerberos for hybrid identities (preview). We strongly recommend that you review the How it works section to select the right AD source for authentication. The setup is different depending on the domain service you choose. This article focuses on enabling and configuring Azure AD DS for authentication with Azure file shares.

If you're new to Azure file shares, we recommend reading our planning guide before reading the following series of articles.

Applies to

File share type SMB NFS
Standard file shares (GPv2), LRS/ZRS Yes No
Standard file shares (GPv2), GRS/GZRS Yes No
Premium file shares (FileStorage), LRS/ZRS Yes No

Supported scenarios and restrictions

  • AD DS identities used for Azure Files on-premises AD DS authentication must be synced to Azure AD or use a default share-level permission. Password hash synchronization is optional.
  • Supports Azure file shares managed by Azure File Sync.
  • Supports Kerberos authentication with AD with AES 256 encryption (recommended) and RC4-HMAC. AES 128 Kerberos encryption is not yet supported.
  • Supports single sign-on experience.
  • Only supported on clients running OS versions Windows 8/Windows Server 2012 or newer.
  • Only supported against the AD forest that the storage account is registered to. You can only access Azure file shares with the AD DS credentials from a single forest by default. If you need to access your Azure file share from a different forest, make sure that you have the proper forest trust configured, see the FAQ for details.
  • Does not support authentication against computer accounts created in AD DS.
  • Does not support authentication against Network File System (NFS) file shares.
  • Does not support using CNAME to mount file shares.

When you enable AD DS for Azure file shares over SMB, your AD DS-joined machines can mount Azure file shares using your existing AD DS credentials. This capability can be enabled with an AD DS environment hosted either in on-premises machines or hosted in Azure.


To help you setup Azure Files AD authentication for some common use cases, we published two videos with step by step guidance for the following scenarios:

Replacing on-premises file servers with Azure Files (including setup on private link for files and AD authentication) Using Azure Files as the profile container for Azure Virtual Desktop (including setup on AD authentication and FSLogix configuration)
Screencast of the replacing on-premises file servers video - click to play. Screencast of the Using Azure Files as the profile container video - click to play.


Before you enable AD DS authentication for Azure file shares, make sure you've completed the following prerequisites:

  • Select or create your AD DS environment and sync it to Azure AD with Azure AD Connect.

    You can enable the feature on a new or existing on-premises AD DS environment. Identities used for access must be synced to Azure AD or use a default share-level permission. The Azure AD tenant and the file share that you're accessing must be associated with the same subscription.

  • Domain-join an on-premises machine or an Azure VM to on-premises AD DS. For information about how to domain-join, refer to Join a Computer to a Domain.

    If your machine is not domain joined to an AD DS, you may still be able to leverage AD credentials for authentication if your machine has line of sight to the AD domain controller.

  • Select or create an Azure storage account. For optimal performance, we recommend that you deploy the storage account in the same region as the client from which you plan to access the share. Then, mount the Azure file share with your storage account key. Mounting with the storage account key verifies connectivity.

    Make sure that the storage account containing your file shares isn't already configured for Azure AD DS Authentication. If Azure Files Azure AD DS authentication is enabled on the storage account, it needs to be disabled before changing to use on-premises AD DS. This implies that existing ACLs configured in Azure AD DS environment will need to be reconfigured for proper permission enforcement.

    If you experience issues in connecting to Azure Files, refer to the troubleshooting tool we published for Azure Files mounting errors on Windows.

  • Make any relevant networking configuration prior to enabling and configuring AD DS authentication to your Azure file shares. See Azure Files networking considerations for more information.

Regional availability

Azure Files authentication with AD DS is available in all Azure Public, China and Gov regions.


If you plan to enable any networking configurations on your file share, we recommend you read the networking considerations article and complete the related configuration before enabling AD DS authentication.

Enabling AD DS authentication for your Azure file shares allows you to authenticate to your Azure file shares with your on-premises AD DS credentials. Further, it allows you to better manage your permissions to allow granular access control. Doing this requires synching identities from on-premises AD DS to Azure AD with AD Connect. You control the share level access with identities synced to Azure AD while managing file/share level access with on-premises AD DS credentials.

Next, follow the steps below to set up Azure Files for AD DS Authentication:

  1. Part one: enable AD DS authentication on your storage account

  2. Part two: assign access permissions for a share to the Azure AD identity (a user, group, or service principal) that is in sync with the target AD identity

  3. Part three: configure Windows ACLs over SMB for directories and files

  4. Part four: mount an Azure file share to a VM joined to your AD DS

  5. Update the password of your storage account identity in AD DS

The following diagram illustrates the end-to-end workflow for enabling Azure AD authentication over SMB for Azure file shares.

Files AD workflow diagram

Identities used to access Azure file shares must be synced to Azure AD to enforce share-level file permissions through the Azure role-based access control (Azure RBAC) model. Alternatively, you can use a default share-level permission. Windows-style DACLs on files/directories carried over from existing file servers will be preserved and enforced. This offers seamless integration with your enterprise AD DS environment. As you replace on-premises file servers with Azure file shares, existing users can access Azure file shares from their current clients with a single sign-on experience, without any change to the credentials in use.

Next steps

To enable on-premises AD DS authentication for your Azure file share, continue to the next article:

Part one: enable AD DS authentication for your account