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.

SharePoint shows the permissions assigned today. To investigate who had access on an earlier date, look for permission records saved at the time and the changes recorded since. Microsoft Purview audit logs and SharePoint Advanced Management reports can help, but their coverage and retention limits matter.
An auditor asks: "Who could read the payroll folder on 14 February?" SharePoint can tell you who can read it now. Answering the question means reconstructing the state from whatever evidence you have, and being explicit about how good that evidence is.
This guide covers what is possible with Microsoft's own tooling, what you need to keep, and where it runs out.
What SharePoint does and does not keep
Current permissions: SharePoint shows the permissions, groups and sharing links that apply now. When a role assignment is removed, it no longer appears in the current permissions view. An earlier saved report or audit record may still provide evidence of the change.
Saved permission reports: SharePoint Advanced Management can generate reports showing site permissions across an organization and the sites accessible to selected users. These reports record a point-in-time view that can be kept for later reference.
Audit events: Microsoft Purview records many permission and sharing changes, along with available information about who made them and when. How long those events remain available depends on licensing and retention policies. See How Long Does Microsoft 365 Keep SharePoint Audit History? for the details.
Together, these can help answer historical questions. A complete answer depends on having enough earlier state and change records; an audit event by itself is not a complete permission snapshot.
So a historical audit has two ingredients: a known state at some point (a baseline) and an ordered list of changes (events) between that point and the date in question. A saved baseline gives you a known permission state. Recorded changes help explain how that state changed. If either is missing, some historical questions may remain unanswered.
Microsoft's permission snapshot reports
SharePoint Advanced Management provides two reports worth checking before building your own collection process.
The Site permissions across your organization report shows site-level permission information, including counts of users, guests, groups and sharing links. It helps find sites that may be broadly shared, but it does not list every person's complete access to every file.
The Site permissions for users report shows which sites selected users can access, including whether that access covers a whole site or specific items. If you generated and kept this report earlier, it can help answer questions about those users at that time.
These reports depend on the required Microsoft licensing and data collection. Microsoft says each report captures data from up to 48 hours before it is generated, and that you can run it again every 30 days.
They are useful baselines, but they are not a way to select any past date and recreate a full history of file permissions. For dates between reports, you still need enough change records to explain what happened.
Why historical permissions are difficult to reconstruct
An audit log tells you which changes were recorded. It does not automatically tell you the complete permissions before or after each change. A reliable historical answer also needs a known permission state, group membership information and enough records to account for changes between dates.
Missing or delayed events make the answer less certain. If the evidence is incomplete, the result must say so. And if you are asked about a date before the first permission state you captured, the honest answer is that you do not know. Do not extrapolate backwards.
Step 1: Take baselines
A baseline needs to capture, per site collection:
- Every securable object with unique permissions, with its role assignments (principal, role definitions).
- Every SharePoint group with its direct members.
- Every Entra ID security group and Microsoft 365 group referenced, with transitive membership at that instant.
- Every sharing link (the
SharingLinks.*groups) with its scope and members.
An introductory PnP PowerShell example for the list items with unique permissions in one site. It needs an account (or app) that can read every list in the site, and it is not a complete baseline: it skips hidden lists, and it does not cover the site and list level or expand any groups.
Connect-PnPOnline -Url $SiteUrl -Interactive -ClientId $ClientId
$capturedAt = (Get-Date).ToUniversalTime().ToString("o")
$rows = foreach ($list in Get-PnPList -Includes HasUniqueRoleAssignments, RoleAssignments) {
if ($list.Hidden) { continue }
$items = Get-PnPListItem -List $list -PageSize 2000 -Fields "FileRef","HasUniqueRoleAssignments"
foreach ($item in $items | Where-Object { $_["HasUniqueRoleAssignments"] }) {
$ras = Get-PnPProperty -ClientObject $item -Property RoleAssignments
foreach ($ra in $ras) {
Get-PnPProperty -ClientObject $ra -Property Member, RoleDefinitionBindings | Out-Null
[pscustomobject]@{
CapturedAtUtc = $capturedAt
Site = $SiteUrl
Resource = $item["FileRef"]
Principal = $ra.Member.LoginName
PrincipalType = $ra.Member.PrincipalType
Roles = ($ra.RoleDefinitionBindings | ForEach-Object Name) -join ";"
}
}
}
}
$rows | Export-Csv "baseline-$($capturedAt -replace '[:.]','-').csv" -NoTypeInformation
Add the web-level and list-level role assignments, then the group expansions from the group comparison guide. Store timestamps in UTC so daylight-saving changes do not make historical comparisons ambiguous.
Take baselines on a schedule. Weekly is a reasonable starting point; the shorter the gap, the fewer changes lie between a baseline and the date you are asked about.
Step 2: Export the events continuously
Retention is the enemy here. A retention window of 180 days means an event export you did not run in time is lost. Export on a schedule and keep the results.
An introductory example using the Exchange Online PowerShell module. For regular, programmatic extraction Microsoft recommends the Office 365 Management Activity API over a PowerShell script; the operation names below are from Microsoft's list of audited activities.
Connect-ExchangeOnline
$start = (Get-Date).AddDays(-1).ToUniversalTime()
$end = (Get-Date).ToUniversalTime()
$ops = @(
"SharingInheritanceBroken","SharingInheritanceReset","PermissionLevelsInheritanceBroken",
"AddedToGroup","RemovedFromGroup","GroupAdded","GroupRemoved",
"SharingSet","SharingRevoked","SharingInvitationCreated",
"SecureLinkCreated","SecureLinkDeleted","AddedToSecureLink","RemovedFromSecureLink",
"CompanyLinkCreated","CompanyLinkRemoved","AnonymousLinkCreated","AnonymousLinkRemoved",
"SiteCollectionAdminAdded","SiteCollectionAdminRemoved"
)
$sessionId = [guid]::NewGuid().ToString()
$all = do {
$batch = Search-UnifiedAuditLog -StartDate $start -EndDate $end `
-Operations $ops -SessionId $sessionId -SessionCommand ReturnLargeSet -ResultSize 5000
$batch
} while ($batch)
$all | Select-Object CreationDate, Operations, UserIds, AuditData |
Export-Csv "spo-events-$($start.ToString('yyyyMMdd')).csv" -NoTypeInformation
Run a second query with -RecordType AzureActiveDirectory for Add member to group. and Remove member from group. so directory group changes are captured too. Microsoft says to run the same search until it returns nothing, and one session stops at 50,000 results, so split wide windows and check that each export really is complete. You may also see operation names that are not in Microsoft's list (sharing with a specific person produced SharingLinkCreated in our test tenant); keep everything the search returns rather than only the names you expected.
The AuditData JSON carries the details, as described in Microsoft's audit log schema: ObjectId (the resource URL), and for sharing events TargetUserOrGroupName and EventData with follow-up detail such as the permission granted. Parse it once and store it in columns, and keep the raw record too.
Step 3: Work forward to the date in question
Start from the nearest baseline before the date and go through the recorded changes between the two, in order. Each record needs reading on its own terms (see How to Investigate Who Changed SharePoint Permissions): some name the person and the permission, some only say that something changed, and some changes, such as the permissions copied when inheritance is broken, may have no record of their own.
Then answer the specific question, "could Alex read Payroll," by walking the chain exactly as in How to Find Out Why a User Has Access to a SharePoint Site, but against the state you worked out instead of live SharePoint. Where a step depends on a change you cannot account for, the answer is incomplete, and it should say so.
Step 4: State the confidence
Attach a confidence label to every answer and mean it:
- Verified snapshot: the date coincides with a baseline; the answer was directly observed.
- Reconstructed: the answer was derived from a baseline and the recorded changes since, with evidence for each step.
- Partial: some evidence exists, but one or more permissions, memberships or changes could not be fully confirmed for that time, for example a nested group whose membership was first captured after the date, or a kind of change you were not exporting.
- Unknown: there is not enough reliable evidence to determine access at that time, for example because the date is before your earliest baseline and no recorded change accounts for it.
When the next baseline disagrees with the state you worked out, you have found a missed event or an ambiguity. Record the discrepancy as a correction rather than silently adjusting; the audit trail of your audit matters too.
Where the manual approach breaks
It works for one site and one question. It does not scale to a tenant with thousands of unique-permission objects, dozens of directory groups per site and a 180-day retention clock ticking on every event. The scripts above also run against a tenant that is throttling you, and a throttled export that silently returns fewer rows is worse than no export at all: check for 429 responses and retry with the Retry-After value rather than looping.
FAQ
- Can I use SharePoint versioning to see old permissions?
- No. SharePoint document version history is not a history of permission assignments. To investigate older permissions, check saved permission reports and relevant audit records.
- Does the Entra ID sign-in log tell me what a user accessed?
- Sign-in logs record authentication to applications, not authorization to specific documents. SharePoint file access events (FileAccessed and similar) in the Unified Audit Log show what was opened, which is evidence of use, not of entitlement.
- How far back can I answer if I start today?
- Your coverage starts at your first complete baseline. Audit records still within retention can show some earlier changes, but they cannot establish the complete permissions before your baseline. Treat what they show as partial, and anything they do not show as unknown.
Related reading
Related guides
All guides
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.

Microsoft 365 Security9 min readbeginner
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.

SharePoint Permissions11 min readintermediate
How to Find Out Why a User Has Access to a SharePoint Site
Learn how to find out whether someone has SharePoint access directly, through inherited permissions or through groups inside other groups. Follow the steps using the admin interface, REST and PowerShell.