What Intune Device Triage helps you do
Helpdesk engineers run one read-only PowerShell collector on a Windows device, drop the redacted haivix-device-diagnostics.json into the browser, and get an explainable health snapshot — enrollment, IME, apps, policies, and Windows — with a score, top findings, and why explanations. Nothing is uploaded to Haivix.
This workflow is designed for browser-first processing, so you can complete the task quickly without sending files off to another dashboard or waiting for an account workflow.
How to use Intune Device Triage
- On the device, run haivix-device-diagnostics.ps1, review the redacted JSON, then import it here.
- Read the health score and top findings first, then expand enrollment, IME, apps, policies, or Windows sections as needed.
- Deep-link into Win32 or Enrollment Troubleshooter for classified next checks.
What you can do with Intune Device Triage
- Download and review a read-only collector with SHA-256 hashing before you run it.
- Redact username, device name, tenant identifiers, serials, and IPs by default.
- Score overall device health and surface up to three priority findings with check-next steps.
- Section enrollment, IME, apps, policies, and Windows signals for quick scanning.
- Deep-link app findings into the Win32 App Troubleshooter and enrollment/MDM findings into the Enrollment Troubleshooter.
Example: Tier 1 triage for a failing Win32 app
On the device, run haivix-device-diagnostics.ps1, review the JSON, then import it here.
Read the top findings first, then open Win32 or Enrollment Troubleshooter for classified next checks.
What to know before you start
- IME log parsing is intentionally coarse — it highlights signals for humans, not a full AppWorkload forensic engine.
- Health scores are Haivix heuristics for triage prioritization, not an Intune portal compliance grade.
- Always review collector output before attaching it to a ticket, even when redaction defaults are on.
Frequently Asked Questions
Read-only signals for Entra join and MDM enrollment, Intune Management Extension health, coarse Win32 app failure hints from IME logs, recent MDM diagnostic events, pending reboot, disk space, OS build, architecture, and uptime.
No. The PowerShell collector writes haivix-device-diagnostics.json on the device. Analysis runs entirely in your browser after you import or paste the file.
Username, UPN/email, device name, tenant name and tenant ID, serial number, and IP/MAC addresses are replaced with REDACTED unless you explicitly re-run with -IncludeSensitive.
It is designed as read-only with no network calls and no changes to enrollment, apps, policies, or services. Still review the script and its SHA-256 hash in the tool before running it in production tenants.
App findings deep-link into the Win32 App Troubleshooter. Enrollment and MDM findings deep-link into the Enrollment Troubleshooter. From there you can continue into Detection or Error Code Explorer.