Forum Discussion
co-managed Working flow
Your follow-up says enrollment succeeds; the missing piece is how that happens without another sign-in. Configuration Manager enrollment can authenticate with the device's Microsoft Entra token, rather than waiting for a user token. That is authenticated enrollment, even when nobody sees a prompt.
Microsoft documents two paths: Configuration Manager clients automatically enrolling into Intune, and devices already enrolled in Intune receiving the Configuration Manager client. These should not be treated as identical evidence of tenant routing. For automatic enrollment, Configuration Manager checks stored MDM URLs against the expected Intune tenant; the setup administrator's credentials are not reused as every device's credentials.
Compare one device from each domain: record its Entra tenant ID, Intune enrollment tenant and CoManagementHandler.log entries. Look for RegisterDeviceWithManagementUsingAADDeviceCredentials and establish which enrollment path ran. Workload movement follows client co-management policy and workload settings. Successful enrollment alone does not establish automatic per-domain tenant mapping for your hierarchy.