Permission Drift vs Who Changed Permissions: What's the Difference?
Published:
Last updated: 2026-11-21
Permission drift compares permissions snapshots to show what changed. Who changed permissions reads the audit log to show who did it and when. Use both.
They overlap on purpose, but they come from different data and answer different questions. Permission drift compares permissions snapshots and tells you what is different now. Who changed permissions reads the audit log and tells you who did something and when. Most teams run both: drift spots the change, activity names the person behind it.
In this article
Permission drift
Permission drift answers one question: what is different now?
Data source: the permissions report, scanning site, list and item permissions. Each run is compared with the previous one.
Headline number: permission grants added, removed or changed since the last run.
Who made the change: not shown. Drift only sees the end state, not the action that produced it.
Defaults: runs weekly on Monday at 6:00 and alerts on any change.
Requirements: none beyond a normal permissions scan.
Who changed permissions
Who changed permissions answers the other question: who did this, and when?
Data source: the user activity report, built from the audit log that governance data collection gathers. It covers sharing, group, permission-inheritance and site-admin events, plus Microsoft 365 group and Entra ID group membership and owner changes.
Headline number: permission and sharing actions users took in the period.
Who made the change: shown as “Changed by …”, with the people who made the most changes.
Defaults: runs daily at 7:00 and alerts when new items appear.
Requirements: audit log collection must be running. Microsoft keeps audit events available for only seven days, so the toolkit collects them daily to build a longer history; governance data collection is available in the Enterprise edition.
Side by side
Permission drift | Who changed permissions | |
|---|---|---|
Question answered | What is different now | Who did it, and when |
Data source | Permissions report (a scan of current access) | Audit log (governance data collection) |
Headline number | Grants added, removed or changed since the last run | Permission and sharing actions in the period |
Shows the person | No — end state only | Yes — “Changed by …” |
Default schedule | Weekly, Monday at 6:00 | Daily at 7:00 |
Alerts when | Any change | New items appear |
Needs | A normal permissions scan | Audit log collection (Enterprise) |
When the difference matters
The two monitors disagree in a few predictable situations, and each disagreement tells you something useful.
A change that was undone. If someone shares something and then removes the share between two drift runs, drift shows nothing, because the end state never changed. Who changed permissions shows both actions.
A change missing from the audit log. Drift still catches it — if it happened before collection started, fell outside retention, or came from a source the event filter doesn’t cover.
Volume. One action, such as breaking inheritance on a library, can show up as many grant changes in drift but only one event in Who changed permissions. The two numbers are not the same unit, so don’t compare them directly.
No audit collection. If audit log collection isn’t running, only drift works.
Which one should you use?
Run both if you can. They are separate monitors in the toolkit’s Monitoring area: each keeps its own run history and shows its own card on the Dashboard, so the drift card’s “what changed” and the activity card’s “see who changed what” are the two halves of one answer.
Reviewing access on a schedule (monthly access reviews, evidence that access was checked): Permission drift. It needs no extra setup and reports the grants that moved.
Answering “who gave Alex access to the finance library?”: Who changed permissions. Drift can tell you the grant exists; only the audit-backed monitor names the person and the time.
If you can only run one: choose Who changed permissions when you need names and timestamps, and set up audit log collection first (Enterprise). Choose Permission drift when you only need to know whether access changed at all, with no extra collection to maintain.
For the underlying scan, see How to Create a SharePoint Permissions Report, and How to Clean Up User Permissions in SharePoint for fixing what the monitors find.
SharePoint Essentials Toolkit (2027) · Questions: Submit a ticket · Feature overview: SharePoint permissions reports.