{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-108-preserve-device-identity-when-joining-intune-fleet-inventory/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260909-108-preserve-device-identity-when-joining-intune-fleet-inventory/", "slug": "dse-20260909-108-preserve-device-identity-when-joining-intune-fleet-inventory", "url": "https://update.dsesecurity.com/updates/dse-20260909-108-preserve-device-identity-when-joining-intune-fleet-inventory/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260909-108-preserve-device-identity-when-joining-intune-fleet-inventory.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-108-preserve-device-identity-when-joining-intune-fleet-inventory/" }, "title": "Preserve device identity when joining Intune fleet inventory", "summary": "How should a fleet query keep its device context when joining or summarizing inventory?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "identity-cloud", "label": "Identity & cloud", "alt": "Governed cloud identity system with connected service and lifecycle nodes.", "card_url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "business-continuity", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-09-10T00:30:08+00:00", "modified_at": "2026-09-10T00:52:38+00:00", "reviewed_on": "2026-09-09", "reading_minutes": 1, "word_count": 205, "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.", "primary_source": { "name": "Device Query for Multiple Devices - Microsoft Intune | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/intune/advanced-analytics/device-query-multiple-devices", "published_on": null, "authority": "Microsoft Learn" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Source facts

\n

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.

\n

Applicability

\n

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

\n

DSE recommendation

\n

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.

\n

Verification

\n

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.

\n

Official references

\n

Microsoft Learn: Device Query for Multiple Devices.

", "content_text": "Source facts\nIntune 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.\nApplicability\nUse this review for device-query inventory analysis. Confirm platform prerequisites and the intended population before treating the result as a fleet-wide answer.\nDSE recommendation\nWrite 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.\nVerification\nChoose 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.\nOfficial references\nMicrosoft Learn: Device Query for Multiple Devices.", "content_markdown": "## Source facts\n\nIntune 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).\n\n## Applicability\n\nUse this review for device-query inventory analysis. Confirm platform prerequisites and the intended population before treating the result as a fleet-wide answer.\n\n## DSE recommendation\n\nWrite 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.\n\n## Verification\n\nChoose 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.\n\n## Official references\n\n[Microsoft Learn: Device Query for Multiple Devices](https://learn.microsoft.com/en-us/intune/advanced-analytics/device-query-multiple-devices)." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/dse-20260909-108-preserve-device-identity-when-joining-intune-fleet-inventory/", "url": "https://update.dsesecurity.com/updates/dse-20260909-108-preserve-device-identity-when-joining-intune-fleet-inventory/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-09" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260909-108-preserve-device-identity-when-joining-intune-fleet-inventory/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Preserve device identity when joining Intune fleet inventory", "item": "https://update.dsesecurity.com/updates/dse-20260909-108-preserve-device-identity-when-joining-intune-fleet-inventory/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260909-108-preserve-device-identity-when-joining-intune-fleet-inventory/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260909-108-preserve-device-identity-when-joining-intune-fleet-inventory/", "url": "https://update.dsesecurity.com/updates/dse-20260909-108-preserve-device-identity-when-joining-intune-fleet-inventory/", "headline": "Preserve device identity when joining Intune fleet inventory", "description": "How should a fleet query keep its device context when joining or summarizing inventory?", "abstract": "How should a fleet query keep its device context when joining or summarizing inventory?", "articleBody": "Source facts\nIntune 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.\nApplicability\nUse this review for device-query inventory analysis. Confirm platform prerequisites and the intended population before treating the result as a fleet-wide answer.\nDSE recommendation\nWrite 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.\nVerification\nChoose 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.\nOfficial references\nMicrosoft Learn: Device Query for Multiple Devices.", "datePublished": "2026-09-10T00:30:08+00:00", "dateModified": "2026-09-10T00:52:38+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260909-108-preserve-device-identity-when-joining-intune-fleet-inventory/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/dse-20260909-108-preserve-device-identity-when-joining-intune-fleet-inventory/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/identity-cloud-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Preserve device identity when joining Intune fleet inventory" }, "articleSection": [ "Business Continuity", "IT" ], "keywords": [ "Business Continuity", "IT", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 205, "timeRequired": "PT1M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Device Query for Multiple Devices - Microsoft Intune | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/intune/advanced-analytics/device-query-multiple-devices" } } ] } }