Skip to content
Troubleshoot and Fix Issue in Duplicate Device Records in Entra ID During Autopilot Hybrid Join

Troubleshoot and Fix Issue in Duplicate Device Records in Entra ID During Autopilot Hybrid Join

Written By Anoop C Nair
Last Updated July 7, 2026
Posted In Entra
SHARE

Let’s discuss Troubleshoot and Fix Issue in Duplicate Device Records in Entra ID During Autopilot Hybrid Join. Some of the users face issues while deploying Windows Laptops with Autopilot and are Hybrid AD joined. This issue is affecting the deployed devices.

There are many issues that occur on Windows Autopilot devices. Most of the issues happen due to mistakes from the Admin side, Network Issues, etc. In this case, the Duplicate Device Records issue occurred which is confirmed by Microsoft.

As you know, in old sore, devices are created twice as the device is first Entra AD joined, after which the device is joined as a Hybrid AD joined device (configuration profile), and thus creating two devices which represent one physical device

Microsoft Support confirmed the above mentioned old soar and does not seem to be a solution. In this case, the same issue is occurred. In this blog post, I would like to share the reasons and recommended actions of this issue.

Patch My PC
Troubleshoot and Fix Issue in Duplicate Device Records in Entra ID During Autopilot Hybrid Join - Fig.1
Troubleshoot and Fix Issue in Duplicate Device Records in Entra ID During Autopilot Hybrid Join – Fig.1

Troubleshoot and Fix Issue in Duplicate Device Records in Entra ID During Autopilot Hybrid Join

As mentioned, the issue is occurred due to old sore which makes issue in Windows Autopatch Deployment. Hybrid AD joined device shows that it is not managed by an MDM, while the Entra-ID joined device shows managed by Intune.

Old Sore Details
An Entra-ID joined device that becomes stale over time, as the device stats are no longer updated. And thus becomes Uncompliant.
An Entra-ID Hybrid joined device which is managed by Intune, and updated so wherefore the device is compliant.
Troubleshoot and Fix Issue in Duplicate Device Records in Entra ID During Autopilot Hybrid Join – Table.1
Troubleshoot and Fix Issue in Duplicate Device Records in Entra ID During Autopilot Hybrid Join - Fig.2 - Creds to MS
Troubleshoot and Fix Issue in Duplicate Device Records in Entra ID During Autopilot Hybrid Join – Fig.2 – Creds to MS

After Effects of the Issue

Due to this issue, correct device is no longer updated by Intune. Also when looking the device ownership it can be can seen that the wrong device states company owned, while the Hybrid AD joined device shows none. Policy Targeting and reporting will be affected.

Troubleshoot and Fix Issue in Duplicate Device Records in Entra ID During Autopilot Hybrid Join - Fig.3 - Creds to MS
Troubleshoot and Fix Issue in Duplicate Device Records in Entra ID During Autopilot Hybrid Join – Fig.3 – Creds to MS

Workaround

This issue has no final resolution. the issue is well known by Microsoft and they still confirm that in a hybrid environment you should only have one hybrid artifact in Entra per device after the initial sync.

Some of the Admins suggest workaround which can be used to resolve your issue. But it is not final resolution. The valuable suggestions are provided by Mr.
Bogdan_Guinea, rpcpancil and TherealKillerbe.

Manual Cleanup

Mr. rpcpancil suggested that Manual cleanup is the best solution. Delete stale Entra ID devices after verifying the correct one is active.

Reset Device Registration with Command

Mr. Bogdan_Guinea suggested that, Login in to the device and open cmd in administrator mode. Then you need to run the command DSREGCMD /leave. Checking the status (DSREGCMD /Status) before the leave shows that the device is Hybrid Ad joined. After the leave, the status shows that the device is not Entra-ID joined. Then you need to reboot the device.

Once the device is rebooted you again check the status and see that although you performed a leave, the device is still Hybrid AD joined. At this moment, the Entra-ID device is updated in which the Hybrid Entra-ID device ownership is registered to company.

  • In Intune device is still not updated and remains stale.
  • Then run the DSREGCMD /Join command again in administrator mode.
  • Then the Intune device will be registered correctly.
  • A reboot is required in each step, and thus also after performing the Join.
  • No objects were deleted from Entra-ID during the procedure.
  • So even after the process, your objects for the device remain.
  • Remove the obsolete device this time, after verifying that the correct device is registered in Intune.

Need Further Assistance or Have Technical Questions?

Join the LinkedIn Page and Telegram group to get the latest step-by-step guides and news updates. Join our Meetup Page to participate in User group meetings. Also, join the WhatsApp Community to get the latest news on Microsoft Technologies. We are there on Reddit as well.

Author

Anoop C Nair has been Microsoft MVP for 10 consecutive years from 2015 onwards. He is a Workplace Solution Architect with more than 22+ years of experience in Workplace technologies. He is a Blogger, Speaker, and Local User Group Community leader. His primary focus is on Device Management technologies like SCCM and Intune. He writes about technologies like Intune, SCCM,  Windows, Cloud PC, Windows, Entra, Microsoft Security, Career, etc.

Written by

Anoop C Nair is Workplace Technology solution architect with 25+ years of experience in global enterprise organizations such as JP Morgan, Capgemini, etc. Microsoft Certified Trainer. Microsoft MVP from 2015 onwards for consecutive 11+ years! He also conducts Intune and modern workplace tech training for enterprise organizations. He is Blogger, Speaker, and Founder of HTMD Community and HTMD Conference. His main focus is on Device Management technologies like Intune, Windows, Cloud PC. He writes about technologies like Intune, SCCM, Windows, Cloud PC, Windows, Entra, Microsoft Security.

Discussion

Join the discussion

Your email address will not be published. Required fields are marked *

Related guides

Entra

Entra ID SSPR Improves Security with Registered Authentication Methods | Impact on Unregistered Users Starting September 2026

Key Takeaway Entra ID SSPR Improves Security with Registered Authentication Methods! Starting September 7, 2026, Microsoft Entra ID Self-Service Password Reset (SSPR) will require users to verify their identity using explicitly registered authentication methods. Directory-sourced contact information, such as mobile phone numbers, business phone numbers, and alternate email addresses, will no longer be accepted for […]

AC Anoop C Nair 4 min read
Entra

Explicit Forward Proxy in Microsoft Entra Internet Access Helps Secure VDI BYOD and Clientless Browsing

Key Takeaways Explicit Forward Proxy in Microsoft Entra Internet Access! This feature allows organizations to use secure web and AI gateway capabilities without deploying the Global Secure Access client, making it useful for browser-based and lightly managed environments. It works with browsers that support Proxy Auto-Configuration (PAC) files. Since this is a prerelease feature, Microsoft […]

AC Anoop C Nair 3 min read
Cloud

Microsoft Enables Entra Writeback for Cloud-Managed Remote Mailboxes to Help Remove Last Exchange Server

Key Takeaways: Let’s discuss about Microsoft Unlocks Entra Writeback for Cloud-Managed Remote Mailboxes to Help Remove Last Exchange Server. For customers with no remaining dependency on their last Exchange Server, a guide for decommissioning your last Exchange Server. Microsoft announced the Public Preview of Cloud-Managed Remote Mailboxes. Microsoft is excited to share these two new milestones […]

AC Anoop C Nair 3 min read