You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These attributes **are not** automatically populated using such synchronization methods such as Azure AD Connect or Azure AD Connect cloud sync.
29
-
30
28
> [!NOTE]
31
29
> Currently, automatic synchronization of the employeeLeaveDateTime attribute for HR Inbound scenarios is not available. To take advantaged of leaver scenarios, you can set the employeeLeaveDateTime manually. Manually setting the attribute can be done in the portal or with Graph. For more information see [User profile in Azure](../fundamentals/active-directory-users-profile-azure-portal.md) and [Update user](/graph/api/user-update?view=graph-rest-beta&tabs=http).
description: Information about audit logs with Lifecycle Workflows
4
+
author: owinfreyATL
5
+
ms.author: owinfrey
6
+
manager: amycolannino
7
+
ms.service: active-directory
8
+
ms.workload: identity
9
+
ms.topic: conceptual
10
+
ms.date: 08/01/2022
11
+
ms.custom: template-concept
12
+
---
13
+
14
+
# Auditing Lifecycle Workflows
15
+
16
+
Workflows created using Lifecycle Workflows allow for the automation of lifecycle task for users no matter where they fall in the Joiner-Mover-Leaver (JML) model of their identity lifecycle in your organization. Making sure workflows are processed correctly is an important part of an organization's lifecycle management process. Workflows that aren't processed correctly can lead to many issues in terms of security and compliance. With audit logs, every action that Lifecycle Workflows complete over a time-frame up to 30 days are recorded.
17
+
18
+
## Audit Logs
19
+
20
+
Every time a workflow is processed, an event is logged. These events are stored in the **Audit Logs** section, and can be used to gain information about workflows for historical, and auditing, purposes.
21
+
22
+
:::image type="content" source="media/lifecycle-workflow-audits/audit-logs-concept.png" alt-text="Screenshot of a workflow audit log.":::
23
+
24
+
On the **Audit Log** page you're presented a sequential list, by date, of every action Lifecycle Workflows has taken. From this information you're able to filter based on the following parameters:
25
+
26
+
|Filter |Description |
27
+
|---------|---------|
28
+
|Date | You can filter a specific range for the audit logs from as short as 24 hours up to 30 days. |
29
+
|Date option | You can filter by your tenant's local time, or by UTC. |
30
+
|Service | The Lifecycle Workflow service. |
31
+
|Category | Categories of the event being logged. Separated into <br><br> **All**- All events logged by Lifecycle Workflows.<br><br> **TaskManagement**- Task specific related events logged by Lifecycle Workflows. <br><br> **WorkflowManagement**- Events dealing with the workflow itself. |
32
+
|Activity | You can filter based on specific activities, which are based on categories. |
33
+
34
+
After filtering this information, you're also able to see other information in the log such as:
35
+
36
+
-**Status**: Whether or not the logged event was successful or not.
37
+
-**Status Reason**: If the event failed, a reason is given why.
38
+
-**Target(s)**: Who the logged event ran for. Information given as their Azure Active Directory object ID.
39
+
-**Initiated by (actor)**: Who did the event being logged. Information given by the user name.
Copy file name to clipboardExpand all lines: articles/active-directory/governance/lifecycle-workflow-history.md
+14-34Lines changed: 14 additions & 34 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,37 +16,11 @@ ms.custom: template-concept
16
16
17
17
18
18
19
-
Workflows created using Lifecycle Workflows allow for the automation of lifecycle task for users no matter where they fall in the Joiner-Mover-Leaver (JML) model of their identity lifecycle in your organization. Making sure workflows are processed correctly is an important part of an organization's lifecycle management process. Workflows that aren't processed correctly can lead to many issues in terms of security and compliance. With Audit logs every action that Lifecycle Workflows complete are recorded. With history features, Lifecycle Workflows allow you to specify workflow events based on user, runs, or task summaries. This reporting feature allows you to quickly see what ran for who, and rather or not it was successful. In this article you'll learn the difference between auditing logs and 3 different type of history summaries you can query with Lifecycle Workflows. You'll also learn when you would use each when getting more information about how your workflows were utilized for users in your organization.
20
-
21
-
22
-
23
-
## Audit Logs
24
-
25
-
Every time a workflow is processed, an event is logged. These events are stored in the **Audit Logs** section, and can be used to gain information about workflows for historical, and auditing, purposes.
26
-
27
-
:::image type="content" source="media/lifecycle-workflow-history/audit-logs-concept.png" alt-text="Screenshot of a workflow audit log.":::
28
-
29
-
On the **Audit Log** page you're presented a sequential list, by date, of every action Lifecycle Workflows has taken. From this information you're able to filter based on the following parameters:
30
-
31
-
32
-
|Filter |Description |
33
-
|---------|---------|
34
-
|Date | You can filter a specific range for the audit logs from as short as 24 hours up to 30 days. |
35
-
|Date option | You can filter by your tenant's local time, or by UTC. |
36
-
|Service | The Lifecycle Workflow service. |
37
-
|Category | Categories of the event being logged. Separated into <br><br> **All**- All events logged by Lifecycle Workflows.<br><br> **TaskManagement**- Task specific related events logged by Lifecycle Workflows. <br><br> **WorkflowManagement**- Events dealing with the workflow itself. |
38
-
|Activity | You can filter based on specific activities, which are based on categories. |
39
-
40
-
After filtering this information, you're also able to see other information in the log such as:
41
-
42
-
-**Status**: Whether or not the logged event was successful or not.
43
-
-**Status Reason**: If the event failed, a reason is given why.
44
-
-**Target(s)**: Who the logged event ran for. Information given as their Azure Active Directory object ID.
45
-
-**Initiated by (actor)**: Who did the event being logged. Information given by the user name.
19
+
Workflows created using Lifecycle Workflows allow for the automation of lifecycle task for users no matter where they fall in the Joiner-Mover-Leaver (JML) model of their identity lifecycle in your organization. Making sure workflows are processed correctly is an important part of an organization's lifecycle management process. Workflows that aren't processed correctly can lead to many issues in terms of security and compliance. With Lifecycle Workflow's history features, you can specify which workflow events you want to view a history of based on user, runs, or task summaries. This reporting feature allows you to quickly see what ran for who, and rather or not it was successful. Along with the summaries in these specific areas, you're also able to view detailed information about each specific event recorded in their respective summary section. In this article you'll learn the difference between the three different type of history summaries, and details, you can query with Lifecycle Workflows. You'll also learn when you would use each when getting more information about how your workflows were utilized for users in your organization. For detailed information about every action Lifecycle Workflows take, see: [Auditing Lifecycle Workflows](lifecycle-workflow-audits.md).
46
20
47
21
## Lifecycle Workflow History Summaries
48
22
49
-
While the large set of information contained in audit logs can be useful for compliance reasons, for regular administration use it might be too much information. To make this large set of information processed easier to read, Lifecycle Workflows provide summaries for quick use. You can view these history summaries in three ways:
23
+
Lifecycle Workflows introduce a history feature based on summaries and details. These history summaries allow you to quickly get information about for who a workflow ran, and whether or not this run was successful or not. This is valuable because the large set of information given by audit logs might become too numerous to be efficiently used. To make a large set of information processed easier to read, Lifecycle Workflows provide summaries for quick use. You can view these history summaries in three ways:
50
24
51
25
-**Users summary**: Shows a summary of users processed by a workflow, and which tasks failed, successfully, and totally ran for each specific user.
52
26
-**Runs summary**: Shows a summary of workflow runs in terms of the workflow. Successful, failed, and total task information when workflow runs are noted.
@@ -61,7 +35,7 @@ User summaries allow you to view workflow information through the lens of users
61
35
:::image type="content" source="media/lifecycle-workflow-history/users-summary-concept.png" alt-text="Screenshot of a workflow user summary.":::
62
36
63
37
64
-
Within the user summary you're able to find the following information:
38
+
Within the user summary, you're able to find the following information:
65
39
66
40
67
41
|Parameter |Description |
@@ -72,8 +46,9 @@ Within the user summary you're able to find the following information:
72
46
|Total tasks | The total number of tasks processed for users in a workflow during the selected time frame. |
73
47
|Failed tasks | The total number of failed tasks processed for users in a workflow during the selected time frame. |
74
48
49
+
### User history details
75
50
76
-
User summaries allow you to filter based on:
51
+
User detailed history information allows you to filter for specific information based on:
77
52
78
53
-**Date**: You can filter a specific range from as short as 24 hours up to 30 days of when workflow ran.
79
54
-**Status**: You can filter a specific status of the user processed. The supported statuses are: **Completed**, **In Progress**, **Queued**, **Canceled**, **Completed with errors**, and **Failed**.
@@ -89,7 +64,7 @@ Runs summaries allow you to view workflow information through the lens of its ru
89
64
90
65
:::image type="content" source="media/lifecycle-workflow-history/runs-status-concept.png" alt-text="Screenshot of a workflow runs summary.":::
91
66
92
-
Within the runs summary you're able to find the following information:
67
+
Within the runs summary, you're able to find the following information:
93
68
94
69
95
70
|Parameter |Description |
@@ -99,7 +74,9 @@ Within the runs summary you're able to find the following information:
99
74
|Failed | Workflows that failed to run. |
100
75
|Failed tasks | Workflows that ran with failed tasks. |
101
76
102
-
Runs summaries allow you to filter based on:
77
+
### Runs history details
78
+
79
+
Runs detailed history information allows you to filter for specific information based on:
103
80
104
81
-**Date**: You can filter a specific range from as short as 24 hours up to 30 days of when workflow ran.
105
82
-**Status**: You can filter a specific status of the workflow run. The supported statuses are: **Completed**, **In Progress**, **Queued**, **Canceled**, **Completed with errors**, and **Failed**.
@@ -115,7 +92,7 @@ Task summaries allow you to view workflow information through the lens of its ta
115
92
116
93
:::image type="content" source="media/lifecycle-workflow-history/task-summary-concept.png" alt-text="Screenshot of a workflow task summary.":::
117
94
118
-
Within the tasks summary you're able to find the following information:
95
+
Within the tasks summary, you're able to find the following information:
119
96
120
97
121
98
|Parameter |Description |
@@ -125,7 +102,10 @@ Within the tasks summary you're able to find the following information:
125
102
|Failed | The number of failed processed tasks by a workflow. |
126
103
|Unprocessed | The number of unprocessed tasks by a workflow. |
127
104
128
-
Task summaries allow you to filter based on:
105
+
106
+
### Task history details
107
+
108
+
Task detailed history information allows you to filter for specific information based on:
129
109
130
110
-**Date**: You can filter a specific range from as short as 24 hours up to 30 days of when workflow ran.
131
111
-**Status**: You can filter a specific status of the workflow run. The supported statuses are: **Completed**, **In Progress**, **Queued**, **Canceled**, **Completed with errors**, and **Failed**.
0 commit comments