Microsoft Planner activity

Operation	Description	Sample	Rule
any	Catch-all for M365-PlannerPlan rules matching the RecordType but no specific Operation.	N	N
PlanCreated	Plan Created activity in Microsoft Planner, recorded in the Unified Audit Log (observed in first-party capture).	Y	N

any: Microsoft Planner activity (catch-all)

RecordType: PlannerPlan

Description

Catch-all for M365-PlannerPlan rules matching the RecordType but no specific Operation.

PlanCreated

RecordType: PlannerPlan

Description

Plan Created activity in Microsoft Planner, recorded in the Unified Audit Log (observed in first-party capture).

Example Audit Record #

{
  "AppAccessContext": {
    "ClientAppId": "22222222-2222-2222-2222-222222222222",
    "CorrelationId": "591d7dfe-54b1-48b8-ac52-d39120dc9813"
  },
  "ClientIP": "203.0.113.10",
  "ContainerId": "6adb895b-fa59-4898-a8ba-0c8ec2f38ac1",
  "ContainerType": 2,
  "CreationTime": "2026-07-02T02:10:43Z",
  "Id": "5892f5ab-9a5f-4969-86e0-884c51ecc10d",
  "ObjectId": "vS4pRN0kgU-rJ96he6uvYmUACinM",
  "Operation": "PlanCreated",
  "OrganizationId": "00000000-0000-0000-0000-000000000001",
  "RecordType": 188,
  "ResultStatus": "Success",
  "UserId": "adminuser@example.onmicrosoft.com",
  "UserKey": "11111111-1111-1111-1111-111111111111",
  "UserType": 2,
  "Workload": "Planner"
}

References #

M365 audit records use different field names on each surface #

The same Unified Audit Log record uses different field names on each surface. A query built for one surface can silently miss on another. These pages document the Management Activity API JSON names, the same names Search-UnifiedAuditLog and the Office 365 Management Activity API return.

Purview CSV export flattens each record to four columns (CreationDate, UserIds, Operations, AuditData). The API field names live only inside the AuditData JSON blob. Expand it with ConvertFrom-Json. The wrapper columns are renamed too: CreationDate not CreationTime, UserIds not UserId, Operations not Operation.
Sentinel's OfficeActivity table renames several fields and turns two integer enum columns into strings. The table below maps them.

API JSON (event pages)	OfficeActivity column	Note
`Id`	`OfficeId`	Renamed.
`Workload`	`OfficeWorkload`	Renamed.
`ObjectId`	`OfficeObjectId`	Renamed.
`CreationTime`	`TimeGenerated`	Renamed. OfficeActivity has no `CreationTime` column.
`SiteUrl`	`Site_Url`	Renamed (SharePoint family).
`RecordType`	`RecordType`	Same name; the Int32 enum becomes its string enum name.
`UserType`	`UserType`	Same name; the Int32 enum becomes a string.
`ClientIP`	`ClientIP`, `Client_IPAddress`	Both columns present on OfficeActivity.
`Scope`	(none)	No OfficeActivity equivalent under any name. Recover it from the API JSON or the Purview `AuditData` blob.
`Operation`, `UserId`, `ResultStatus`, `UserKey`, `AppAccessContext`, `OrganizationId`	same names	Unchanged. No `_s` / `_d` suffixes (a native table, not a custom log).

Mapping verified against the OfficeActivity table reference, the Management Activity API schema, and the Purview audit-record export format.