Microsoft 365 audit logs provide a searchable record of many user, administrator, application, and service activities. They are useful when you need to investigate a suspicious sign-in, confirm a mailbox or SharePoint change, review a file-sharing event, or preserve an initial incident timeline. This guide shows how to run a focused search in the Microsoft Purview portal and export the results without overstating what the audit log can prove.
Before you start
- Use an account assigned the Audit Logs or View-Only Audit Logs role in Microsoft Purview. A custom role group can include one of those roles.
- Use a supported Microsoft 365 or Office 365 subscription. Retention depends on the license assigned to the relevant users. Microsoft documents 180 days for users with other supported non-E5 licenses and one year by default for users with Microsoft 365 E5, Office 365 E5, or qualifying Purview add-ons.
- Know the approximate time window, user, workload, file, site, or activity you are investigating. Microsoft presents search times in UTC.
Important: An audit result is evidence of a recorded activity, not proof of the person’s intent. Correlate it with sign-in, device, mailbox, endpoint, and network evidence before making a security decision.
1. Confirm that unified audit ingestion is enabled
Audit search is normally enabled in Microsoft 365 enterprise environments, but confirm the setting before troubleshooting an empty result. Connect to Exchange Online PowerShell, not Security & Compliance PowerShell, and run:
Get-AdminAuditLogConfig | Format-List UnifiedAuditLogIngestionEnabled
A value of True indicates that unified audit log ingestion is enabled. Do not disable the setting as a troubleshooting experiment. If it is disabled, an appropriately privileged administrator can re-enable it with:
Set-AdminAuditLogConfig -UnifiedAuditLogIngestionEnabled $true
2. Open the Audit solution
- Sign in to the Microsoft Purview portal.
- Open Solutions, then select Audit. If the card is not visible, select View all solutions and find Audit under the Core section.
- Open the search page and give the search a descriptive name, such as
Investigate-JaneDoe-SharePoint-2026-11-17.
3. Build a focused search
Start narrow and widen the query only when needed. The portal supports these useful criteria:
- Date and time range: Enter the smallest useful UTC window. The portal search supports up to 180 days. Broad searches can take much longer in large tenants.
- Users: Select one or more accounts. Leave this blank when you are looking for activity by any user or service account.
- Activities: Select friendly activity names from the list, or enter exact operation names when you know them. A misspelled operation name returns no results.
- Record types and workloads: Use these to narrow the search to services such as Exchange, SharePoint, OneDrive, Teams, or directory activity.
- File, folder, or site: Enter part of a name or URL when investigating a particular location. A site URL can use a trailing wildcard, such as
https://contoso.sharepoint.com/sites/Finance*. - Administrative units: Use this when the investigation must be limited to an administrative unit. A restricted administrator cannot necessarily search every account or system activity in the tenant.
Select Search and leave the search job running. The browser window does not have to remain open. Completed search jobs are retained in the portal for 30 days.
4. Review the results and activity details
Check the job status, search time, result count, and UTC timestamps. In the result list, compare the user, IP address, record type, activity, item, and workload. Open an individual activity for additional details. Look for a coherent sequence rather than treating a single row as conclusive.
For example, a suspicious SharePoint download is more meaningful when its time, user, IP address, device sign-in, and related file operations line up. A missing event does not prove that the activity did not happen because audit records may not be available immediately.
5. Export the evidence
- Open the completed search job.
- Apply the result filters needed for your review, but record the original search criteria separately.
- Select Export and save the CSV in a restricted investigation location.
Microsoft documents export limits of up to 50,000 rows for Audit (Standard) and up to 1,000,000 rows for Audit (Premium). Preserve the original CSV, the search name, the UTC time window, the operator, and the tenant involved. Do not email sensitive exports as ordinary attachments.
Common problems
The search returns no results
Check the time zone, shorten the date range, remove the activity filter, and verify the user or workload spelling. Confirm that the event is covered by the selected license and that audit ingestion was enabled when the activity occurred. Core-service records commonly appear after 60 to 90 minutes, but Microsoft does not guarantee a fixed delay.
The activity name is not available
Use the official audit activities reference to identify the exact operation name and the associated record type. Friendly names and operation names are not interchangeable.
The admin cannot see all results
Review administrative-unit scope and the assigned audit role. Restricted administrators may only search and export user-generated audit logs within their assigned scope. Use an unrestricted, appropriately authorized investigator when the incident requires tenant-wide coverage.
Security and retention notes
Audit logs are not a substitute for a backup, an immutable evidence store, or a full SIEM. Export sensitive results only to an access-controlled location and apply your organization’s retention and legal-hold requirements. Do not grant global administrator rights merely to make audit search work.
Related Guava guidance
- Responding to a Compromised Email Account in Office 365
- Could Your Business Recover Its Microsoft Cloud Data?

