Implement Microsoft Kerberos for Azure Files - Kerberos Group Policy Issue

Nekabari Yobo 0 Reputation points
2026-11-13T18:49:40.1966667+00:00

I am trying to implement Microsoft Kerberos for Azure file share, but after working with Windows and Azure Support teams over a month, I was told that it is a blocker related to the Microsoft Entra Kerberos authentication prerequisites in the client environment. Specifically, the required Group Policy setting for retrieving the Microsoft Entra Kerberos Ticket Granting Ticket (TGT) is currently not available in the environment.

Microsoft's response:

"We have also internally checked this behavior with our Windows team. Based on our internal validation, we recommend verifying the Windows/Group Policy configuration in your environment and ensuring that the required Microsoft Entra Kerberos policy is available and enabled on the affected client machines." - However, the policies are not available on the server, the server is running Windows Server 2019.

Could this be an OS version-specific issue or what am we missing? This issue is affecting implementation deadlines, please assist.

Azure Files
Azure Files

An Azure service that offers file shares in the cloud.

0 comments No comments

3 answers

Sort by: Oldest
  1. AI answer

    2026-11-13T18:51:24.86+00:00

    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.

    Path 1: Keep Server 2019 and configure cloud trust

    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:

    1. Open the applicable domain GPO.
    2. Navigate to: Computer Configuration > Administrative Templates > System > Kerberos
    3. Enable Specify KDC proxy servers for Kerberos clients.
    4. 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^
    5. 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

    1. Configure a cloud trust between on-premises AD DS and Microsoft Entra ID for accessing Azure Files
    2. Enable Microsoft Entra Kerberos authentication for hybrid and cloud-only identities on Azure Files
    3. Policy CSP - Kerberos
    4. Microsoft Entra Kerberos FAQ
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Rukshan edirisinghe 2,935 Reputation points
    2026-11-15T03:47:54.9966667+00:00

    Hi @Nekabari Yobo

    Yes, it's the OS version. Windows Server 2019 isn't a supported client for Microsoft Entra Kerberos with Azure Files, which is why the "Allow retrieving the Azure AD Kerberos Ticket Granting Ticket during logon" policy never shows up there. Newer Windows versions ship that policy, 2019 doesn't, so no GPO change on that box will fix it.

    What gets you unblocked:

    1. Mount the share from a supported client instead: Windows Server 2022 or 2025, Windows 11, or Windows 10 version 2004 or later, all with the latest cumulative updates.
    2. On that client, enable the policy under Computer Configuration > Administrative Templates > System > Kerberos.
    3. Run gpupdate /force, sign in again with a hybrid user, then run klist get cifs/<storageaccount>.file.core.windows.net to confirm a ticket comes back.

    If the 2019 server has to stay and it's domain-joined with synced users, the other route is the cloud trust setup, which supports older clients.

    Is the 2019 machine the one that has to mount the share, or could it run from a newer server?

    If my response resolved your issue, please consider accepting it as the answer. If the issue persists, let me know and I'll be happy to continue helping.

    Reference:

    Was this answer helpful?


  3. Nekabari Yobo 0 Reputation points
    2026-11-16T19:48:05.3933333+00:00

    Interesting. Well, I am actually on a server that is running Windows Server 2022 Datacenter, and it is not listing the required Kerberos policies. Please see the screenshots below and update me on what is missing. Thanks!

    User's image

    User's image

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.