Make Intune report export columns and localization explicit

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.

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.