Purview & Compliance

Purview audit log: why events are late, missing or already gone

Purview audit log: why events are late, missing or already gone. Purview & Compliance article banner on grbadhon.com

The Purview audit log is where every investigation starts, and it is the first thing to let you down when the event you know happened is not there. Either the record has not arrived yet, or it was never recorded for that user, or it has already aged out. The search screen shows all three the same way, as an empty result, and the fix is different for each.

Most of the causes come back to licensing: who holds E5, which tenants audit by default, and how long each licence keeps a record. That makes this the audit side of Microsoft Purview cost, where the same licence cliffs decide the bill. Every Microsoft fact below was checked against Microsoft Learn on 26 September 2026.

How long before an event shows up in the Purview audit log

For core services Microsoft gives a typical range and then declines to promise it. The Search the audit log article states that for Exchange, SharePoint, OneDrive and Teams, audit record availability is typically 60 to 90 minutes after an event occurs, and that for other services it might be longer. The same article states that Microsoft doesn’t guarantee a specific time after an event for the record to be returned in a search.

That second sentence is the one to quote back to anyone asking for an incident timeline built on the audit log. There is no service level on the page, and none should be implied. Treat anything under two hours as normal and anything longer as a question about the specific service, not about the audit pipeline as a whole.

Is auditing actually on? The check that lies to you

Auditing is not on everywhere by default. Microsoft’s Turn auditing on or off article states that auditing isn’t enabled by default for Small and Medium Business licences, including Microsoft 365 Business Basic, Business Standard and Business Premium, and that unmanaged tenants on free trials of enterprise licences don’t have it enabled by default either. In both cases someone has to turn it on.

The obvious way to check gives the wrong answer in one of the two PowerShell modules. The same article warns that although Get-AdminAuditLogConfig is available in Security & Compliance PowerShell, the UnifiedAuditLogIngestionEnabled property there is always False, even when auditing is turned on. Run the check in Exchange Online PowerShell.

powershell
# Run in Exchange Online PowerShell, not Security and Compliance PowerShell.
# In Security and Compliance PowerShell this property always reads False.
Connect-ExchangeOnline
Get-AdminAuditLogConfig | Format-List UnifiedAuditLogIngestionEnabled

# Only if it reads False. Microsoft says this can take up to 60 minutes
# to take effect, and events can take several hours to become searchable.
Set-AdminAuditLogConfig -UnifiedAuditLogIngestionEnabled $true

Do not expect it to backfill. Nothing in the documentation suggests records are created for activity that happened before ingestion was enabled, and the retention policies that could have kept them are explicitly not retroactive. Assume the gap is permanent and write it into the case notes.

The failure modes

Each row below produces the same symptom in the Purview audit log: an event you are sure of that the search does not return.

What you seeWhat is happeningWhat to do
Mailbox activity missing for some users onlyMailbox audit events return only for users with E5 licences through the portal, the cmdlet or the Management Activity APIEnable auditing on the mailbox explicitly. If it already reads enabled, set it to False and back to True
Nothing at all in a small tenantSMB and trial tenants do not audit by defaultCheck ingestion in Exchange Online PowerShell and enable it
Events older than six months are goneNon-E5 users and guests are retained for 180 daysNothing recovers them. License or add a policy before the next incident
Export has fewer rows than the searchAudit (Standard) exports up to 50,000 records per search. Audit (Premium) raises that to 1,000,000Split the search by date range or by user
PowerShell returns exactly 100 resultsSearch-UnifiedAuditLog defaults to 100, maximum 5,000 per callUse -ResultSize and page with ReturnLargeSet, up to 50,000
Two runs of the same search disagreeWithout HighCompleteness the cmdlet runs faster but may miss resultsAdd the switch for anything that goes into a report
New searches will not startEach admin can run up to 10 search jobs at once, and only one unfiltered searchCancel stale jobs before starting another

The first row is the one that wastes most time, because it looks like a licensing bug and is documented behaviour. Microsoft’s audit troubleshooting scenarios article sets it out: even with mailbox auditing on by default, mailbox audit events return only for E5 users in the unified audit log, and the workaround is Set-Mailbox -Identity <mailbox> -AuditEnabled $true per mailbox. The article adds that if the mailbox already shows auditing enabled and searches still return nothing, you change the value to False and then back to True. That toggle is not something anyone guesses.

The audit log is an input as well as a record. Insider Risk Management reads it for the activity its policies score, so a gap here becomes a silent policy there: what else keeps insider risk alerts from appearing.

Retention by licence: what you keep, and what you cannot get back

The audit log retention policies article describes the default policy in Audit (Premium). It retains Exchange Online, SharePoint, OneDrive and Microsoft Entra audit records for one year, and records for all other activities for 180 days unless a custom policy says otherwise. Non-E5 users and guest users are retained for 180 days.

ScenarioRetention, as documented
Audit (Standard) records created on or after 17 October 2023180 days
Audit (Standard) records created before 17 October 202390 days
E5 users: Exchange, SharePoint, OneDrive and Entra recordsOne year, under the default Premium policy
Custom retention policiesUp to 50 per organisation
3, 5, 7 or 10 yearsRequires the 10-Year Audit Log Retention add-on in addition to E5

Two traps sit in that table. First, a retention policy is not retroactive: Microsoft’s audit solutions overview states that the 10-year policy can’t retain logs generated before the policy was created. Buying the add-on after an incident keeps nothing from before the purchase. Second, the licence that matters is the user’s, not the tenant’s. A tenant with E5 for the security team and E3 for everyone else keeps one year of mailbox evidence for a few people and 180 days for everyone else, and the person under investigation is rarely in the security team. The licence arithmetic is laid out in Microsoft 365 E3 vs E5.

The newsletter

Get the next Purview fix like this one by email

Subscribe and get the free 8-page Intune troubleshooting field guide (PDF), then new fixes about twice a month. From a Microsoft MVP.

Free. Confirm by email, unsubscribe in one click. Privacy.

How to search the Purview audit log, step by step

This is the portal route as Microsoft’s Search the audit log page describes it, checked on 1 November 2026. You need the Audit Logs or View-Only Audit Logs role in the Microsoft Purview portal.

  1. Sign in to the Microsoft Purview portal and select the Audit solution card. If it is not shown, select View all solutions, then Audit under Core.
  2. Set the Date and time range. It is in UTC, defaults to the last seven days, and accepts at most 180 days. If you use the full 180, set the end to the current time or the search errors.
  3. Narrow it. Activities – operations names takes exact operation names separated by commas and returns nothing if one is mistyped, so copy them from Microsoft’s audit activities list. Add Users, Record types, Workloads or a File, folder, or site, where a URL can end in a * wildcard.
  4. Give it a Search name you will recognise later, then select Search.
  5. Open the job from the search job dashboard when its status reaches Completed, filter the items, and use Export for a .csv.

Three limits shape how you run it. A job keeps going after you close the browser, and completed jobs are kept for 30 days. One account can run 10 jobs in parallel, only one of them unfiltered. And Microsoft warns that a broadly scoped job in a large tenant can take up to 48 hours, so a wide first search is the slow way to answer a narrow question. Keyword Search is the other trap: it only searches indexed content in the audit common schema, not the audit data itself, so a keyword that appears only inside an event’s details will not match.

Portal, PowerShell or an export: which one to trust

The portal search covers a maximum date range of 180 days per search, keeps completed search jobs for 30 days, and shows an approximate count once a query returns more than 100,000 results. It requires the Audit Logs or View-Only Audit Logs role in the Purview portal. It is the right tool for a first look and the wrong one for evidence, because the count is approximate and the export is capped.

PowerShell is better for evidence, provided you remove the defaults that hide data. Always set -ResultSize, use -HighCompleteness, and page with ReturnLargeSet. Record the exact command you ran in the case notes, because the same search without those parameters returns a different and smaller answer. If the evidence then goes to a hold or a review set, eDiscovery in Microsoft 365 is where it lands. Check ingestion before a rollout such as sensitivity labels, where you will want a record of who changed what.

What I would do differently

I have not run an incident investigation against this tenant’s Purview audit log. It is a lab, so the judgement below comes from the documentation, not from a case.

Check ingestion on day one of any tenant you inherit, in Exchange Online PowerShell. It costs one command, and the alternative is discovering during an incident that nothing was recorded.

Decide audit retention before an incident, by user, not by tenant. List the roles whose activity you would need a year later: administrators, finance approvers, anyone with access to regulated data. Make sure those people hold the licence that keeps a year. The retention policies cannot reach back, so the decision only has value if it is made early.

Treat the portal count as an estimate and the export cap as a hard edge. Any audit evidence that matters should come from a scripted PowerShell search with the completeness switch, run twice, with both outputs kept. If the two runs disagree, that is itself a finding worth writing down.

Last verified: 1 November 2026 (portal search steps and limits against Microsoft Learn), first verified 26 September 2026.

Common questions

Microsoft Learn states that for core services such as Exchange, SharePoint, OneDrive and Teams, audit records are typically available 60 to 90 minutes after an event, and other services may take longer. Microsoft does not guarantee a specific time, so an incident timeline should never assume a record will be there within a set window.

With the Audit Logs or View-Only Audit Logs role, open the Purview portal, select Audit, set a UTC date range of up to 180 days, add users, exact operation names or record types, name the search and select Search. The job runs in the background, and completed jobs stay available for 30 days.

In the unified audit log, mailbox audit events return only for users with E5 licences, even with mailbox auditing on by default. Microsoft's workaround is to run Set-Mailbox with AuditEnabled set to true on each affected mailbox. If it already shows as enabled and searches still return nothing, set it to false and then back to true.

Audit (Standard) records created from 17 October 2023 are kept for 180 days. Under Audit (Premium), the default policy keeps Exchange, SharePoint, OneDrive and Entra records for one year, while non-E5 users and guests stay at 180 days. Retention of 3 to 10 years requires the 10-Year Audit Log Retention add-on alongside E5.

No. Microsoft Learn states auditing isn't enabled by default for SMB licences, including Business Basic, Business Standard and Business Premium, nor for unmanaged tenants on enterprise trials. Check UnifiedAuditLogIngestionEnabled in Exchange Online PowerShell, because the same property in Security and Compliance PowerShell always reads False.

Audit (Standard) exports up to 50,000 records from a single search, and Audit (Premium) raises the export limit to 1,000,000. Above the limit the CSV does not include all results and might omit some audit logs, so split a large search by date range or by user rather than trusting one export.

The newsletter

Free: the Intune troubleshooting field guide

Subscribe and get my 8-page PDF: 13 common Intune problems, the order to check them in, and the fix for each. Then Microsoft 365 fixes from the field, about twice a month. From G.R Badhon, Microsoft MVP.

  • The field guide, sent the moment you confirm
  • New Intune, Entra ID and Purview guides as they publish
  • One field-tested fix or script per issue

Free. Confirm by email, unsubscribe in one click. Privacy.