Azure AD PIM Role Activations Too Frequent for Same User

Alerts when Azure PIM logs sequential activation renewals for the same role by the same user.

FreeReviewedSigma · High · v5

Product: azure
Service: pim
Author: Mark Morowczynski '@markmorow', Gloria Lee, '@gleeiamglo' (SigmaHQ), DRL 1.1
Published: 2023-09-14
Updated: 2026-07-31

ATT&CK techniques

Initial Access → Defense Evasion

Recon
Resource Dev
Initial Access
- T1078Valid Accounts
Execution
Persistence
- T1078Valid Accounts
Priv Esc
- T1078Valid Accounts
Defense Evasion
- T1078Valid Accounts
Cred Access
Discovery
Lateral Movement
Collection
C2
Exfiltration
Impact

What it detects

This rule flags Azure AD Privileged Identity Management (PIM) incidents where a privilege role is activated repeatedly for the same user in a short sequence. Attackers may rely on frequent activations to obtain or extend privileged access while reducing the likelihood of standing assignments. The detection relies on PIM telemetry with a specific risk event type indicating sequential activation renewals.

Reporting behind it

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 PIM Role Activations Too Frequent for Same User

Pivot detection · T1078 · 9 related

Changelog

v5
Candidate ingested via manual entry.2026-07-31
v4
Candidate ingested via manual entry.2026-07-31
v3
Candidate ingested via manual entry.2026-07-31
v2
Candidate ingested via manual entry.2026-07-31
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.

azure-pim-role-activated-too-frequently-sequential-activation-renewals-645fd80d

title: Azure AD PIM Role Activations Too Frequent for Same User
id: 4466f17e-c405-4f2a-9286-006c0c70d55c
status: test
description: This rule flags Azure AD Privileged Identity Management (PIM) incidents where a privilege role is activated repeatedly for the same user in a short sequence. Attackers may rely on frequent activations to obtain or extend privileged access while reducing the likelihood of standing assignments. The detection relies on PIM telemetry with a specific risk event type indicating sequential activation renewals.
references:
  - https://learn.microsoft.com/en-us/entra/id-governance/privileged-identity-management/pim-how-to-configure-security-alerts#roles-are-being-activated-too-frequently
  - https://github.com/SigmaHQ/sigma/blob/master/rules/cloud/azure/privileged_identity_management/azure_pim_role_frequent_activation.yml
author: Mark Morowczynski '@markmorow', Gloria Lee, '@gleeiamglo', Huntrule Team
date: 2023-09-14
tags:
  - attack.initial-access
  - attack.stealth
  - attack.t1078
  - attack.persistence
  - attack.privilege-escalation
logsource:
  product: azure
  service: pim
detection:
  selection:
    riskEventType: sequentialActivationRenewalsAlertIncident
  condition: selection
falsepositives:
  - Investigate where if active time period for a role is set too short.
level: high
license: DRL-1.1
related:
  - id: 645fd80d-6c07-435b-9e06-7bc1b5656cba
    type: derived

Convert

This rule as a query you can run. Uses no unlock credit.

SplunkSPL