Opselith
POWERSHELL / MICROSOFT.GRAPH.DEVICEMANAGEMENT
ProIntermediateRead-onlylow

Summarize Intune devices by compliance state

Summarize Microsoft Intune managed devices by their current ComplianceState with PowerShell.

Open in PowerShell Builder →Browse all scripts

Generated securely after server-side Pro license validation · Review before running · Opselith does not connect to your tenant

What this PowerShell script does

Summarizes managed devices by compliance state.

Requirements

  • CSV output path - Example: C:\Temp\report.csv

Environment

  • Module: Microsoft.Graph.DeviceManagement
  • Permissions: DeviceManagementManagedDevices.Read.All
  • Output: CSV report
  • Context: PowerShell 7 · Microsoft Graph
  • Risk: Low
Review before you run The script is generated securely after server-side Pro license validation. Test outside production first.
NEXT STEP

Ready to generate

Configure Summarize Intune devices by compliance state in the Builder, review the generated PowerShell and run it yourself in your own PowerShell session.

Configure this script →Open Builder
More about this script

Why use this template?

Use this PowerShell template when you need to summarize managed devices by compliance state. It can be previewed in the Builder; Pro access is required to generate it for your own environment.

The template uses Microsoft.Graph.DeviceManagement and requires DeviceManagementManagedDevices.Read.All. Output: CSV report. Level: Intermediate. Action: Read-only. Risk: Low.

Review before running

The script remains preview-only until Pro access is enabled. Review it before running it, and test it outside production first. “Read-only” describes the script itself; anything you add around it can still change data.

Preview the script

  1. Open the template in the PowerShell Builder.
  2. Review the purpose, requirements, permissions, output and risk.
  3. Activate Pro when you are ready to generate the full script, then test it outside production.

Pro templates remain previewable before purchase or activation. No tenant connection is required. When you generate a Pro script, only the configuration values needed for that template are sent to Opselith after license validation.Preview Summarize Intune devices by compliance state →

How to use this result

Use this report for a quick count of managed-device records grouped by the compliance state Intune currently returns.

When this helps

  • Create a high-level compliance distribution snapshot before investigating individual devices.
  • Compare the relative size of compliant, noncompliant, grace-period and other returned states.

How to read the result

  • The output contains state names and counts only; it does not identify the affected devices or policies.
  • Different states such as unknown, error or conflict should not be silently treated as noncompliant without separate review.

Things to check

  • A summary can hide which policy or setting caused a device-level result.
  • Counts are a point-in-time snapshot and can change as devices sync and policies evaluate.

What to do next: Use the focused non-compliant device report and policy inventory for any state that needs investigation.

Related tasks

Official references

Before you runModule, permissions, inputs, compatibility and script checks
OPS / SCRIPT DETAILS

Script details

Summarizes managed devices by compliance state. Review these details before generating or running the script.

reportingdeviceintuneentracompliance
Generated here. Run by you.Opselith does not connect to your tenant or run PowerShell. After generating, review the script and run it in your own PowerShell session.

What it works with

Module: Microsoft.Graph.DeviceManagement

Microsoft Graph PowerShell lets the script work with Microsoft Entra and Microsoft 365 data through Microsoft Graph.

Context: PowerShell 7 · Microsoft Graph

Compatibility: PowerShell 7 is the supported target for this Microsoft 365 template.

Permissions and changes

Permissions: DeviceManagementManagedDevices.Read.All

Risk: Low

Read-only: designed to collect information without intentionally changing the target environment.

Changes: Read-only. The script reads data and does not intentionally change the target environment.

Inputs

  • CSV output path - Example: C:\Temp\report.csv (Required)

What to expect

Output: CSV report

Expect a CSV file at the path you choose. Open it in Excel or another CSV viewer and review the rows.

Example: C:\Temp\report.csv

This template is in the Pro library. Generating the full script requires eligible Pro or tester access. Opselith receives only the values needed to build the script; it does not connect to your tenant, run PowerShell or store the generated script. You review and run the result in your own PowerShell session.

Example use

Summarizes managed devices by compliance state.

Enter the required values in the Builder, review the generated script and confirm the output before running it.

Before you run: Make sure your account has DeviceManagementManagedDevices.Read.All. Check that the Microsoft.Graph.DeviceManagement PowerShell module is available and that you are using the supported PowerShell version. Review the generated script and output path, then test outside production first.
Script checksWhat has been verifiedQA reviewed
Static checksPassed
PSScriptAnalyzerPending
Real-world run testNot yet recorded
Last checkedNot yet recorded

Real-world run results are shown only after Opselith reviews and accepts a tester report.

Tester: report a result →
TEST STATUSWhat Opselith has checked

Last reviewed: 10 Sept 2026

PSScriptAnalyzer: Awaiting a release PSScriptAnalyzer gate that includes this script. No analyzer pass is claimed yet.

Pending or Not yet recorded means there is no accepted result on file yet. A passed analyzer check does not mean the script has been run in a real tenant.

PRACTICAL GUIDE

How to use this result

Use this compact report to see how managed devices are distributed across the compliance states returned by Intune.

When this helps

  • Create a quick compliance-state baseline before deeper device investigation.
  • Track whether non-compliant or other non-success states are growing between snapshots.
  • Use the state counts to decide which detailed device report to run next.

How to read the result

  • Name is the ComplianceState returned by Microsoft Graph and Count is the number of managed devices currently grouped into that state.
  • States other than compliant should not automatically be collapsed into one meaning; unknown, conflict, error and other values can require different follow-up.

Things to check

  • This is an aggregate count, so it does not identify which policy caused a device state.
  • A compliance-state snapshot can change as devices check in and policies are evaluated.
What to do next: Use the summary to choose the state that needs attention, then run a device-level report before deciding on remediation.
NEXT IN THE LIBRARY

Scripts for similar admin tasks and Microsoft services.

Browse Microsoft Intune PowerShell scripts →
POWERSHELLFind non-compliant Intune devicesintune · find · devicePOWERSHELLExport Intune managed devicesintune · export · devicePOWERSHELLFind duplicate Intune device namesintune · find · device