duplicate devices in Microsoft Defender Device Inventory

Tilman Schmidt 100 Reputation points
2025-04-24T08:29:19.5433333+00:00

In the Microsoft Defender portal Device Inventory page for my tenant there are several instances where one and the same PC appears twice with different names.

One entry shows the default name "desktop-" + 7 random characters assigned by Windows to new systems, while the other one has the correct name assigned by us according to our naming convention. Both entries show the same value in the fields "Device AAD id" and "Hardware UUID", but different values in the field "Device id" (without "AAD"). The IP addresses are the same. Both show "Managed by: Intune". The First/Last Seen intervals are disjoint, with the default name sightings predating those for the correct name, as expected.

In Intune, the affected PCs appear only once, with the correct name.

How can that happen, how do I clean it up, and how can I prevent it from reoccurring?

Microsoft Defender for Cloud
Microsoft Defender for Cloud
An Azure service that provides threat protection for workloads running in Azure, on-premises, and in other clouds. Previously known as Azure Security Center and Azure Defender.
1,528 questions
{count} votes

Accepted answer
  1. Catherine Kyalo 1,305 Reputation points Microsoft Employee
    2025-04-25T07:42:42.0366667+00:00

    Hi Tilman Schmidt, Below are some known actions that will create a new/additional entry for onboarded machines in MDE:

    • Renaming device
    • Workgroup rename/change/join
    • Join a Domain
    • Changing primary DNS suffix

    Here is some logic into why duplicate entries are created for "can be onboarded" and "onboarded"?

    For Windows OS, Device Discovery is based on the MAC address and name of discovered host. So, if a device is joined to the domain (for example), then the device ID of the onboarded machine will be different than that of the original "can be onboarded" discovered device. Regardless, upon next active probe by a nearby agent with 'Discovery' - it is expected that a match will be found between the MAC address of the onboarded device and the previous discovered ID (that no longer points to an unmanaged host) and the old Device in the "can be onboarded" state will be removed from the portal.

    Probing happens roughly every 3 weeks, and so the duplicates may take at least 3 weeks to resolve.

    One recommendation is that Discovered devices should be merged with onboarded devices if identified as the same device.

    If you find the answer above helpful, please Accept the answer to help anyone in the community who might have a similar question to quickly find the solution.

    1 person found this answer helpful.
    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.