Co-Management Mechanism

Occasional Contributor

Good day, 


Do you know the exact mechanism co-management uses to communicate between Intune and Config Man?


Scenario: Computer1 is ConfigMan client.

                 Computer1 goes home and never connects on VPN.

                 No IBCM or CMG is configured. No Contact with MP.

                 You enable Automatic Enrollment in Azure MDM and assign the user license.

                 You also configure Co-management On-premise and add the machine to the Pilot Collection.

                 You go one step further and enable Hybrid Azure Join in ADConnect.


Does the machine know it is co-management or does ConfigMan Client block the Intune Enrollment (due to no policy)?

5 Replies
Sorry, to specify the reason for this question, it is a customer that wants to enable Windows Update for Business for machines that are currently at home without VPN connection to the SCCM MP.
Tough spot for sure. There's not really going to be a good solution here but there are solutions, that are outside the box, Something like using Intune, but still that might have some caveats, and pitfalls. Feel free to reach out via Direct Message and we can chat about some interesting options.
In case you enable client to be managed by Intune, when user is not connected to VPN (meaning Config Manager is not managing it) when it connect to internet, it will be managed by Intune. Unless if there are any specific policy which might cause conflict or blocking.
I recommend you to check Intune for status of device enrollment .

In your scenario , you may ask user to enroll to Intune and manage it.
Thank you Danny, will do
Thank you Reza, currently all the machines have the ConfigMan agent. So we are looking at ways to enroll machines into Intune so we can get to the end state of WuFB. For now at least, these machines will have to communicate with the MP to become co-managed. Just needed to confirm this is what I suspected.