Azure AD Kerberos Server object missing — Azure Files AADKERB stuck (urbacon.net)

Richard Hilton 5 Reputation points
2025-06-19T20:30:34.2966667+00:00

We are trying to enable Azure AD Kerberos authentication for our Storage Account:

Storage Account: fileshareurb1 (canadacentral)

Domain: urbacon.net (Hybrid joined)

DirectoryServiceOptions: AADKERB

OnPremisesSyncEnabled: Yes

AD Connect: OK

Permissions: All fixed and verified:

Replicating Directory Changes

  Replicating Directory Changes All
  
     Write userPrincipalName
     
        Write mS-DS-ConsistencyGuid
        
           (checked via PowerShell and GUI — confirmed inheritance correct)
           
           **Sync:** Full sync run several times
           
           **Federation:** No legacy federation — domain is Managed
           
           **Inheritance:** Now applied to all user objects under CN=Users and OUs
           

Issue: The required AzureADKerberosServer object is missing — verified by running:

powershell
Copy
Get-MgBetaDirectorySetting | Where-Object { $_.DisplayName -match "Kerberos" }

Result: no object found — even after 12+ hours and toggling AADKERB OFF/ON again.

Request: Please check backend state and force creation of the AzureADKerberosServer object for domain urbacon.net — so we can complete AADKERB configuration for Azure Files.

Azure Files
Azure Files
An Azure service that offers file shares in the cloud.
1,420 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Nandamuri Pranay Teja 3,610 Reputation points Microsoft External Staff Moderator
    2025-06-20T04:22:54.1066667+00:00

    Hello Richard Hilton

    Thank you for your question!

    If CheckEntraObject fails, disable and re-enable AADKERB on the storage account.

    Set-AzStorageAccount -ResourceGroupName $ResourceGroupName -Name $StorageAccountName -EnableAzureActiveDirectoryKerberosForFile $false
    Set-AzStorageAccount -ResourceGroupName $ResourceGroupName -Name $StorageAccountName -EnableAzureActiveDirectoryKerberosForFile $true
    

    If CheckRegKey fails, set the registry key. Reboot the client machine after this change.

    reg add HKLM\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parameters /v CloudKerberosTicketRetrievalEnabled /t REG_DWORD /d 1
    

    Since OnPremisesSyncEnabled is Yes and full syncs have been run, verify that the hybrid identity sync is working correctly

    • In the Microsoft Entra admin center, go to Azure AD Connect > Health and check for sync errors. Ensure the mS-DS-ConsistencyGuid and userPrincipalName attributes are syncing correctly for users.

    Check if the storage account’s service principal exists in Entra ID

    Get-MgServicePrincipal -Filter "displayName eq 'fileshareurb1'"
    

    If the AzureADKerberos object is created but authentication still fails, rotate the Kerberos key Wait a few hours for key propagation. Use -Force if rotation is needed within 24 hours.

    Set-AzureADKerberosServer -Domain $domain -UserPrincipalName $userPrincipalName -DomainCredential $domainCred -RotateServerKey
    

    Please refer to the below article on Enable Microsoft Entra Kerberos authentication for hybrid identities on Azure Files: https://learn.microsoft.com/en-us/azure/storage/files/storage-files-identity-auth-hybrid-identities-enable?tabs=azure-portal%2Cintune

    • Prerequisites: Confirm that client devices are running supported OS versions (Windows 11 Enterprise, Windows 10 Enterprise, or Windows Server 2019/2022).
    • Verify that urbacon.net is synchronized with Microsoft Entra ID using AD Connect, and OnPremisesSyncEnabled is Yes (as you confirmed).
    • Ensure the storage account (fileshareurb1) is in the same Azure region (canadacentral) as the domain’s synced identities.

    Hope the above answer helps! Please let us know do you have any further queries.


    Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members. 

     User's image


Your answer

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