Tutorial: Reporting on automatic user account provisioning
Microsoft Entra ID includes a user account provisioning service. The service helps automate the provisioning deprovisioning of user accounts in SaaS apps and other systems. The automation helps with end-to-end identity lifecycle management. Microsoft Entra ID supports preintegrated user provisioning connectors for many applications and systems. To learn more about user provisioning tutorials, see Provisioning Tutorials.
This article describes how to check the status of provisioning jobs after they have been set up, and how to troubleshoot the provisioning of individual users and groups.
Provisioning connectors are set up and configured using the Microsoft Entra admin center, by following the provided documentation for the supported application. When the connector is configured and running, provisioning jobs can be reported using the following methods:
Streaming the provisioning logs into Azure Monitor. This method allows for extended data retention and building custom dashboards, alerts, and queries.
Querying the Microsoft Graph API for the provisioning logs.
Downloading the provisioning logs as a CSV or JSON file.
This article uses the following terms:
- Source System - The repository of users that the Microsoft Entra provisioning service synchronizes from. Microsoft Entra ID is the source system for most preintegrated provisioning connectors, however there are some exceptions (example: Workday Inbound Synchronization).
- Target System - The repository of users where the Microsoft Entra provisioning service synchronizes. The repository is typically a SaaS application, such as Salesforce, ServiceNow, G Suite, and Dropbox for Business. In some cases the repository can be an on-premises system such as Active Directory, such as Workday Inbound Synchronization to Active Directory.
Getting provisioning reports from the Microsoft Entra admin center
To get provisioning report information for a given application:
- Sign in to the Microsoft Entra admin center as at least a Application Administrator.
- Browse to Identity > Applications > Enterprise applications.
- Select Provisioning logs in the Activity section. You can also browse to the Enterprise Application for which provisioning is configured. For example, if you're provisioning users to LinkedIn Elevate, the navigation path to the application details is:
Identity > Applications > Enterprise applications > All applications > LinkedIn Elevate
From the all applications area, you access both the provisioning progress bar and provisioning logs.
Provisioning progress bar
The provisioning progress bar is visible in the Provisioning tab for a given application. It's located in the Current Status section and shows the status of the current initial or incremental cycle. This section also shows:
- The total number of users and groups that are synchronized and currently in scope for provisioning between the source system and the target system.
- The last time the synchronization was run. Synchronizations typically occur every 20-40 minutes, after an initial cycle has completed.
- The status of an initial cycle and if the cycle has been completed.
- The status of the provisioning process and if it's being placed in quarantine. The status also shows the reason for the quarantine. For example, a status might indicate a failure to communicate with the target system due to invalid admin credentials.
The Current Status should be the first place admins look to check on the operational health of the provisioning job.
All activities performed by the provisioning service are recorded in the Microsoft Entra provisioning logs. You can access the provisioning logs in the Microsoft Entra admin center. You can search the provisioning data based on the name of the user or the identifier in either the source system or the target system. For details, see Provisioning logs.
The provisioning summary report and provisioning logs play a key role helping admins troubleshoot various user account provisioning issues.
For scenario-based guidance on how to troubleshoot automatic user provisioning, see Problems configuring and provisioning users to an application.