What Intune Policy Export Comparator helps you do
Review Intune policy changes without drowning in object ordering, generated IDs, timestamps, and Graph envelope metadata. This comparator aligns array objects by setting or assignment identity, classifies meaningful changes, prioritizes security-sensitive paths, redacts likely secrets, and creates a change-control report entirely in the browser.
Check the tool page and Privacy Policy for how this workflow handles your input.
How to use Intune Policy Export Comparator
- Export or paste the baseline and candidate Intune policy JSON, keeping metadata suppression and identifier-aware array matching enabled for a semantic review.
- Compare the exports, then filter by settings, assignments, or security-sensitive changes and investigate each high-impact difference.
- Download the redacted Markdown report for change control, and verify assignments, filters, applicability, and device behavior before rollout.
What you can do with Intune Policy Export Comparator
- Compare JSON objects, arrays, and common Microsoft Graph value envelopes.
- Ignore volatile IDs, timestamps, versions, scope tags, and pagination metadata when appropriate.
- Align settings and assignments by stable identifiers instead of array position.
- Filter changes by setting, assignment, metadata, path text, or security impact.
- Export a redacted Markdown report plus normalized baseline and candidate JSON.
Example: review a policy before production promotion
Paste the current production export on the left and the pilot or replacement export on the right. Keep semantic normalization enabled unless array order or generated metadata is explicitly part of the contract you are reviewing.
Start with security-sensitive and assignment changes, then review the remaining setting differences. Attach the redacted Markdown evidence to change control and verify filters, applicability, licensing, conflicts, and test-device behavior separately.
What to know before you start
- This is a semantic JSON comparison, not an effective-policy or assignment-resolution engine.
- Secret detection is heuristic; inspect every report before posting it to a ticket, repository, or chat.
- Disabling volatile-field suppression is useful for forensic export comparison but creates much noisier results.
- Different Graph endpoints can represent equivalent settings with different schemas, which may require export normalization before comparison.