{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-515-make-intune-report-export-columns-and-localization-explicit/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/dse-20260909-515-make-intune-report-export-columns-and-localization-explicit/",
        "slug": "dse-20260909-515-make-intune-report-export-columns-and-localization-explicit",
        "url": "https://update.dsesecurity.com/updates/dse-20260909-515-make-intune-report-export-columns-and-localization-explicit/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/dse-20260909-515-make-intune-report-export-columns-and-localization-explicit.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-515-make-intune-report-export-columns-and-localization-explicit/"
        },
        "title": "Make Intune report export columns and localization explicit",
        "summary": "Will an automated Intune export retain the schema and values its consumer expects?",
        "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:23:21+00:00",
        "modified_at": "2026-09-10T02:11:18+00:00",
        "reviewed_on": "2026-09-09",
        "reading_minutes": 2,
        "word_count": 227,
        "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.",
        "primary_source": {
            "name": "Use Graph APIs to Export Intune Reports - Microsoft Intune | Microsoft Learn",
            "url": "https://learn.microsoft.com/en-us/intune/device-management/reports/export-graph-apis",
            "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": "<h2>Source facts</h2>\n<p>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. <a href=\"https://learn.microsoft.com/en-us/intune/device-management/reports/export-graph-apis\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn</a>.</p>\n<h2>Applicability</h2>\n<p>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.</p>\n<h2>DSE recommendation</h2>\n<p>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.</p>\n<h2>Verification</h2>\n<p>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.</p>\n<h2>Official references</h2>\n<p><a href=\"https://learn.microsoft.com/en-us/intune/device-management/reports/export-graph-apis\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn: Use Graph APIs to Export Intune Reports</a>.</p>",
        "content_text": "Source facts\nMicrosoft 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.\nApplicability\nUse this design for reports supported by Intune’s export infrastructure. Identify the exact report name and its valid columns before adapting an example request.\nDSE recommendation\nDefine 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.\nVerification\nRun 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.\nOfficial references\nMicrosoft Learn: Use Graph APIs to Export Intune Reports.",
        "content_markdown": "## Source facts\n\nMicrosoft 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).\n\n## Applicability\n\nUse this design for reports supported by Intune’s export infrastructure. Identify the exact report name and its valid columns before adapting an example request.\n\n## DSE recommendation\n\nDefine 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.\n\n## Verification\n\nRun 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.\n\n## Official references\n\n[Microsoft Learn: Use Graph APIs to Export Intune Reports](https://learn.microsoft.com/en-us/intune/device-management/reports/export-graph-apis)."
    },
    "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-515-make-intune-report-export-columns-and-localization-explicit/",
                "url": "https://update.dsesecurity.com/updates/dse-20260909-515-make-intune-report-export-columns-and-localization-explicit/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-09-09"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-515-make-intune-report-export-columns-and-localization-explicit/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Make Intune report export columns and localization explicit",
                        "item": "https://update.dsesecurity.com/updates/dse-20260909-515-make-intune-report-export-columns-and-localization-explicit/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-515-make-intune-report-export-columns-and-localization-explicit/#article",
                "identifier": "https://update.dsesecurity.com/updates/dse-20260909-515-make-intune-report-export-columns-and-localization-explicit/",
                "url": "https://update.dsesecurity.com/updates/dse-20260909-515-make-intune-report-export-columns-and-localization-explicit/",
                "headline": "Make Intune report export columns and localization explicit",
                "description": "Will an automated Intune export retain the schema and values its consumer expects?",
                "abstract": "Will an automated Intune export retain the schema and values its consumer expects?",
                "articleBody": "Source facts\nMicrosoft 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.\nApplicability\nUse this design for reports supported by Intune’s export infrastructure. Identify the exact report name and its valid columns before adapting an example request.\nDSE recommendation\nDefine 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.\nVerification\nRun 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.\nOfficial references\nMicrosoft Learn: Use Graph APIs to Export Intune Reports.",
                "datePublished": "2026-09-10T00:23:21+00:00",
                "dateModified": "2026-09-10T02:11:18+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/dse-20260909-515-make-intune-report-export-columns-and-localization-explicit/"
                },
                "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-515-make-intune-report-export-columns-and-localization-explicit/#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": "Make Intune report export columns and localization explicit"
                },
                "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": 227,
                "timeRequired": "PT2M",
                "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": "Use Graph APIs to Export Intune Reports - Microsoft Intune | Microsoft Learn",
                    "url": "https://learn.microsoft.com/en-us/intune/device-management/reports/export-graph-apis"
                }
            }
        ]
    }
}