Windows Server 2019 does not support the standard Microsoft Entra Kerberos client flow for Azure Files; use the documented cloud-trust flow for AD-joined clients with synchronized hybrid identities, or upgrade the SMB client operating system.
Choose the supported path
- Hybrid users + AD-joined Server 2019: Configure an incoming cloud trust between AD DS and Microsoft Entra ID. Cloud trust supports Windows Server 2012 or later and is specifically intended for clients that do not satisfy the standard flow’s OS or domain requirements.^1^
- Cloud-only users: Server 2019 has no documented supported path. Move the SMB client to Windows Server 2025 with current cumulative updates.
- Standard hybrid flow without cloud trust: Upgrade Server 2019 to Windows Server 2022 or Windows Server 2025, with current cumulative updates. The client must also be Microsoft Entra joined or hybrid joined; an AD-only or Microsoft Entra Domain Services-joined client does not meet the standard-flow requirements.^2^
The missing policy on Server 2019 is therefore consistent with the support matrix—not merely an outdated Administrative Templates issue. Adding the registry value can expose the configuration behavior, but it does not make Server 2019 supported for the standard flow.
This path requires:
- Hybrid users created in AD DS and synchronized through Microsoft Entra Connect Sync or Cloud Sync.
- Server 2019 clients joined to AD.
- AD domain functional level Windows Server 2012 or later.
- A Domain Admin or Enterprise Admin account.
- A Microsoft Entra Global Administrator account.
- A forest trust; external and other trust types are unsupported.^1^
Complete the linked cloud-trust procedure in full, including enabling Microsoft Entra Kerberos on the storage account, granting admin consent, and creating/configuring the Trusted Domain Object. Those administrative steps cannot be replaced by configuring only the client GPO.
On every Server 2019 client that accesses the share:
- Open the applicable domain GPO.
- Navigate to:
Computer Configuration > Administrative Templates > System > Kerberos
- Enable Specify KDC proxy servers for Kerberos clients.
- Select Show and add:
- Value name:
KERBEROS.MICROSOFTONLINE.COM
- Value:
<https login.microsoftonline.com:443:<tenant-id>/kerberos />
Preserve the documented space after https and before the closing /, and replace <tenant-id> with the Microsoft Entra tenant ID.^1^
- Apply the policy, then refresh policy and restart the client.
Path 2: Upgrade and use the standard client flow
On a supported client OS, enable:
Computer Configuration > Administrative Templates > System > Kerberos > Allow retrieving the Azure AD Kerberos Ticket Granting Ticket during logon
Older supported Windows releases can display the policy as Allow retrieving the cloud Kerberos ticket during the logon.^2^
If the policy UI is missing on an otherwise supported OS, use the documented registry equivalent from an elevated command prompt:
reg add HKLM\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parameters ^
/v CloudKerberosTicketRetrievalEnabled /t REG_DWORD /d 1
Restart or refresh policy afterward. This registry method is an alternative configuration mechanism, not a workaround for the Server 2019 support limitation. The corresponding Policy CSP applies to Windows 11 21H2 and later.^3^
Validate the completed configuration
After signing out and back in:
dsregcmd /status
klist
dir \\<storage-account>.file.core.windows.net\<share>
klist
For the standard joined-device flow, verify that dsregcmd /status reports the expected Entra/hybrid join, AzureAdPrt : YES, and CloudTgt : YES.^4^ After accessing the UNC path, klist should show a service ticket for cifs/<storage-account>.file.core.windows.net.
Also verify these Azure Files prerequisites:
- Microsoft Entra Kerberos is the storage account’s only configured identity source.
- Kerberos is allowed in its SMB security profile.
-
WinHttpAutoProxySvc and iphlpsvc are running.
- Conditional Access does not require MFA for the storage-account application because SMB cannot complete MFA.^2^
An MFA exclusion reduces a security control. Scope any exception only to the required storage application/account and have it reviewed through the organization’s security or identity-governance process; do not disable MFA broadly.
References
- Configure a cloud trust between on-premises AD DS and Microsoft Entra ID for accessing Azure Files
- Enable Microsoft Entra Kerberos authentication for hybrid and cloud-only identities on Azure Files
- Policy CSP - Kerberos
- Microsoft Entra Kerberos FAQ