From d1c809e86c6d6c1011510fad54beb82406923406 Mon Sep 17 00:00:00 2001
From: Herbert Mauerer <41573578+HerbertMauerer@users.noreply.github.com>
Date: Tue, 3 Feb 2026 08:57:10 +0100
Subject: [PATCH] Update documentation for
 -PrincipalsAllowedToDelegateToAccount

Clarify usage of Set-ADComputer for principals delegation.
---
 docset/winserver2025-ps/ActiveDirectory/Set-ADComputer.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docset/winserver2025-ps/ActiveDirectory/Set-ADComputer.md b/docset/winserver2025-ps/ActiveDirectory/Set-ADComputer.md
index 7ab7c4c450..4ccbdd10a9 100644
--- a/docset/winserver2025-ps/ActiveDirectory/Set-ADComputer.md
+++ b/docset/winserver2025-ps/ActiveDirectory/Set-ADComputer.md
@@ -816,7 +816,7 @@ Accept wildcard characters: False
 Specifies the accounts which can act on the behalf of users to services running as this computer account.
 This parameter sets the **msDS-AllowedToActOnBehalfOfOtherIdentity** attribute of a computer account object.
 
-`Running Set-ADComputer without specifying the first principal will cause it to get overridden`
+You can specify the Distinguished Name of an account when it is from the same domain as the account in focus. When you want a security principal from another domain, you need to construct an ADPrincipal object with the desired account, for example using Get-ADGroup.
 
 ```yaml
 Type: ADPrincipal[]