Opselith
POWERSHELL / MICROSOFT.GRAPH.DEVICEMANAGEMENT
FreeBeginnerRead-onlylow

Find non-compliant Intune devices

Find Microsoft Intune devices in noncompliant or inGracePeriod state and export them to CSV with PowerShell.

Open in PowerShell Builder →Browse all scripts

Generated locally in your browser · Review before running · Opselith does not connect to your tenant

What this PowerShell script does

Finds managed devices that are not compliant.

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 locally. Test outside production first.
NEXT STEP

Ready to generate

Configure Find non-compliant Intune devices 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 find managed devices that are not compliant. It is generated locally and can be reviewed before you run it yourself in your own PowerShell session.

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

Review before running

The script is generated in your browser. Read it before you run it, and test it outside production first. “Read-only” describes the script itself; anything you add around it can still change data.

Generate the script

  1. Open the template in the PowerShell Builder.
  2. Enter the requested values and review the module, permissions, output and risk.
  3. Generate the script, read it carefully, and test it outside production before use.

The script is generated locally in your browser. Nothing needs to be uploaded to Opselith.

Generate Find non-compliant Intune devices →

How to use this result

Use this report to focus on the explicit Intune compliance states the script treats as requiring non-compliance follow-up.

When this helps

  • Create a focused queue of noncompliant and grace-period devices for support or security follow-up.
  • Compare affected device, user, OS and last-sync details before opening policy-specific diagnostics.

How to read the result

  • The script includes complianceState values noncompliant and inGracePeriod.
  • Unknown, conflict, error and configManager states are intentionally not relabeled as non-compliant by this report.

Things to check

  • A device-level compliance state does not explain which policy or setting caused the result.
  • Conditional Access behavior depends on your policy configuration and should not be inferred from this CSV alone.

What to do next: Open the affected device and its compliance-policy details in Intune to identify the specific setting or policy behind the state.

Related tasks

Official references

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

Script details

Finds managed devices that are not compliant. Review these details before generating or running the script.

intunefinddeviceentracompliance
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 Free library and is generated locally in your browser. Opselith does not run it; you review and run the script in your own PowerShell session.

Example use

Finds managed devices that are not compliant.

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.

NEXT IN THE LIBRARY

Scripts for similar admin tasks and Microsoft services.

Browse Microsoft Intune PowerShell scripts →
POWERSHELLFind duplicate Intune device namesintune · find · devicePOWERSHELLFind duplicate Intune serial numbersintune · find · devicePOWERSHELLFind Intune corporate devicesintune · find · device