Remove the SharePoint prerequisite for MIM portal.
The fact that MIM Portal runs on top of SharePoint just adds a lot of extra complexity and moving parts. If MIM Portal instead was just a simple IIS application it would become a lot easier to set up and maintain.
Unless other variables change we do not plan to remove this from SharePoint. We have however added the support for Minroles(Front-end) in the SharePoint deployment model to reduce the footprinthttps://docs.microsoft.com/en-us/sharepoint/what-s-new/new-and-improved-features-in-sharepoint-server-2016#minrole
-David , MIM Engineering Manager
Gavin Ashton commented
Many customers have custom features built upon the MIM Portal with it being a SharePoint platform offering those features. If the SP element is removed, those customers potentially face some heavy redevelopment. But I agree, in general 'self service' should be moving out to places like ServiceNow with requests being piped directly to the MIM Service via the Azure service bus (for example). The portal component itself could be diminished in functionality - perhaps as an admin function only? Interesting topic.
Marc Mac Donell commented
@Peter, agreed. I have had two clients so far balk at deploying SharePoint 2016 on Windows Server 2016 to simply host the MIM Portal, due to licensing requirements. In those cases, we've ended up with SharePoint Foundation 2013 on Windows Server 2012 R2. Not really the direction we want to be going...
It would be really great to have that, since there are no more SharePoint Foundation Version and installating SharePoint just for some technical basics is oversized.
Should be one of the major points for a next release.