# Preserve device identity when joining Intune fleet inventory

> How should a fleet query keep its device context when joining or summarizing inventory?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-108-preserve-device-identity-when-joining-intune-fleet-inventory/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:30:08+00:00
- Modified: 2026-09-10T00:52:38+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, IT
- Reading time: 1 minutes

## What you need to know

How should a fleet query keep its device context when joining or summarizing inventory?

## Potentially affected

Use this review for device-query inventory analysis. Confirm platform prerequisites and the intended population before treating the result as a fleet-wide answer.

## DSE recommendation

Write down whether the question asks for devices, components, or grouped measurements.

## Article

## Source facts

Intune fleet queries cover managed, corporate-owned devices; Windows inventory requires a properties catalog policy. Device is an entity, so scalar operations need a property such as its serial number. Microsoft no longer supports joins on Device.DeviceID; device joins use Device instead. Projection and aggregation can change the returned columns. [Microsoft Learn](https://learn.microsoft.com/en-us/intune/advanced-analytics/device-query-multiple-devices).

## Applicability

Use this review for device-query inventory analysis. Confirm platform prerequisites and the intended population before treating the result as a fleet-wide answer.

## DSE recommendation

Write down whether the question asks for devices, components, or grouped measurements. Retain an explicit device identifier wherever the result must be traced back to an endpoint. Review each join and projection against the supported syntax rather than transplanting a general KQL query unchanged. Keep any proposed group-targeting action separate from the initial read-only query.

## Verification

Choose a few known devices with different inventory characteristics and compare their source records with the query output. Check which identifiers survive the final projection and whether the reported count answers the original question. Investigate missing or unexpected rows before exporting a targeting list. Retain the query text and collection scope alongside the results so another operator can reproduce the interpretation.

## Official references

[Microsoft Learn: Device Query for Multiple Devices](https://learn.microsoft.com/en-us/intune/advanced-analytics/device-query-multiple-devices).

## Primary reference

- Name: Device Query for Multiple Devices - Microsoft Intune | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/intune/advanced-analytics/device-query-multiple-devices
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Preserve device identity when joining Intune fleet inventory,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-108-preserve-device-identity-when-joining-intune-fleet-inventory/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.