MIM 2016 future improvements
We have already discussed the role and importance of MIM 2016 in the On-Premise IAM landscape. As you already know, there are two synchronization engines in place at the moment - the Azure Active Directory (AAD) Connect and the MIM 2016 synchronization engine.
Synchronization engine merger
One of the main strategies of Microsoft is to combine these two engines into one for better usability and the fulfillment of all requirements with one engine. Microsoft actually recommends using AAD Connect for synchronization with Azure AD and MIM 2016 to synchronize with all the On-premise directories and repositories. The first steps of consolidation are already done for building the identity bridge, as you can see with all the rich functionality of Azure AD Connect. The consolidation process is still in progress.
REST API support
Another planned strategy is to provide a complete REST API for the MIM Service. You will find a partial implementation with the MIM PAM portal...