TenuVaultDesktopPractical guide
Check Intune backup freshness
Check Intune backup freshness in Operations by running Health review for the selected tenant. It checks the latest complete backup and records stale, missing or unreadable evidence. Pro and MSP include scheduled health review and opt-in notifications; a review reads evidence and does not create a new backup.
Can the Intune admin center tell me my backup is fresh?
Native Intune access lets you inspect current policy configuration. A saved Settings Catalog export is a separate file, with its own collection time and scope. Seeing the live policy today does not establish when your external backup last completed or whether you can read it from the recovery location.
Keep backup health separate from tenant configuration health. A tenant may be working normally while its backup schedule has stopped. Equally, a recent backup may faithfully record a configuration problem. Review collection freshness first, then use drift and configuration review for the content of what was collected.
How do I check Intune backup freshness?
1. Select the tenant in the switcher, open Operations and choose Review now under Schedule. Confirm you selected the intended customer before recording the result. Health review is included on Pro and MSP. Community Free still provides manual backups and a weekly scheduled backup, but does not include this health-review workflow.
2. Inspect Last review and its outcome, Evidence from, Scheduling readiness and Open findings. The review checks the latest complete backup: healthy below 24 hours and critical after 48 hours. A recent failed or incomplete run does not substitute for a complete backup; the finding names those recent attempts.
3. Treat Unknown evidence as unresolved. If backup storage cannot be read or sign-in is missing, the review records the reason instead of showing a pass. Restore access, run the review again and record the fresh evidence time. An empty-looking screen during a read failure is not proof of healthy backups.
How do I investigate a stale or missing backup?
Open the finding and inspect the tenant's backup history. Check the last complete run, the latest failed or incomplete attempt and its log. Compare the actual collection time with the planned schedule. Confirm that the operator computer, sign-in and selected storage location match the team's operating procedure.
Run a manual backup after correcting the cause, then inspect its scope and status. Only after the evidence is refreshed should you run Health review again. Findings resolve when a later review reads fresh evidence and reopen when the problem returns. Acknowledging a finding records handling, not recovery.
Assign an Owner and save it when a colleague needs to investigate. Acknowledge the finding to record that it is being handled. Export CSV or JSON when you need a handover record, keeping the evidence date and outcome alongside the customer ticket so the next reviewer can see what was checked.
How do I schedule reviews and notifications?
4. Tick Review on a schedule and choose 6, 12, 24 or 48 hours, or 7 days. Check the readiness tile for Ready, Off, Sign-in required or Not licensed. Reviews run only while TenuVault runs, so make the responsible computer and its expected running time part of the procedure.
5. Add a notification endpoint only if the team wants alerts. Notifications are opt-in and sent for new findings, once until the finding resolves and reopens. Verify the endpoint using the documented Operations procedure. A notification channel supplements review ownership; it does not run a missing backup for you.
Health review also reads stored work signals such as pending upgrades, standard deviations, hygiene findings and old baseline comparisons. Those sources have their own evidence dates. Refresh the owning screen when evidence is stale, then review again. Running a review alone never makes an old comparison or scan newer.
How do I try it on my tenant?
Run one review and save the latest complete backup time and outcome. Inspect a finding through its Open link, refresh the underlying evidence as needed and review again. Then observe a scheduled review while the app runs. Pair this freshness check with a restore drill so your operational record covers both collection and usable recovery.
Read the technical guides
Product scope reviewed . Check your installed release and the current plan table before using a workflow.
Frequently asked questions
Does Review now run an Intune backup?+
No. It reads stored backup listings and work signals. Run a backup separately when collection evidence needs refreshing.
Can unknown evidence count as healthy?+
No. Unreadable evidence is recorded with its reason. Resolve access and review again.
Do scheduled reviews run while the app is closed?+
No. Reviews run only while TenuVault runs. Check Scheduling readiness and the last review time.