# Make Intune report export columns and localization explicit

> Will an automated Intune export retain the schema and values its consumer expects?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-515-make-intune-report-export-columns-and-localization-explicit/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:23:21+00:00
- Modified: 2026-09-10T02:11:18+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, IT
- Reading time: 2 minutes

## What you need to know

Will an automated Intune export retain the schema and values its consumer expects?

## Potentially affected

Use this design for reports supported by Intune’s export infrastructure. Identify the exact report name and its valid columns before adapting an example request.

## DSE recommendation

Define the expected column set and which fields the consumer treats as stable identifiers, raw values, or display labels.

## Article

## Source facts

Microsoft directs report-export automation to select named columns rather than depend on defaults. The default localization mode supplies a raw-value column plus a localized companion ending in _loc; replacement mode returns localized values under the original name. The Devices and DevicesWithInventory reports do not honor that localization setting because of compatibility requirements. [Microsoft Learn](https://learn.microsoft.com/en-us/intune/device-management/reports/export-graph-apis).

## Applicability

Use this design for reports supported by Intune’s export infrastructure. Identify the exact report name and its valid columns before adapting an example request.

## DSE recommendation

Define the expected column set and which fields the consumer treats as stable identifiers, raw values, or display labels. Make the localization choice part of the request contract and record any report-specific exception. Preserve the raw export separately from presentation changes. Do not repair an unexpected column set by silently guessing which friendly label replaced a machine-readable value.

## Verification

Run an authorized sample export and wait for its completed job result before inspecting the downloaded data. Compare column names and representative values with the contract, including an exception report if the automation supports one. Test missing, additional, and unexpectedly localized columns as explicit validation failures. Retain the report name, request parameters, job identity, and sanitized sample with the consumer version so a later schema change can be investigated without trusting default behavior.

## Official references

[Microsoft Learn: Use Graph APIs to Export Intune Reports](https://learn.microsoft.com/en-us/intune/device-management/reports/export-graph-apis).

## Primary reference

- Name: Use Graph APIs to Export Intune Reports - Microsoft Intune | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/intune/device-management/reports/export-graph-apis
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Make Intune report export columns and localization explicit,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-515-make-intune-report-export-columns-and-localization-explicit/
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.