Forum Discussion
Migration tool
MicrosoftGreat question. The tool that you linked to is actually to migrate MDM policies from a hybrid ConfigMgr/Intune configuration to an Intune standalone configuration. It will not to translate GPO to MDM – check out https://github.com/WindowsDeviceManagement/MMAT for that.
BTW, PowerShell script execution is in fact coming to Intune with the Intune Management Extension that will be released in a few weeks!
I thought that if you offer co-management, then this can be seen as a "long transition phase", and you believe that one day, your customers will not stay with SCCM and Intune running in parallel forever, even if these "authority sliders" in SCCM 1710 let you choose what backend is doing what.
Then sooner or later, the Data Importer tool and MMAT tools will need to translate the GPOs and other advanced SCCM options to their MDM equivalents...or you will somehow "simplify" things by dropping lot of SCCM options, no? ;-).
- Maayan Bar-Niv
You are right, co-management is a temporary state and not an end goal (though it may last years in some organizations). Modern management is about simplifying IT processes. For settings this means that policies are more intent based, and not as granular as the thousands of GPOs available today - we have no intention to replicate all of those to MDM. We are making sure that all the critical settings are addressed in MDM (and you will see that most gaps are addressed in the Fall creators update), and looking to our customers to continue to provide the feedback on any settings gaps they see in the MDM model. We are working on experiences in SCCM to help with the transition, through MMAT and by leveraging the Management Insights framework that we added in 1708 TP.
