Skip to content

Lifecycle Workflow Failures (30 days)

The question it answers: Which lifecycle workflow runs and tasks failed in the last 30 days, and for which users?

Joiner, mover and leaver workflows run unattended. When a task fails - a leaver’s licences are not removed, a new starter gets no Temporary Access Pass - nobody notices until someone complains. This report lists every failed user run and the task that failed.

Where in the appEntra ID › Identity Governance & Lifecycle › Lifecycle Workflow Failures
WorkloadEntra ID
KindFindings list · dashboard tile
DataRead from Microsoft 365 when someone first opens it, then kept for the report cache lifetime (Settings > Data & cache, 1 hour unless changed).
LicenceMicrosoft Entra ID Governance.
Report id (API and MCP)entra.governance.lifecycle-workflows
ColumnKeyType
SeveritySeverityStatus
ItemCategoryText
Workflow / userSubjectLink
CheckSettingText
ValueValueText
FindingFindingText
DetailDetailText
Last runWhenDate
RunsNumberNumber

A findings list hides columns that no row fills. Severity is Critical, Serious, Warning, OK or Info; rows rated Critical, Serious or Warning need attention (Working with findings).

Licence: Microsoft Entra ID Governance.

Application permissions on the IntensiveReports app registration (all permissions):

PermissionAPIWhat it allowsNote
LifecycleWorkflows.Read.AllMicrosoft GraphRead all lifecycle workflows resources
Data sources it reads
  • GET /v1.0/identityGovernance/lifecycleWorkflows/workflows
  • GET .../workflows/{id}/runs
  • GET .../runs/{id}/userProcessingResults
  • GET .../userProcessingResults/{id}/taskProcessingResults
GET /ir-api/v1/reports/entra.governance.lifecycle-workflows?size=100

An AI assistant reads it with the MCP tool get_report and the id entra.governance.lifecycle-workflows. The client needs the Read grant for Entra ID. See Using the API.