Power Automate - Departing employee flow activity

Status: available
Severity: high
Time window: 7d
Group by: ActorName, UserPrincipalName
Source: github.com/Azure/Azure-Sentinel

Identifies instances where an employee who has been notified or is already terminated, on the TerminatedEmployees watchlist, creates or modifies a Power Automate flow.

MITRE ATT&CK coverage

Tactic	Techniques
Exfiltration	`T1567` Exfiltration Over Web Service
Impact	`T1485` Data Destruction, `T1491` Defacement
Impact	`T0813` Denial of Control, `T0826` Loss of Availability, `T0879` Damage to Property

Rule body kusto

id: b1e11b8c-545a-4dea-a912-0008e160d183
kind: Scheduled
name: Power Automate - Departing employee flow activity
description: Identifies instances where an employee who has been notified or is already
  terminated, on the TerminatedEmployees watchlist, creates or modifies a Power Automate
  flow.
severity: High
status: Available
requiredDataConnectors:
  - connectorId: PowerAutomate
    dataTypes:
      - PowerAutomateActivity
queryFrequency: 1h
queryPeriod: 7d
triggerOperator: gt
triggerThreshold: 0
tactics:
  - Exfiltration
  - Impact
relevantTechniques:
  - T1567
  - T1485
  - T1491
  - T0813
  - T0879
  - T0826
query: |
  let query_frequency = 1h;
  PowerAutomateActivity
  | where TimeGenerated >= ago(query_frequency)
  | where EventOriginalType in ("CreateFlow", "EditFlow")
  | join kind=inner (MSBizAppsTerminatedEmployees()) on $left.ActorName == $right.UserPrincipalName
  | extend path = parse_url(FlowDetailsUrl).Path
  | extend EnvironmentId = tostring(split(path, "/")[2])
  | extend FlowId = tostring(split(path, "/")[-2])
  | extend
      AccountName = tostring(split(ActorName, "@")[0]),
      UPNSuffix = tostring(split(ActorName, "@")[1]),
      PowerAutomateAppId = 27592,
      CloudAppId = 32780
  | project
      TimeGenerated,
      EventOriginalType,
      ActorName,
      EnvironmentId,
      AccountName,
      UPNSuffix,
      PowerAutomateAppId,
      CloudAppId,
      FlowId
eventGroupingSettings:
  aggregationKind: SingleAlert
entityMappings:
  - entityType: Account
    fieldMappings:
      - identifier: Name
        columnName: AccountName
      - identifier: UPNSuffix
        columnName: UPNSuffix
  - entityType: CloudApplication
    fieldMappings:
      - identifier: AppId
        columnName: PowerAutomateAppId
alertDetailsOverride:
  alertDisplayNameFormat: PowerAutomate - Terminated user {{EventOriginalType}} detected
  alertDescriptionFormat: '{{ActorName}} is on the terminated employees watchlist
    and carried out {{EventOriginalType}} in environment id {{EnvironmentId}}.'
customDetails:
  Environment: EnvironmentId
  FlowDetails: FlowId
version: 3.2.0

Stages and Predicates

Parameters

let query_frequency = 1h;

Stage 1: `source`

PowerAutomateActivity

Stage 2: `where`

| where TimeGenerated >= ago(query_frequency)

Stage 3: `where`

| where EventOriginalType in ("CreateFlow", "EditFlow")

Stage 4: `join`

| join kind=inner (MSBizAppsTerminatedEmployees()) on $left.ActorName == $right.UserPrincipalName

Stage 5: `extend` (4 consecutive steps)

| extend path = parse_url(FlowDetailsUrl).Path
| extend EnvironmentId = tostring(split(path, "/")[2])
| extend FlowId = tostring(split(path, "/")[-2])
| extend
    AccountName = tostring(split(ActorName, "@")[0]),
    UPNSuffix = tostring(split(ActorName, "@")[1]),
    PowerAutomateAppId = 27592,
    CloudAppId = 32780

Stage 6: `project`

| project
    TimeGenerated,
    EventOriginalType,
    ActorName,
    EnvironmentId,
    AccountName,
    UPNSuffix,
    PowerAutomateAppId,
    CloudAppId,
    FlowId

Indicators

Each row is a field, operator, and value that the rule matches. The corpus column counts how many other rules in the catalog look for the same combination: high numbers point to widely-used, community-vetted indicators. Blank or 1 shows that the indicator is specific to this rule.

Field	Kind	Values
`EventOriginalType`	in	`CreateFlow` transforms: `cased` `EditFlow` transforms: `cased`

Output fields

Fields the rule emits when it matches. Chronicle authors list these in the outcome block; they appear on the detection and $risk_score drives alerting. Sentinel / Defender XDR rules build them up through project / summarize / extend stages. Sentinel maps these into alert fields via entityMappings and customDetails; Defender XDR custom detections surface them as alert fields directly.

Field	Source
`AccountName`	`project`
`ActorName`	`project`
`CloudAppId`	`project`
`EnvironmentId`	`project`
`EventOriginalType`	`project`
`FlowId`	`project`
`PowerAutomateAppId`	`project`
`TimeGenerated`	`project`
`UPNSuffix`	`project`

`j` / `k`	Scroll down / up
`d` / `u`	Half-page down / up
`gg` / `G`	Top / bottom
`h` / `l`	History back / forward
`f`	Follow link (`Shift` = new tab)
`/`	Focus search
`?`	Toggle this help
`↑` / `↓`	Navigate search results
`Enter`	Open highlighted result
`Esc`	Close results / dialog

`type:`	`events` / `rules` / `providers`
`vendor:`	`sigma` / `elastic` / `splunk` / `kusto` / `chronicle` (vendor name alone also works: `sigma:`, `kql:`, `secops:`…)
`tactic:`	TA-id, slug, or name: `credential_access`, `TA0006`
`technique:`	technique or sub-technique ID: `T1003`, `T1003.001` (alias `tech:`)
`severity:`	`critical` / `high` / `medium` / `low` / `informational` (alias `sev:`)
`risk_score`	Numeric comparison on the Elastic risk score (0 to 100): `risk_score>50`, `risk_score<=20`, `risk_score=99` (alias `risk`; Elastic rules only)
`stages:`	Rules with exactly N pipeline stages
`correlation:`	`single_event` / `sequence` / `alternatives` / `alternatives_cross_log` / `all_required` / `correlated`
`with:`	Co-occurrence event-id; stacks (`with:4624 with:4769`) to require all, while a comma list in one occurrence (`with:4624,4769`) is an either-or group. Implies multi-event
`like:`	Structural neighbors of a rule slug (equivalents + subsumption stricter / broader): `like:comsvcs_lsass_memory_dump-splunk-sysmon`
`groupby:`	Entity-grouping substring match against `group_by_keys`: `groupby:user`, `groupby:host`
`uses:`	Rules whose predicate tree touches the field (any kind, any value): `uses:CommandLine`
`excludes:`	Rules with top-level `not()` clauses on the field (FP whitelists): `excludes:ParentImage`
`field:` / `value:`	Predicate search; narrows rule cards to those with a matching leaf and drives the indicator tier. Unquoted = substring, wildcards allowed (`value:mimikatz`)
`indicator:`	Shorthand for `field:F value:V`: `indicator:Image=*\powershell.exe`
`kind:`	Filter by predicate kind. Narrows rule cards to those carrying a matching predicate leaf (`vendor:elastic kind:cidr_match`) and drives the indicator tier: `contains` / `starts_with` / `ends_with` / `regex` / `cidr` / `eq` / `in` … (operator aliases `op:`/`match:`)
`has:` / `no:`	`sample`, `field`, `notes`, `refs`, `trace`, `thirdparty`, `rule`, `pattern`, `timewindow`, `threshold`, `newterms`, `sigma`/`elastic`/`splunk`/`kusto`/`chronicle`
`-op:val`	Exclude matches; works on most operators but not `type:`/`like:`/`has:`/`no:` (use `no:<flag>` to exclude a rule flag): `tactic:execution -vendor:splunk`. Standalone `-kind:`/`-field:`/`-value:` drop every rule carrying a matching predicate leaf (`type:rules -kind:is_null`)
`field:"…"` / `value:"…"`	Quoted value = anchored exact match (also allows spaces): `value:"net user"`
`a,b`	Comma = OR inside one operator (`vendor:sigma,elastic`, `severity:high,critical`); repeating a facet merges the same way. `field:`/`value:` never split (literal commas)
`vendors:` / `stage:`	Singular and plural spellings fold to the canonical operator and value: `tactics:` = `tactic:`, `type:event` = `type:events`, `correlation:sequences` = `correlation:sequence`, `has:thresholds` = `has:threshold`
`"quoted phrase"`	Exact-match a multi-word phrase (free text)

Power Automate - Departing employee flow activity

MITRE ATT&CK coverage

Rule body kusto

Stages and Predicates

Parameters

Stage 1: `source`

Stage 2: `where`

Stage 3: `where`

Stage 4: `join`

Stage 5: `extend` (4 consecutive steps)

Stage 6: `project`

Indicators

Output fields

Keyboard shortcuts

Search operators

Power Automate - Departing employee flow activity

MITRE ATT&CK coverage

Rule body kusto

Stages and Predicates

Parameters

Stage 1: source

Stage 2: where

Stage 3: where

Stage 4: join

Stage 5: extend (4 consecutive steps)

Stage 6: project

Indicators

Output fields

Stage 1: `source`

Stage 2: `where`

Stage 3: `where`

Stage 4: `join`

Stage 5: `extend` (4 consecutive steps)

Stage 6: `project`