May 11 2020 09:04 AM
May 12 2020 07:06 AM
@Dean Gross The answer is: it depends Obviously, the client needs to be enrolled first. As explained in the Enable co-management for existing Configuration Manager clients tutorial:
Starting in version 1806, automatic enrollment isn't immediate for all clients. This behavior helps enrollment scale better for large environments. Configuration Manager randomizes enrollment based on the number of clients. For example, if your environment has 100,000 clients, when you enable this setting, enrollment occurs over several days.
Check the CoManagementHandler.log file on the client for any errors during the enrollment process. For more information, see Troubleshooting co-management: Auto-enroll existing Configuration Manager-managed devices into Intun....
May 12 2020 10:35 AM
May 13 2020 07:35 AM
@Dean Gross Impossible to say from here, but the first thing I would check is if the client did actually receive and process the co-management policy. Is the client healthy, requesting policy and sending inventory/status/state messages? Is it Azure AD joined? Is it in scope for co-management (member of a collection that's targeted for Intune auto enrollment)? If so, do the various "CoMgmtSettings..." baselines show up in the Configurations tab for the ConfigMgr Client control panel applet? If so, are they marked as Compliant? The troubleshooting link I posted earlier contains additional steps you can take to investigate this further.