# Intune Drift Detection: See What Changed | TenuVault

Compare Intune configuration backups and inspect changed settings with TenuVault. Export JSON or CSV reports and review recovery options for policy drift.

Canonical: https://www.tenuvault.com/intune-drift-detection

TenuVault Desktop

# Intune drift detection: see what changed, down to the setting

Intune drift detection in TenuVault compares your two newest complete backups to find added, changed and deleted items. It shows the setting differences so you can investigate the change and choose a supported recovery action.

[Download for Windows](https://www.tenuvault.com/download/windows)[![Get it from Microsoft](https://www.tenuvault.com/_next/image?url=%2Fdesktop%2Fmicrosoft-store-badge.png&w=1920&q=75)](https://apps.microsoft.com/detail/xpfp6qq47l0gdk?cid=website-intro)

[Download for Mac](https://www.tenuvault.com/download/mac-arm64)

For Apple silicon Macs.Intel Mac? [Get the Intel build](https://www.tenuvault.com/download/mac-x64)

Free to download. Every new tenant starts with 14 days of Pro, with no card and no email. [Plans and features](https://www.tenuvault.com/pricing)

## At a glance

-   TenuVault drift detection compares the two newest complete backups of a tenant, not the live tenant, so run a backup first to include the latest changes.
-   Changed items show each changed setting with its old and new value; added and deleted items are listed separately.
-   Drift findings export as JSON or CSV on every plan; one click revert of drifted policies requires Pro or MSP.
-   A drift result shows that saved configuration changed; it does not prove the change was unauthorized or that devices applied it.

![TenuVault Desktop drift report comparing Intune configuration snapshots](https://www.tenuvault.com/_next/image?url=%2Fdesktop%2Fscreens%2Fdrift-dark.webp&w=3840&q=75)

Product screenshot with fictional demo data. Snapshot comparison describes saved configuration, not live device enforcement.

## Use version history to undo a policy change

Backup history gives you saved versions to inspect before recovery. Compare the changed settings, choose a snapshot from before the mistake and review the restore. Community can create a policy copy; Pro and MSP can replace supported policies in place.

For several customer tenants, assess each tenant against the intended baseline as well as checking its backup drift. A time comparison within one tenant does not establish that every customer follows the same standard.

-   [Roll back an unwanted policy edit](https://www.tenuvault.com/guides/roll-back-intune-policy-change)
-   [Browse policy version history](https://www.tenuvault.com/guides/intune-policy-version-history)
-   [Manage customer baselines](https://www.tenuvault.com/solutions/msps)

## Compare configuration at the setting level

Drift detection requires two backups of the same tenant. Added and deleted policies are listed separately from changed policies, and changed items expose old and new values where supported.

A difference tells you that the saved configuration changed. It does not establish that the change was unauthorized, that it reached every device, or that an endpoint is compliant.

-   [What drift detection compares](https://docs.tenuvault.com/drift/#what-drift-detection-compares)

## Keep your evidence current

The comparison can only see changes captured in the snapshots. Run a fresh backup when investigating an incident and inspect backup completeness before interpreting the report.

Schedule weekly backups on Community or daily backups on Pro and MSP. Authentication, permissions, storage and an awake computer remain prerequisites. Choose a schedule that fits your recovery requirements.

-   [Backup setup and scheduling](https://www.tenuvault.com/guides/intune-backup-setup)

## Export findings and review a response

Export drift findings as JSON or CSV for a change ticket or investigation. Community can restore a previous item as a copy; Pro and MSP add supported in-place reversion.

Review what the recovery operation will change and whether assignments or dependencies need attention. Use a pilot group or an unassigned copy to validate the result before expanding a rollout.

-   [Understand policy restore](https://www.tenuvault.com/intune-restore)
-   [How TenuVault backs up Intune](https://www.tenuvault.com/intune-backup)

## Validate a baseline separately

Backup drift compares your saved tenant configuration across time. OpenIntuneBaseline validation instead compares deployed policies with a selected upstream baseline version.

Use the workflow that matches the question: what changed in the tenant, or where configuration differs from the baseline. Neither workflow claims framework certification or device enforcement.

-   [OpenIntuneBaseline workflows](https://www.tenuvault.com/openintunebaseline)

## Read the technical guides

-   [Drift detection guide](https://docs.tenuvault.com/drift/)
-   [Compare backups](https://docs.tenuvault.com/backups/compare/)

Product scope reviewed 13 November 2026. Check your installed release and the current plan table before using a workflow.

## Frequently asked questions

### Q: How does TenuVault detect Intune configuration drift?

A: 

TenuVault compares the two newest complete backups of an Intune tenant and lists added, modified and deleted items. Backups that failed, completed with warnings or are incomplete are skipped, because missing items would otherwise appear as deleted.

### Q: Does Intune drift detection in TenuVault check the live tenant?

A: 

No. TenuVault compares saved backups, not the live Intune tenant. Run a fresh backup before you investigate so the comparison includes the latest changes.

### Q: Can I revert an Intune change that drift detection found?

A: 

Yes. On every TenuVault plan you can restore the previous version of an Intune item as a copy. Pro and MSP add one click revert, which puts the drifted policy back to its backed-up version in place.

### Q: Is drift detection included in TenuVault Community?

A: 

Yes. TenuVault Community compares backups and shows Intune drift with setting diffs for one tenant. Community schedules weekly backups, so drift is found at most as often as backups run unless you start one manually.

### Q: How is backup drift different from OpenIntuneBaseline validation?

A: 

Backup drift compares your saved Intune configuration across time. OpenIntuneBaseline Policy Validation compares deployed policies with a selected upstream baseline version. TenuVault offers both, and neither proves device enforcement or compliance certification.

## Related guides

-   [How to detect configuration drift in Intune](https://www.tenuvault.com/guides/detect-intune-configuration-drift)
-   [Intune policy version history](https://www.tenuvault.com/guides/intune-policy-version-history)
-   [Intune audit logs and diffs or drift detection](https://www.tenuvault.com/compare/intune-drift-audit-logs-vs-backup-comparison)
-   [Intune audit logs or a backup](https://www.tenuvault.com/compare/intune-audit-logs-vs-intune-backup)

## Review your setup before the first change

Community is free for one tenant. Try Pro free by connecting a new tenant in the app, no email or card needed. Tenant access, supported restore types and scheduling requirements still apply.

[Start free trial](https://www.tenuvault.com/trial?src=cta)[Book a 30-minute demo](https://cal.com/ugur-koc/tenuvault-demo)[Permissions and data flows](https://www.tenuvault.com/trust)
