Skip to content

Windows Event ID 4722: A user account was enabled

Written when a disabled user account is enabled. It captures re-enabling of dormant or former-employee accounts, detecting groundwork for misuse.

Overview

The subcategory is Audit User Account Management. It is generated when an account is switched to enabled. It appears right after a new creation 4720 or when a previously disabled account is reused.

How it is triggered

  • Enabling via net user /active:yes, account enabling in AD, Enable-ADAccount, and so on.

Security review points

  • Enabling a former-employee, dormant, or normally-unused account suggests misuse or takeover of an ownerless account. Re-enabling an administrator-level account in particular is notable.
  • An attacker may enable an account they had kept disabled to avoid detection, at attack time. Together with creation 4720 and disabling 4725, track the account’s state changes.

Notes for log review

  • It also occurs during legitimate operations (return to work, recovery from suspension). Match against the target account’s profile (dormancy period, last logon).
  • Monitor enabling of high-privilege and service accounts at high priority.

MITRE ATT&CK mapping

TechniqueTacticWhat this event shows
T1078 Valid AccountsStealth, Persistence, Privilege Escalation, Initial AccessRe-enabling and abusing departed or dormant accounts

Mapping as of ATT&CK v19.2. To search by technique, see the ATT&CK reverse lookup.

Detection rules

Microsoft Sentinel has 2 public detection rules that use this event ID as a condition.

RuleTypeSeverity
User account enabled and disabled within 10 minsSentinel analytics ruleMedium
AD user enabled and password not set within 48 hoursSentinel analytics ruleLow

Rules are collected from SigmaHQ r2026-07-01 and from Azure-Sentinel as of 2026-10-09, limited to those whose conditions include this event ID. Sentinel rules are limited to those that query the SecurityEvent or WindowsEvent table. “Threat-specific” rules target a particular threat group or malware, and “needs setup” rules require values for your environment. Severity is the value each rule’s author assigned.

Key fields

FieldMeaning
Target Account\Account NameThe enabled account
Subject\Account NameThe subject that performed the operation

References