How to Investigate Who Changed SharePoint Permissions
Learn how to investigate a SharePoint permission change. Check when it happened, who made it when Microsoft 365 recorded their name, and what access looked like before and after.

Start with Microsoft Purview's audit log to investigate who changed SharePoint permissions. Look for the change, its recorded time and the person or application that made it. Some access changes come from group membership changes, so check the relevant Entra records too.
A finance folder that should have been restricted to five people now shows a contractor group with Edit. Nobody admits to changing it. The question is not "who has access" but "who granted it, when, and what did it look like before." This guide is the procedure for answering that from the Microsoft 365 Unified Audit Log, with the pitfalls marked.
What the audit log records for permissions
SharePoint and Microsoft 365 record several kinds of permission-related activity. The operation name tells you what Microsoft reported, but it does not always explain the full effect on access. Start with the original record, then check group membership and permission state before drawing a conclusion.
These are the operations Microsoft documents in its list of audited activities that you will use most, with what Microsoft says they record:
| Operation | What Microsoft says it records |
|---|---|
SharingInheritanceBroken | An item no longer inherits sharing permissions from its parent |
SharingInheritanceReset | An item inherits sharing permissions from its parent again |
PermissionLevelsInheritanceBroken | An item no longer inherits permission levels from its parent |
AddedToGroup / RemovedFromGroup | A member or guest was added to or removed from a SharePoint group (possibly as a side effect of sharing) |
GroupAdded / GroupRemoved / GroupUpdated | A SharePoint group was created, deleted or had its settings changed |
SiteCollectionAdminAdded / SiteCollectionAdminRemoved | A site collection administrator was added or removed |
SharingSet / SharingRevoked | A file, folder or site was shared with someone in your directory, or a share was removed |
SharingInvitationCreated | Something was shared with a person who is not in your directory |
SecureLinkCreated / SecureLinkDeleted | A specific-people sharing link was created or deleted |
AddedToSecureLink / RemovedFromSecureLink | Someone was added to or removed from a specific-people link |
CompanyLinkCreated / CompanyLinkRemoved | A link anyone in your organization can use was created or removed |
AnonymousLinkCreated / AnonymousLinkRemoved | A link that needs no sign-in was created or removed |
PermissionLevelAdded / PermissionLevelModified / PermissionLevelRemoved | A permission level itself was added, changed or removed on a site collection |
Two cautions about that list. The PermissionLevel* operations are about permission level definitions (such as a custom level's rights), not about giving a person or group a level on a folder. And Microsoft marks SitePermissionsModified, which recorded a group's level changing on a site, as deprecated. You may also find operation names in your own records that are not in Microsoft's list: in our test tenant, sharing a file with a specific person also produced SharingLinkCreated, and removing the link produced SharingLinkRemoved. Treat the details inside a record, not its name alone, as the evidence.
Entra ID group membership changes are logged under the Azure Active Directory workload as Add member to group. and Remove member from group., with the trailing period. They are just as relevant. A change to an Entra group can affect SharePoint access without changing the permissions assigned directly on the site. Include directory-group membership events in the investigation, not only SharePoint events.
Each record has UserIds (the actor), Operations, and an AuditData JSON blob with the specifics, including CreationTime, in UTC. The fields inside AuditData are described in Microsoft's audit log schema: for sharing events, for example, TargetUserOrGroupName names who something was shared with and EventData carries follow-up detail such as the permission granted.
Step 1: Scope the search
Start narrow: the object, a time window, and the relevant operations. Using Exchange Online PowerShell:
Connect-ExchangeOnline
$objectUrl = "https://contoso.sharepoint.com/sites/Finance/Shared Documents/Payroll"
$start = [datetime]::Parse("2026-01-01T00:00:00Z").ToUniversalTime()
$end = [datetime]::Parse("2026-02-01T00:00:00Z").ToUniversalTime()
$results = Search-UnifiedAuditLog -StartDate $start -EndDate $end `
-Operations SharingInheritanceBroken,SharingInheritanceReset,AddedToGroup,RemovedFromGroup,SharingSet,SharingRevoked,SiteCollectionAdminAdded `
-ObjectIds $objectUrl -SessionId "payroll-permissions" -SessionCommand ReturnLargeSet -ResultSize 5000
A plain -ObjectIds value targets that one address, so a change on a file inside the folder may not match the folder URL. To search a whole site, add a wildcard (https://contoso.sharepoint.com/sites/test/*) or use -SiteIds (the site collection GUID), then filter on ObjectId afterwards:
$results | ForEach-Object {
$d = $_.AuditData | ConvertFrom-Json
[pscustomobject]@{
WhenUtc = $d.CreationTime
Actor = $_.UserIds
Operation = $_.Operations
Object = $d.ObjectId
Target = $d.TargetUserOrGroupName
Level = $d.EventData
}
} | Where-Object { $_.Object -like "$objectUrl*" } | Sort-Object WhenUtc
Run the same command again with the same -SessionId until a call returns nothing, and collect each page. One session stops at 50,000 results, so split wide windows. Never assume one call returned everything.
Step 2: Read the record
Open each candidate record and read its AuditData, not only the summary columns. In the Contoso Finance sample scenario (fictional data), the record that matters is the change on the Payroll folder on 20 January. Whatever its operation name, confirm three things from the record itself:
- Who: the actor in
UserIds, as a user principal name, an application, orapp@sharepoint. The event may identify the person or application responsible. If Microsoft did not record an identifiable actor, do not assign the change to someone based on a guess. - When:
CreationTimeinsideAuditData, in UTC. - What: the object (
ObjectId), the person or group it concerns, and any detail of the change the record carries.
What the record does not tell you is why, or who was affected downstream. If a detail you need, such as the level a group had before, is not in the record, do not assume it: get it from a baseline.
Some records need a second look:
SharingInheritanceBrokenlogs the object that became unique. The permissions it starts with are a copy of the parent's, and Microsoft's activity list describes no event for that copy. To know the initial state you need the parent's permissions at that moment.- App-only actors appear as
app@sharepointor the application's display name. That means an automation, a provisioning engine or a governance tool made the change under an application identity; the human trigger, if any, is in that system's own logs. SharingSetfrequently comes withAddedToGroupor link events and can look like a duplicate. Microsoft notes that sharing is often accompanied by a second event that describes how access was granted.
Step 3: Establish the before and after
The audit record describes a change. To state the before and after honestly you need the state on either side of it. There are two sources:
- Your own baselines, if you keep them (see How to Audit Historical SharePoint Permissions). The nearest baseline before the event, plus the recorded changes up to it, gives you "before." Apply the event and you have "after."
- Adjacent events, if you do not. A group-addition event records a direct membership being added. It does not, by itself, tell you whether the person already had access through another group or sharing link. Chaining such records gives you the history of one person or group on one object, but not the whole object's state, and only for the changes that were recorded.
For the Payroll example, the sample records give: unique since 12 December (Robert Williams broke inheritance, then removed Finance Members), Visitors raised to Edit on 20 January (Jordan Ellis), set back to Read on 28 January (Jordan Ellis). The exposure window is eight days.
Step 4: Find who was affected
A permission change on a group affects every member of that group, transitively. Take the target principal from the record and expand it as of the event time, not as of today. Finance Visitors contained the Entra ID security group Finance Contractors, which contained the guest Alex Turner and the nested group External Auditors. Every one of those identities could edit payroll files for eight days.
If you only have current membership, say so in the finding. "Members of Finance Visitors as of today" is a different claim from "members of Finance Visitors on 20 January."
Step 5: Look for related events
Investigations rarely involve one event. Widen the window around the timestamp and look for:
- Other permission changes by the same actor in the same session (batch changes often come in bursts seconds apart).
- Group membership changes on the target group around the same time (someone added to the group the day before it was elevated is a pattern worth noting).
FileAccessed,FileDownloadedandFileSyncDownloadedFullevents on the object during the exposure window by identities that only had access because of the change. That is the difference between "could have" and "did."
Search-UnifiedAuditLog -StartDate "2026-01-20T15:00:00Z" -EndDate "2026-01-28T10:00:00Z" `
-RecordType SharePointFileOperation -Operations FileAccessed,FileDownloaded `
-SiteIds $financeSiteId -SessionId "payroll-file-events" -SessionCommand ReturnLargeSet -ResultSize 5000 |
ForEach-Object { $d = $_.AuditData | ConvertFrom-Json; $d } |
Where-Object { $_.ObjectId -like "*/Payroll/*" } |
Select-Object CreationTime, UserId, Operation, ObjectId
If the change was to a setting rather than a permission, such as tenant external sharing, check SharePoint's change history report. It shows what changed, when and who initiated it for site settings and for organization settings changed in the admin center, for up to 180 days depending on user license. It needs SharePoint Advanced Management and auditing.
Step 6: Write it up
A defensible finding contains:
- The object (URL and id), the change, the actor, the UTC timestamp, and the raw audit record id.
- The state before and after, with the source of that state (baseline, chained events, or current state with a caveat).
- The affected identities, expanded as of the event time, with the method used.
- Related events in the window.
- The confidence of each element, including any retention or coverage limits.
Keep the raw records. Parsed summaries are for reading; raw AuditData is for proving.
FAQ
- The actor is shown as a GUID or as app@sharepoint. Who is that?
- An application identity made the change. Look up the GUID in Entra ID enterprise applications. Check ApplicationDisplayName and EventData in the record, then the application's own logs for any person who triggered it.
- Why can't I find an event for the permissions copied when inheritance was broken?
- SharingInheritanceBroken records the break itself. Microsoft's activity list describes no event for the copied permissions, so use the parent's state at that time.
- Can I get these events without Exchange Online PowerShell?
- Yes. Audit search in the Microsoft Purview portal exposes the same log, and Microsoft recommends the Office 365 Management Activity API for downloading audit data programmatically.
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.

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.