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
Copy file name to clipboardExpand all lines: articles/active-directory/reports-monitoring/concept-provisioning-logs.md
+32-18Lines changed: 32 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -86,23 +86,31 @@ Select an item in the list view to get more detailed information.
86
86
87
87
## Filter provisioning activities
88
88
89
-
To narrow down the reported data to a level that works for you, you can filter the provisioning data using the following default fields. Note that the values in the filters are dynamically populated based on your tenant. If, for example, you don't have any create events in your tenant, there won't be a filter option for create.
89
+
You can filter your provisioning data. Some filter values are dynamically populated based on your tenant. If, for example, you don't have any create events in your tenant, there won't be a filter option for create.
90
+
In the default view, you can select the following filters:
The **Identity** filter enables you to specify the name or the identity that you care about. This identity could be a user, group, role, or other object. You can search by the name or ID of the object. The ID varies by scenario. For example, when provisioning an object from Azure AD to SalesForce, the Source ID is the object ID of the user in Azure AD while the TargetID is the ID of the user in Salesforce. When provisioning from Workday to Active Directory, the Source ID is the Workday worker employee ID. Note that the Name of the user may not always be present in the Identity column. There will always be one ID.
102
101
103
-
The **Source System** filter enables you to specify where the identity is getting provisioned from. For example, when provisioning an object from Azure AD to ServiceNow, the Source system is Azure AD.
104
102
105
-
The **Target System** filter enables you to specify where the identity is getting provisioned to. For example, when provisioning an object from Azure AD to ServiceNow, the Target System is ServiceNow.
103
+
The **Date** filter enables to you to define a timeframe for the returned data.
104
+
Possible values are:
105
+
106
+
- 1 month
107
+
- 7 days
108
+
- 30 days
109
+
- 24 hours
110
+
- Custom time interval
111
+
112
+
When you select a custom time frame, you can configure a start date and an end date.
113
+
106
114
107
115
The **Status** filter enables you to select:
108
116
@@ -111,6 +119,8 @@ The **Status** filter enables you to select:
111
119
- Failure
112
120
- Skipped
113
121
122
+
123
+
114
124
The **Action** filter enables you to filter the:
115
125
116
126
- Create
@@ -119,19 +129,18 @@ The **Action** filter enables you to filter the:
119
129
- Disable
120
130
- Other
121
131
122
-
The **Date** filter enables to you to define a timeframe for the returned data.
123
-
Possible values are:
132
+
In addition, to the filters of the default view, you can also set the following filters:
124
133
125
-
- 1 month
126
-
- 7 days
127
-
- 30 days
128
-
- 24 hours
129
-
- Custom time interval
134
+
- Job ID
135
+
- Cycle ID
136
+
- Change ID
137
+
- Source ID
138
+
- Target ID
139
+
- Application
130
140
131
-
When you select a custom time frame, you can configure a start date and an end date.
132
141
142
+

133
143
134
-
In addition to the default fields, when selected, you can also include the following fields in your filter:
135
144
136
145
-**Job ID** - A unique Job ID is associated with each application that you have enabled provisioning for.
137
146
@@ -140,8 +149,13 @@ In addition to the default fields, when selected, you can also include the follo
140
149
-**Change ID** - Unique identifier for the provisioning event. You can share this ID to support to look up the provisioning event.
141
150
142
151
152
+
-**Source System** - Enables you to specify where the identity is getting provisioned from. For example, when provisioning an object from Azure AD to ServiceNow, the Source system is Azure AD.
153
+
154
+
-**Target System** - Enables you to specify where the identity is getting provisioned to. For example, when provisioning an object from Azure AD to ServiceNow, the Target System is ServiceNow.
155
+
156
+
-**Application** - Enables you to show only records of applications with a display name that contains a specific string.
0 commit comments