Microsoft Defender for Identity
Identity protection

Manage Action Accounts

In brief

The page date and wording were updated to advise avoiding the same managed-action gMSA account on servers other than domain controllers. The text explains that a compromised server could expose the password and enable password changes or account disabling.

What Defender admins need to know

Review where the managed-action gMSA account is used, since reuse on other servers increases compromise impact.

Summaries are generated from the documentation change itself.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

Best practices for action accounts

We recommend that you avoidAvoid using the same gMSA account you configured for Defender for Identity managed actions on servers other than domain controllers. If you use the same account on another server and that server is compromised, an attacker could retrieve the password for the account and gain the ability to change passwords and disable accounts.

We also recommend that you avoid using the same account as both the Directory Service account and the Manage Action account. Separating these roles is important because the Directory Service account requires only read-only permissions to Active Directory, and the Manage Action account needs write permissions on user accounts.