When the user management changes are performed via the Atlassian cloud administration, the changes are first applied on the Atlassian cloud identity service. These are then propagated further to the cwd tables of the Jira application. 

Within the Jira audit log, the terms com.atlassian.crowd.directory.IdentityPlatformRemoteDirectory and IDP Directory are used in the event entry with Jira as the author. This can be confusing to Jira administrators as it would seem that external/third party identity directories are involved. In reality, these are just the changes from the Atlassian cloud identity service propagating to the Jira application. 

Suggestion

• Hide the terms com.atlassian.crowd.directory.IdentityPlatformRemoteDirectory and IDP Directory from the Jira audit log entries. This is irrelevant to Jira administrators. 
• In the Jira audit logs, specify the real actors for the user management changes or put a link instead to the orgainzation audit log events. 
• Specify the full user details similar to the organization audit log

Workaround 

Inspect the organization audit logs to check who are the real actors for the user management events.

Org Administration > Security > Audit log