Event banner
AMA: Troubleshoot device issues with Intune
Event Ended
Thursday, Sep 14, 2023, 08:30 AM PDTEvent details
Looking to improve the troubleshooting experience within Intune? Have questions on accessing ServiceNow incidents in the admin console? Curious how to use advanced analytics to drill down into report...
Heather_Poulsen
Updated Dec 27, 2024
ryanmcdonald
Sep 14, 2023Copper Contributor
Hybrid Azure AD Joined Device when going through Autopilot, it creates two Devices in Entra.
From what I have read that is expected but wondering if that is correct and if so, is there any recommendations to identify these separately from each other.
- Char_CheesmanSep 14, 2023Bronze Contributor
Thanks for participating in today's AMA: Troubleshoot device issues with Intune! For reference, the panel covered this topic at 40:10.
- HeyHey16KSep 14, 2023Iron ContributorWe have this too and have been told it is correct
- Hung_DangSep 14, 2023
Microsoft
This is correct. Autopilot registration precreates the Entra device object. After a device gets deployed via AP-into-HAADJ, the device object also gets created in AD, which syncs it (via the AAD Connector) to Entra during the user ESP. That's why you see two objects in Entra. To identify them, they have the same ZTDID property and have different object types. This is unfortunately a side effect of the two different infrastructures targeted (i.e., Entra by Autopilot, AD by HAADJ) and the necessity to associate them together somewhere. Hope that helps, Ryan. Have a great day!