Azure AD Account Created and Deleted Shortly After Creation (Audit Logs)

Identifies successful Azure user creation and deletion in quick succession, consistent with short-lived account activity.

FreeReviewedSigma · High · v5
Product
azure
Service
auditlogs
Author
Mark Morowczynski '@markmorow', MikeDuddington, '@dudders1', Tim Shelton (SigmaHQ), DRL 1.1
Published
2022-08-11
Updated
2026-07-31

ATT&CK techniques

Initial Access → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule flags cases where Azure account lifecycle events show a user was added and then deleted successfully within a very short time window. Rapid create-and-delete activity can be used to quickly obtain access or test persistence without leaving long-lived objects. It relies on Azure audit log messages indicating successful “Add user” and “Delete user” operations.

Related detections9 linkedT1078 — drag to rearrange
Possible Next.js Middleware Auth Bypass via X-Middleware-Subrequest Header (CVE-2025-29927)
Suspicious Brutforce with Denied Access Due to Account Restrictions Policies (via security)
Suspicious Success Login Attempt on a Windows OpenSSH Server (via security)
Suspicious SQL Server - Connection Attempt Using a Disabled Account (via application)
Suspicious Lateral Movement Detection - Based on "special Groups" Feature (via security)
Suspicious Snowflake Anomalous Client Application Associated With UNC5537 (via cloud)
Malicious Network Login Performed to Multiple Targets (via security)
Malicious RDP Reconnaissance with Valid Credentials Performed on Multiple Hosts (via security)
Malicious Local Administrator Added by Atera RMM Agent
Azure AD Account Created and Deleted Shortly After Creation (Audit Logs)
Pivot detection · T1078 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.