Necessary

Keeps you signed in to the customer portal and remembers your cookie choice. These functions do not use Google Analytics.

Always on

Read the Cookie Notice

Microsoft 365 Securitybeginner

How Long Does Microsoft 365 Keep SharePoint Audit History?

Learn how long Microsoft 365 keeps audit records with Audit (Standard) and Audit (Premium). See what the 10-year add-on covers, why some changes appear late and why audit records do not give you a full history of permissions.

Published Updated Microsoft documentation checked on 9 min read

The short answer: 180 days with Audit (Standard), one year with Audit (Premium), and up to ten years with the additional retention add-on license. The longer answer matters because those numbers describe how long event records survive, and event records are not the same thing as a history of who had access.

This guide lays out the retention rules as Microsoft documents them (search the audit log and audit log retention policies), the practical caveats, and what you have to do yourself if you need to answer questions further back.

Retention by licensing tier

Microsoft Purview Audit comes in two tiers, and the tier is determined per user by licensing.

TierTypical licensingDefault retentionNotes
Audit (Standard)Microsoft 365 E3 / Business Premium and similar180 daysIncreased from 90 days for records generated on or after October 17, 2023
Audit (Premium)Microsoft 365 E5 / Microsoft Purview Suite / eDiscovery and Audit add-on1 year for Exchange, SharePoint, OneDrive and Entra ID recordsOther activities 180 days unless a retention policy says otherwise
Audit (Premium) plus 10-Year Audit Log Retention add-onE5 plus add-onUp to 10 years, through a retention policyAdd-on for the users whose activity is kept

Actual retention depends on the license assigned to the user whose activity was recorded, the record type and any applicable retention policy. Records from applications and other non-user entities are kept for one year.

Two details trip people up:

  • Retention is evaluated per user, by the license of the user who performed the action, not by the tenant. In a mixed tenant, an E5 administrator's actions are kept for a year while an E3 site owner's actions are kept for 180 days.
  • Changes are not retroactive. The increase from 90 to 180 days applied to records generated on or after October 17, 2023, and a license or policy change does not extend records already committed.

Always confirm the current values against Microsoft's documentation for your tenant's licensing; Microsoft has changed these numbers before and will again.

What "audit retention" actually retains

The Unified Audit Log stores events: a record that something happened, when, by whom, to what. For SharePoint permissions that means operations such as SharingInheritanceBroken, AddedToGroup and the sharing link events (Microsoft lists them all in its audited activities). For Entra ID it means Add member to group. and its relatives.

Audit records show actions that occurred, not a complete list of every permission at every moment. SharePoint Advanced Management also offers point-in-time permission reports. Saved copies of those reports can help with later questions, but neither source automatically provides a complete historical view for every file and date. To answer for a past date you need a baseline from around that time plus the changes since, as described in How to Audit Historical SharePoint Permissions.

Audit retention and permission snapshots are different things. Purview retains records of activities. SharePoint Advanced Management reports capture permission information at a particular point in time. You may need both kinds of evidence to investigate earlier access.

Audit delay: how soon does an event appear?

Audit records are not written synchronously with the action. For core services such as SharePoint and OneDrive, Microsoft says a record is typically available 60 to 90 minutes after the event; other services can take longer, and Microsoft does not commit to a specific time. Anything built on the audit log has to allow for that delay.

Practical consequences:

  • Do not treat absence as evidence for recent time windows. If you search for a change made twenty minutes ago and find nothing, that is not proof it did not happen.
  • Order by the event's own timestamp, CreationDate or CreationTime, not by when your export ran.
  • Overlap your export windows so a record that arrived late still lands in a later export.
  • Expect corrections. An answer you worked out at 10:00 may need revising at 11:00 when a delayed record arrives. Keep the revision, do not overwrite it.

The Entra ID audit log is a separate clock

Directory group membership changes appear in two places: the Unified Audit Log (Azure Active Directory workload, subject to the retention above) and Entra ID's own audit log in the Entra admin center. Entra ID's log retains 30 days with Entra ID P1 or P2 licensing and 7 days on the free tier (Microsoft Entra data retention). If you rely on the Entra ID portal for group history, your window is much shorter than the Unified Audit Log's.

Checking what your tenant actually has

Verify that auditing is on and see what the search returns for your oldest window:

Connect-ExchangeOnline
Get-AdminAuditLogConfig | Select-Object UnifiedAuditLogIngestionEnabled

# Probe the edge of retention: does anything come back from ~180 days ago?
$end   = (Get-Date).ToUniversalTime().AddDays(-178)
$start = $end.AddDays(-2)
Search-UnifiedAuditLog -StartDate $start -EndDate $end -RecordType SharePointSharingOperation -ResultSize 10 |
  Select-Object CreationDate, Operations, UserIds

If auditing was ever switched off, there is a gap for that period that no license will fill.

To see which users are on which tier, check assigned licenses: the license of the person who acted decides how long their records are kept.

Extending your history beyond retention

If the questions you need to answer go further back than your retention, or need state rather than events, you have three options:

  1. Buy longer retention. The 10-year add-on extends event retention, but still only events, and only for licensed users.
  2. Export continuously and keep the exports. A scheduled export, run daily with overlapping windows, gives you an event archive under your own retention policy. Store it in your own database with the raw AuditData preserved. For programmatic extraction Microsoft recommends the Office 365 Management Activity API rather than a PowerShell script.
  3. Take periodic permission baselines alongside the exports. Baselines plus the recorded changes are what let you answer for a past date, rather than only list changes.

An introductory daily export with Exchange Online PowerShell. It is an example, not a complete archive: check that each run returned everything, because one session stops at 50,000 results.

$stamp = Get-Date -Format "yyyyMMdd"
$start = (Get-Date).ToUniversalTime().Date.AddDays(-2)   # two-day overlap for late arrivals
$end   = (Get-Date).ToUniversalTime()
foreach ($recordType in "SharePointSharingOperation", "SharePointFileOperation") {
  $sessionId = "spo-audit-$stamp-$recordType"
  do {
    $batch = Search-UnifiedAuditLog -StartDate $start -EndDate $end -RecordType $recordType `
      -SessionId $sessionId -SessionCommand ReturnLargeSet -ResultSize 5000
    $batch | Export-Csv "ual-spo-$stamp.csv" -Append -NoTypeInformation
  } while ($batch)
}

Deduplicate on the record Identity when you load the overlapping windows.

FAQ

Does turning on Audit (Premium) recover older records?
No. Retention applies going forward from when the record was created under the applicable tier. Records that already expired are gone.
Are SharePoint file access events kept for the same period?
Yes. FileAccessed, FileDownloaded and similar operations are ordinary audit records under the SharePoint workload and follow the same tier-based retention as permission operations.
Is the audit log a legally sufficient record of who could access data?
That is a question for your auditors and counsel, but technically the log records changes, not entitlements. A defensible entitlement history needs baselines as well as events.
auditretentionmicrosoft-purviewsharepoint-online
All guides
  • Microsoft 365 Security9 min readbeginner

    Does Microsoft 365 Copilot Respect SharePoint Permissions? What Can It See?

    Copilot follows SharePoint permissions, so it only shows each person what they can already open. Learn what that includes, when a sharing link counts, how to find content open to everyone, and how to limit what Copilot finds while you fix it.

  • Compliance & Audit10 min readintermediate

    How to Export SharePoint Online Permissions for an Audit

    Export SharePoint permissions with Microsoft's reports or a tested PowerShell script, see what each export leaves out, and save a dated baseline you can compare later.

  • Historical Access12 min readadvanced

    How to Audit Historical SharePoint Permissions

    SharePoint shows current permissions. Learn what Microsoft's audit log and snapshot reports can tell you about a past date, how to save permission records with PowerShell and how to explain when information is missing.