Cross‑Domain delegation failure in same forest

Jutsi Mohanmed 0 Reputation points
2026-07-30T03:46:24.2866667+00:00

Hi all

A service account was set up with constrained delegation.

The target resource sits in a different domain.

The delegation attempt keeps failing repeatedly.

This happens even though both domains share one forest.

So what resource‑based constrained delegation (RBCD) configuration is required to make cross‑domain delegation succeed in this scenario ?

Windows for business | Windows 365 Enterprise
0 comments No comments

1 answer

Sort by: Most helpful
  1. Steven Nguyen (WICLOUD CORPORATION) 415 Reputation points Microsoft External Staff Moderator
    2026-07-30T07:21:17.7666667+00:00

    Hi Jutsi Mohanmed,

    Based on your description, this is a Kerberos constrained delegation cross-domain scenario within the same forest.

    For this scenario, Resource-Based Constrained Delegation (RBCD) is typically the correct configuration model because the delegation permission is configured on the back-end/target resource account, not on the front-end service account.

    Microsoft documents that earlier constrained delegation required domain admin privileges and restricted the service account to a single domain. With the newer Kerberos constrained delegation model, delegation can be configured on the back-end service account, and that account can be in another domain.

    Recommended Action Plan:

    You can configure RBCD by running the following PowerShell commands from a Domain Controller in the target domain (Domain B), using an account with administrative privileges:

    # 1. Retrieve the Front-end Service Account object from Domain A
    $FrontendAccount = Get-ADUser -Identity "FrontEndAccountName" -Server "DomainA.com"
    # Note: If the front-end is a computer account, use Get-ADComputer instead of Get-ADUser.
    # 2. Grant the Front-end Account permission to delegate to the Target Resource in Domain B
    Set-ADComputer -Identity "TargetComputerName" -Server "DomainB.com" -PrincipalsAllowedToDelegateToAccount $FrontendAccount
    # Note: If the Target Resource runs under a specific service account instead of the computer account (Local System), use Set-ADUser instead of Set-ADComputer.
    

    Once this command successfully populates the msDS-AllowedToActOnBehalfOfOtherIdentity attribute on the target resource, the Key Distribution Center (KDC) will allow the cross-domain delegation.

    =======================

    I hope this helps address your query! If this works for you, please consider hitting "Accept Answer" so other users facing this issue can easily find the solution as a reference.

    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.