The MIM synchronization service is the heart of the product. You can import and aggregate data in a central identity store, which is called metaverse (MV). The service provides a staging zone to compare the connected directory with the metaverse. This staging zone is called the connector space (CS). The connection to any repository is done over specific connectors, which are also called management agents (MAs). The synchronization service is also responsible for the data integrity through all connected repositories, including the provisioning and deprovisioning of objects, including their attributes. You can find an overview of the available connectors at https://docs.microsoft.com/en-us/microsoft-identity-manager/supported-management-agents. In case you need a custom connector, MIM provides a development framework to fit your needs.

The following screenshot shows an example of different directories and systems that can be connected:

Refer to the following practical notes:

• MIM synchronization service is a state-based system by default:
  • Imported data will be compared with previously imported data; differences indicate modifications in the source
  • Imported data will be compared with previously exported data; no difference indicates a successful export
• MIM is not real-time; it uses run cycles that can be configured

MIM synchronization can work event-based with a synchronization service extension, as we provide in the following section.