Black Friday sale: an extra 40% off every course until Monday, November 30.New Year sale: an extra 30% off every course until Friday, January 1.Memorial Day sale: an extra 25% off every course until Monday, May 31.SysAdmin Day sale: an extra 25% off every course until Sunday, August 1.Back to School sale: an extra 25% off every course until Sunday, August 22.Labor Day sale: an extra 25% off every course until Monday, September 6.Black Friday sale: an extra 40% off every course until Monday, November 29.New Year sale: an extra 30% off every course until Saturday, January 1.Choose your certification →

Copyright (c) 2026 MindMesh Academy. All rights reserved. This content is proprietary and may not be reproduced or distributed without permission.

6.2.1. Intune Reports, Exports, and Workbooks

💡 First Principle: Reports differ in who they serve and how fresh they are. A help desk agent needs a live list of which devices are failing right now; a manager needs a summary; a security team wants the raw data to join with their own. Intune builds separate report types for each of those audiences, so the first step in any reporting question is to work out who's asking and what they'll do with the answer.

Four report types. Intune sorts its reports into four categories:

TypePurposeExamplesHow to get data out
OperationalTimely, actionable lists for help desk and adminsNoncompliant devices, Enrollment failures, Configuration policy assignment failures (Devices > Monitor)Export from the report, or Graph exportJobs
OrganizationalBroad summaries of the estateDevice compliance, Profile configuration statusExport, or Graph exportJobs
HistoricalTrends over timeDevice compliance trends (30 days)Export
SpecialistRaw data for custom reportsAzure Monitor workbooks over Log AnalyticsDiagnostic settings to Log Analytics, storage or an event hub

All reports support search and sort on any column, paging and export. The least-privileged built-in role that can review them is Read Only Operator.

Filtering and generating. Organizational reports such as Device compliance (Reports > Device compliance > Reports tab) let you filter on compliance status, OS and ownership, then select Generate report; the report shows when it was last generated, so a stale view is easy to spot. Exports keep the report's current search and filter, so if you filtered to OS = Windows and searched "PC", the CSV contains only those rows.

The reports that answer common symptoms:
  • Which setting makes this device noncompliant? Noncompliant devices and settings gives one row per device per failing setting, including custom compliance settings.
  • Are unassigned devices slipping through? Devices without compliance policy also shows the tenant setting Mark devices with no compliance policy assigned as, which defaults to Compliant (Microsoft recommends Not compliant).
  • Why didn't a profile apply? Configuration policy assignment failures (Devices > Monitor) lists profiles with devices in error or conflict. Profile configuration status filters profiles by success, error, conflict or not applicable, and a single profile's Per setting status pinpoints the conflicting setting.
  • Why can't users enroll? Enrollment failures (Devices > Monitor) shows failed enrollment attempts, alongside Windows Autopilot deployments (last 30 days) and Enrollment time grouping failures.
  • Who wiped that device? The Device actions report keeps 180 days of remote actions, and Tenant administration > Audit logs, which can't be disabled, records every create, update, delete, assign and remote action.

One policy-interaction rule shows up in these reports: when a compliance policy and a configuration profile set the same thing, the compliance setting wins, and across multiple compliance policies the most secure value applies.

Automated exports with Graph. For the Monday-morning CSV from 6.1.1, post to deviceManagement/reports/exportJobs with a reportName, plus optional filter, select and format (CSV by default, or JSON). Poll the job until its status is completed, then download the zipped file from the returned URL before it expires. Select explicit columns rather than relying on a report's defaults, which can change. Throttling is 100 requests per tenant per minute, 8 per user and 48 per app.

Workbooks, Log Analytics and the Data Warehouse. For custom dashboards, history beyond the built-in reports, or alerting, send Intune data to Azure Monitor. In Reports > Diagnostics settings > Add diagnostic setting, choose the log categories (AuditLogs, OperationalLogs, DeviceComplianceOrg, IntuneDevices) and a destination: Send to Log Analytics for queries, workbooks and alerts, Archive to a storage account for retention, or Stream to an event hub for a SIEM such as Splunk or QRadar. This needs an Azure subscription, the Intune Service Administrator role and Log Analytics Contributor on the workspace. Audit and operational logs flow immediately; compliance and device inventory data is sent once every 24 hours and can take up to 48. The Intune Data Warehouse offers daily-refreshed historical data through an OData feed (Reports > Intune Data warehouse) that Power BI or any OData v4 client can read.

⚠️ Exam Trap: If a requirement says "build a custom dashboard" or "query Intune data with KQL alongside other Azure data", the built-in reports and CSV exports aren't enough. The answer is a diagnostic setting sending data to a Log Analytics workspace, with Azure Monitor workbooks on top, and that requires an Azure subscription.

Reflection Question: A compliance manager wants a 90-day view of compliance by department, refreshed automatically, in Power BI. Which report source would you use, and why aren't the Device compliance trends report or a manual export the right fit?

See how it connects
Alvin Varughese
Written byAlvin Varughese
Founder•26 professional certifications earned