Consider the following scenario:
- You’re using SharePoint 2016 or 2019 and using Active Directory Import to import user profiles.
- You decide to switch to using an external identity manager utilizing Microsoft Identity Manager (MIM).
- You configure MIM and run a Full Import on the SharePoint Management Agent (SPMA).
- The Full Import does not import anything and shows status “Completed-No-Objects“.
Switching your profile synchronization option from “Active Directory Import” to “External Identity Manager” (or vice versa) clears out a few “status” tables in the Profile database that the SharePoint import / export web service uses to determine the synch status of the imported profiles. That is normal and expected.
However, in that case, when only a Full Import step is run, the web service cannot tell that any profiles have been imported, so the step will complete with status “Completed-No-Objects“
Usually, this goes unnoticed because in most cases, Administrators will kick off a “Full Synchronization”, which would include a Full Import from Active Directory (AD), Full Sync for the AD Management Agent, Full Sync for the SharePoint MA, and then Export to SharePoint.
During that Export to SharePoint, those “status” tables are populated, and then subsequent runs of the Full Import step for the SharePoint MA are able to pull the existing user profiles into MIM.
You must run though all the Sync steps (run profiles) the first time around, and then Full Import should work after that.
In most cases, simply running through all of the synchronization steps / run profiles for both the AD and SP management agents will fix this up.
If that doesn’t work, you may need to clear out the SharePoint connector space and then run a few sync steps in a certain order to properly populate the connector space and hook up the existing AD objects to the existing SharePoint profiles, as detailed below: