What are the Microsoft Entra user provisioning logs?

Microsoft Entra ID integrates with several non-Microsoft services to provision users into your tenant. If you need to troubleshoot an issue with a provisioned user, you can use the information captured in the Microsoft Entra provisioning logs to help find a solution.

Two other activity logs are also available to help monitor the health of your tenant:

• Sign-ins – Information about sign-ins and how your resources are used by your users.
• Audit – Information about changes applied to your tenant such as users and group management or updates applied to your tenant’s resources.

This article gives you an overview of the user provisioning logs.

License and role requirements

To use the provisioning logs, you need a Microsoft Entra ID P1 or P2 license.

The following roles are required to view the provisioning logs:

• Reports Reader
• Security Reader
• Application Administrator
• Cloud App Administrator

What can you do with the provisioning logs?

You can use the provisioning logs to find answers to questions like:

• What groups were successfully created in ServiceNow?
• What users were successfully removed from Adobe?
• What users from Workday were successfully created in Active Directory?

Note

Entries in the provisioning logs are system generated and can't be changed or deleted.

What do the logs show?

The logs display the identity, action taken, source system, target system, and the status of the provisioning event. Other columns can be added for further troubleshooting, but the following details are standard:

• Identity: The display name and source ID of the identity being provisioned appear in this column.
• Action: Possible values include Create, Update, Delete, Disable, StagedDelete, and Other.
  • Examples of Other include if the source and target system details already match, so no change was made.
• Source System and Target System: Paired together, these details show which system the identity is coming from and where it's being provisioned.
• Status: Possible values include Success, Failure, Skipped, and Warning.
  • There are several scenarios that could trigger the Skipped status. For details on these scenarios, see No users are being provisioned

Select an item from the provisioning logs to see more details about this item, such as the steps taken to provision the user and tips for troubleshooting issues. The details are grouped into four tabs.

• Steps: This tab outlines the steps taken to provision an object. Provisioning an object can include the following steps, but not all steps are applicable to all provisioning events.

  • Import the object.
  • Match the object between source and target.
  • Determine if the object is in scope.
  • Evaluate the object before synchronization.
  • Provision the object (create, update, delete, or disable).

  

• Troubleshooting & Recommendations: If there was an error, this tab provides the error code and reason. In many cases, a detailed description of the error is provided. Review this information to understand the issue and follow the guidance provided to resolve it. Review the following troubleshooting articles:

  • Troubleshoot HR user creation issues
  • Troubleshoot HR user update issues
  • Troubleshoot insufficient access rights error

• Modified Properties: If there were changes, this tab shows the old value and the new value.

• Summary: Provides an overview of what happened and identifiers for the object in the source and target systems.

Related content

• Integrating provisioning logs with Azure Monitor logs
• Reporting on automatic user account provisioning