Practical guide
Intune audit log retention
Intune audit log retention has two documented views: the admin center date range can show logs for the previous year, and Graph returns two years of audit events. Entra audit logs have separate limits of seven days on Free and 30 days on P1 or P2. For a longer investigation history, route audit logs to Azure Monitor and retain configuration backups alongside them.
Also for Mac: Apple silicon · Intel
For Apple silicon Macs.Intel Mac? Get the Intel build
Also for Windows: direct download · Microsoft Store
Send yourself the link and install TenuVault on your computer.
Windows: direct download · Microsoft Store
Mac: Apple silicon · Intel
For Apple silicon Macs.Intel Mac? Get the Intel build
Free to download. Every new tenant starts with 14 days of Pro, with no card and no email. Plans and features
Why can an old policy investigation lose its actors?
You are investigating an old change, but the matching audit event is no longer available. TenuVault reports for older backups can have fewer matching events because Intune and Entra keep audit events for limited periods. Keep the question of who changed something separate from the question of what its configuration was.
How long is Intune audit log retention?
In the Intune admin center, open Tenant administration > Audit logs, select Date and enter the start and end dates. Microsoft says this date range can show logs for the previous year, month, week or day. Its Graph guidance separately says you can get two years of audit events.
Intune auditing is enabled for every customer and cannot be disabled. Audit review requires the Intune Administrator Microsoft Entra role or an Intune role with Audit data - Read permissions.
How long does Entra keep Conditional Access audit events?
Conditional Access changes use the Entra audit log. Its default audit retention is seven days with Microsoft Entra ID Free and 30 days with either P1 or P2. Microsoft documents routing Entra audit activity to Azure storage through Azure Monitor for longer retention.
Upgrading from Free to a premium license does not reveal last month's missing activity. Microsoft says that after the switch you can only see up to seven days of existing data.
How do I keep Intune audit events longer natively?
Use Intune Diagnostics settings to route AuditLogs to a storage account, Event Hubs or Log Analytics. Storage supports archival; Log Analytics supports visualizations, monitoring and alerting. Azure resources have usage costs that vary with tenant size. Set this up before an investigation needs older evidence.
- Open Reports > Diagnostics settings in the Intune admin center. Turn it on the first time, or add a setting.
- Select AuditLogs and the destination for the audit data.
- For a storage account, enter Retention (days). Set it to 0 to keep the data forever.
- Review retention before changing it: the new policy applies to logs collected after the change, while earlier logs are unaffected.
Do audit events contain the full policy?
Audit events describe activities such as creating, editing, deleting and assigning objects. Their actor and target details identify who ran a task and the properties changed. Treat that event record separately from a saved policy configuration.
TenuVault compares saved item fingerprints between backups to identify additions, changes and deletions down to individual settings. Keep both forms of history when you need the event context and the configuration difference.
How do I retain configuration history in TenuVault?
Backup retention controls saved backup folders, not Microsoft audit events. Community keeps backups for up to 30 days; Pro and MSP honor longer selections, including Forever. The default setting is 30 days, and the backup that just finished is never deleted.
- In Settings, open Background runner and find Keep backups for.
- Choose 7, 14, 30, 60, 90, 180 or 365 days, or Forever, within your plan's retention limit.
- For a saved comparison, open Backup & Restore > Backup History, select a backup in Backup Timeline, then choose View Changes in Backup Details.
How do I connect saved changes to audit actors?
Open Reports, choose two complete backups and select Generate report. The report lists added, changed and deleted items, old and new setting values, and matching actors. TenuVault matches audit events between the two backup start times to report items by object ID.
Conditional Access actors require optional delegated AuditLog.Read.All permission. Without it, those items have no actors and the report explains why. If audit logs cannot be read, the report still completes and states that the actors are unknown. Save the result as PDF, Markdown or JSON.
How can I try a longer change history on my tenant?
Download TenuVault, retain two complete backups and compare one policy between them. Generate a report while matching audit events are available, then save it with your investigation notes.
TenuVault's own audit log records its operations, rather than a complete tenant audit. It does not show changes made in the Intune admin center, by other tools or by other administrators.
Read the technical guides
- Microsoft: Intune audit log views
- Microsoft: diagnostic log routing and retention
- Microsoft: Entra activity retention
- Change reports
- Backup retention
Product scope reviewed . Check your installed release and the current plan table before using a workflow.
Frequently asked questions
Does choosing Forever preserve Microsoft audit events?+
Forever applies to TenuVault backup folders. It does not extend Microsoft audit event availability; configure native log archival separately.
Can an old backup report still identify the admin?+
Only where matching audit evidence is available. Older backup periods can have fewer matching events, and unreadable logs leave actors unknown with an explanation.
Does changing diagnostic retention update earlier logs?+
Microsoft applies a revised diagnostic retention policy to logs collected after the change. Logs collected earlier keep their existing treatment.
Can I compare backups on Community?+
Backup comparison is included in Community, Pro and MSP. Community backup history is limited to 30 days.
