Learn · Cloud DFIR

Acquiring the Microsoft 365 Unified Audit Log

How do I export the Microsoft 365 Unified Audit Log for an investigation, and what will I be missing?

Updated

  • Microsoft 365
LinkedInXSend to your team
On this page

The Unified Audit Log is where most Microsoft 365 investigations start. It is also where most of them quietly go wrong, because what the log contains depends on licensing, on whether auditing was ever switched on, and on how the export was run.

Check retention before you export

Retention is 180 days on E3 and one year on E5 with Audit Premium. If the incident window predates that, the records are gone and no export will recover them — establish this first so the investigation plan is honest about its own limits.

Export with the Extractor Suite

The Purview UI caps results and truncates large windows without saying so. Use the tooling instead:

PowerShellFull UAL export for a date range
Import-Module Microsoft-Extractor-Suite
Connect-M365

Get-UALAll -StartDate 2026-05-01 -EndDate 2026-08-01 `
  -OutputDir .\ual -Output JSON

# Interval is halved automatically when a window returns the 50k ceiling

What you will still be missing

The UAL records that an action happened. It does not record message content, file content, or — critically — mailbox item access unless Mailbox Auditing was enabled for that mailbox. Confirm the auditing configuration for the accounts in scope before drawing conclusions from absence.