WHfB Hybrid Cloud Kerberos Trust Configuration Error

Chanuka Francis 361 Reputation points
2025-02-18T08:44:28.3433333+00:00

I'm encountering the following error while configuring cloud trust.

Set-AzureADKerberosServer : Failed to create Microsoft Entra ID Kerberos Server: Failed to set directory ACLs on object: CN=krbtgt_AzureAD,CN=Users,DC=Users,DC=###########

Could you assist me with this?

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
13,729 questions
Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
23,426 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Kancharla Saiteja 945 Reputation points Microsoft Vendor
    2025-02-19T09:51:18.96+00:00

    Hi Chanuka Francis,

    Thank you for posting your query on Microsoft Q&A. I am Saiteja from Q&A will be assisting you with your query.

    Based on your query, I understand your configuration has failed at the initial stage of creating Kerberos server object.

    As per the error, I see there is a failure with authentication to create an object in On-premise AD. I would like to provide you the two supported scenarios before we go into the configuration:

    • Cloud resources such as Microsoft 365 and other Security Assertion Markup Language (SAML)-enabled applications.
    • On-premises resources, and Windows-integrated authentication to websites. The resources can include websites and SharePoint sites that require IIS authentication and/or resources that use NTLM authentication.

    Before starting the configuration, make sure you have 2016 or 2019 servers, and you need to enable TLS1.2 in it from PowerShell as administrator using the following command: [Net.ServicePointManager]::SecurityProtocol = [Net.ServicePointManager]::SecurityProtocol -bor [Net.SecurityProtocolType]::Tls12

    All the required PORTS for NTLM, LDAP and Kerberos should be open in your DC. While performing this operation Entra reaches your DC to create a Kerberos server object which needs an internet connectivity. Kindly make sure to have internet accessible for domain controller.

    Network security: Configure encryption types allowed for Kerberos policy enabled with AES256_HMAC_SHA1 on your domain controller. You can refer this document for configuration.

    If you would like to use $domaincred make sure the user is associated with Domain admin group and Enterprise admin group. If you would like to use $CloudCred the user should be hybrid administrator or synchronized user with Global admin role with following attributes populated in Entra from AD connect:

    • onPremisesSamAccountName (accountName in Microsoft Entra Connect)
    • onPremisesDomainName (domainFQDN in Microsoft Entra Connect)
    • onPremisesSecurityIdentifier (objectSID in Microsoft Entra Connect)

    Here is the Microsoft document that refers to perform the configuration based on the above pre checks: https://learn.microsoft.com/en-us/entra/identity/authentication/howto-authentication-passwordless-security-key-on-premises#install-the-azureadhybridauthenticationmanagement-module

    Note: If you're working on a domain-joined machine with an account that has domain administrator privileges, you can skip the "-DomainCredential" parameter. If the "-DomainCredential" parameter isn't provided, the current Windows login credential is used to access your on-premises Active Directory Domain Controller.

    I hope this information is helpful. Please feel free to reach out if you have any further questions.

    If the answer is helpful, please click "Accept Answer" and kindly "upvote it". If you have extra questions about this answer, please click "Comment".


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.