A cloud-based identity and access management service for securing user authentication and resource access
Yes, Microsoft Entra Kerberos can be enabled for Azure Files in a hybrid environment, but it should be done with a few checks first rather than treated as a no-impact toggle.
What enabling it does:
- Microsoft Entra ID acts as a cloud-based Kerberos Key Distribution Center (KDC).
- Hybrid users synced from on-prem AD DS to Microsoft Entra ID can get Kerberos tickets for Azure file shares.
- This helps users access Azure Files without requiring direct line of sight to on-prem domain controllers for authentication.
Important consequences and limits:
- Only one identity source can be enabled on a storage account for identity-based authentication with Azure Files.
- If a storage account is already configured for another Azure Files identity source, Microsoft Entra Kerberos is not an additive switch on that same account.
- Supported alternatives mentioned are on-prem AD DS or Microsoft Entra Domain Services, but the configuration steps and supported scenarios differ.
- Hybrid identity is supported.
- Accounts created in on-prem AD and synced to Microsoft Entra ID are a supported scenario.
- Cloud-only support exists for some workloads.
- Cloud-only identities can use Kerberos authentication for workloads like Azure Files.
- File and folder permission management has a dependency for hybrid identities.
- For hybrid identities, configuring Windows ACLs and directory/file-level permissions requires unimpeded network connectivity to the on-prem domain controller.
- If using File Explorer for permission configuration, the domain name and domain GUID from on-prem AD are needed.
- If a cloud trust design is being considered, only forest trusts are supported for Azure Files.
- The context does not state support details for using two separate domains beyond that note.
So the practical answer is:
- Yes, it can be turned on for Azure Files in a hybrid synced environment.
- No, it should not be turned on blindly without first confirming what identity source is already configured on the target storage account and how permissions will be managed.
Safe rollout path:
- In Azure portal, open the target storage account.
- Go to Data storage > Classic file shares.
- Open Identity-based access.
- Verify whether an identity source is already configured.
- If none is configured and Microsoft Entra Kerberos matches the requirement, select Set up under Microsoft Entra Kerberos, check the box, and save.
- If hybrid users will need directory and file-level permissions managed through Windows File Explorer, gather the on-prem AD domain name and domain GUID first by running
Get-ADDomainfrom an AD-joined client.
If using automation instead of the portal:
- Azure CLI:
az storage account update --name <storageaccountname> --resource-group <resourcegroupname> --enable-files-aadkerb true - Azure PowerShell:
Set-AzStorageAccount -ResourceGroupName <resourceGroupName> -StorageAccountName <storageAccountName> -EnableAzureActiveDirectoryKerberosForFile $true
For the two-domain concern:
- The provided material confirms hybrid identities are supported and states that only forest trusts are supported for Azure Files in cloud trust scenarios.
- It does not provide broader impact guidance for a two-domain design beyond that.
- Introduction to Microsoft Entra Kerberos
- Introduction to Microsoft Entra Kerberos
- Enable Microsoft Entra Kerberos authentication for hybrid and cloud-only identities on Azure Files
- Enable Microsoft Entra Kerberos authentication for hybrid and cloud-only identities on Azure Files
- Configure a cloud trust between on-premises AD DS and Microsoft Entra ID for accessing Azure Files