Applies to: SharePoint Online, OneDrive for work or school, Microsoft 365 admin center
A manager sends a short message on a Thursday. Alex moves from Marketing to Sales on Monday. “Can you make sure Alex can’t get into the marketing files anymore?”
You open the Microsoft 365 admin center, find Alex, and look at the groups. Six of them. You remove the marketing ones and reply “done.”
That groups list is one layer of access out of four, so Alex can still open files you never saw on that screen.
The real cause: access lives in four places
People think of access as “which groups is this person in.” In SharePoint, a person can reach content through four separate layers:
- Microsoft 365 groups and Teams. Members of the group become members of the connected site.
- SharePoint groups and direct grants on a site. Owners, Members, Visitors, or the person added by name.
- Files and folders with their own permissions. Someone shared one item, so it no longer follows the site.
- Files in other people’s OneDrives. Every OneDrive is its own site, owned by one person.
Each layer is stored in a different place, and no free screen adds them up. So the check is four short steps, one per layer.
In the screenshots below, Alex Wilber is a sample user with three kinds of access: Read through the IntraTeam Visitors group, Contribute on one file in that site, and View on a file in my OneDrive.
Step 1: Check their groups in the admin center
In the Microsoft 365 admin center, go to Users > Active users and select the person. The Account tab has a Groups section.
Admin center > Active users > user
Six groups, and none of them is IntraTeam Visitors. A SharePoint group lives inside the site, so it never shows on this pane.
Select Manage groups to see the full list and remove memberships. Each Microsoft 365 group in this list has a connected SharePoint site, and some also have a team. Microsoft says group owners become site owners, and group members become site members.
Microsoft says that after you remove someone from a private group, it takes 5 minutes for them to be blocked from the group. Security groups in this list can grant site access too, if someone added them to a SharePoint group.
Check whether the team is public before you count this step as done. Microsoft notes that on a public group-connected team site, Everyone except external users has Edit by default. Removing Alex from the group changes nothing there. Alex still has Edit as an employee, and can join the group again. Make the team private, or remove Everyone except external users from the site’s groups.
That covers layer one. Alex was in IntraTeam Visitors the whole time, and this pane didn’t show it.
Step 2: Run Check Permissions on each site
Go to the site. Open Settings (the gear), select Site permissions, then Advanced permissions settings. On the ribbon, select Check Permissions. Type the person’s name, then select Check Now.
Site permissions > Check Permissions
Read through IntraTeam Visitors, plus Limited Access given directly. Nothing in this dialog says Alex can edit a file on this site.
The result lists each permission level and where it comes from. Here it said Alex had Read, given through the IntraTeam Visitors group. That’s the layer the admin center missed.
When I ran it, Check Permissions said Read, but the same person could edit a file on that site.
The second row is the one to read twice: Limited Access, given directly.
Microsoft describes Limited Access as a level SharePoint adds by itself when one item is shared with someone. It “doesn’t grant any additional permissions to the user” on its own. What it does tell you is that something on this site (a file, folder, list or library) was shared with this person or with a group they’re in. It doesn’t say which item, or at what level.
The banner is also a clue
Look above the list of groups. The yellow banner has two lines:
- Some content on this site has different permissions from what you see here. At least one file, folder or list has its own permissions.
- There are limited access users on this site. Someone has been given a single item. Select Show users to see who.
If either line is there, do Step 3 for this site.
Step 3: Find the files with their own permissions
In that same banner, select Show these items. An Exceptions dialog lists each library that holds items with unique permissions. Select view exceptions next to the library, then manage permissions next to the item.
Exceptions > view exceptions > manage permissions
The file the Limited Access marker pointed to. Alex is listed by name with Contribute, which means Alex can edit and delete it.
This is where the edit access was hiding. Alex has Contribute on Board-notes-Q4.txt, as a direct entry. Select the name, then Remove User Permissions on the ribbon.
If the person isn’t listed by name, the access may come through a sharing link instead. Specific people links give access to everyone added to the link. Open the file in its library, select Manage access, and check the links. Remove the person from the link, or delete the link.
One catch from Microsoft’s own page on this: when you unshare the item, the person keeps Limited Access on the site. That’s harmless, since they “will not have access to any items not shared with them.” It does mean the Limited Access row in Step 2 can be a leftover, not a live share. Step 3 tells you which.
Repeat Steps 2 and 3 for every site the person could have touched. On a tenant with 15 sites, that’s an afternoon. Past a few dozen sites, it isn’t a real option, and the section on the paid report below is for you.
Include the sites people forget. Teams private and shared channels each get a separate SharePoint site, managed from Teams, so a check on the parent team site doesn’t cover them. Site admins aren’t in any group either. Microsoft says they have “full control of the site root and any subsites.” In the SharePoint admin center, open Active sites and check which sites list the person as an admin.
Step 4: Search the audit log for OneDrive shares
The first three steps cover sites. They don’t cover the file a coworker shared with Alex from their own OneDrive. You’d have to open every OneDrive in the tenant to find it that way.
The audit log is the free way in. In the Microsoft Purview portal, go to Audit > Search. Set the date range, and under Activities - friendly names, pick the sharing activities, including Shared file, folder, or site. Leave the Users box empty. That box matches the person who did the sharing, not the person who received it. Run the search, then filter on the recipient. For Shared file, folder, or site, the Detail column names who the item was shared with. For the other events, export the results and filter the TargetUserOrGroupName field for the person’s UPN.
If an item was shared with a group, the record names the group, not the person. Filter for the person’s security groups and SharePoint groups too.
Microsoft’s sharing audit page names the field to look at. TargetUserOrGroupName holds “the UPN or name of the target user or group that a resource was shared with.” The audit activities list defines the events to look for:
| Event | What it means |
|---|---|
| SharingSet | A file, folder or site was shared with someone in your directory. The Detail column names who. |
| AddedToSecureLink | The person was added to a Specific people link |
| AddedToSharingLink | The person was added to a sharing link |
| AddedToGroup | The person was added to a SharePoint group to get access |
| CompanyLinkUsed | Someone opened a file through a People in your organization link |
Before you trust the result, know where the audit log stops:
- On most licences it only goes back 180 days. Audit (Standard) keeps records for 180 days. Retention follows the licence of the person who did the sharing, not the person you’re checking. If the sharer has E5 or Audit (Premium), SharePoint and OneDrive records are kept for one year. Anything older won’t show up.
- New events are not instant. Microsoft says records for SharePoint and OneDrive usually show up 60 to 90 minutes after the event.
- Auditing has to be on. It’s on by default for most organizations. Check that the Search page doesn’t show a banner asking you to start recording. If it does, nothing before that day exists to search.
The test tenant for this post showed that banner, and the button to start recording did nothing from the portal. Check yours now, before a leaver makes you need it.
Step 5: For a leaver, cut sign-in before the cleanup
The four steps above take time. If the person is leaving, don’t make them wait for your cleanup. Microsoft’s steps for a former employee are, in order:
- Reset the password. This is the immediate block.
- Sign out of all sessions. On the Account tab, select Sign out of all sessions. They’re prompted to sign in again within an hour, when their access token runs out.
- Block sign-in. Select Block sign-in at the top of the user pane. Microsoft notes this “can take up to 24 hours to take effect,” which is why the password reset comes first.
Microsoft Entra says that once the account is disabled and its sessions are revoked, the person “can’t gain new tokens,” and loses access as the current tokens and sessions expire. Any permission that needs a sign-in can’t be used after that. Anyone links are the exception. Microsoft says people using them “don’t have to authenticate.” Delete the Anyone links the person created, in their OneDrive and on sites. You can’t list the Anyone links they received, so on sensitive sites, review all of them. Then clean up the entries at your own pace, so the next person who inherits the role doesn’t find surprises.
For the person’s own OneDrive, the OneDrive tab on their user pane has Create link to files under Get access to files. After you delete the account, the OneDrive is kept for 30 days by default, then moved to the recycle bin for 93 days. By default their manager gets access, or the secondary owner if no manager is set. Blocking sign-in or removing the licence doesn’t start that clock. Until you delete the account, the OneDrive and its shared links stay in place.
For someone changing roles, there’s no sign-in to cut. All four steps matter, because the person keeps working with the same account.
If you have SharePoint Advanced Management
One report replaces Step 2 across every site and tells you where Step 3 is needed. It lists each site the person can reach and how many files or folders were shared with them. You still open the site to see which files those are. Run it again with the OneDrive scope to cover other people’s OneDrives. It’s the Site permissions for users report, under Reports > Data access governance in the SharePoint admin center.
It needs SharePoint Advanced Management, which you get when at least one user is assigned a Microsoft Copilot licence, or by buying the SharePoint Advanced Management Plan 1 add-on. Neither was in my test tenant, so I’m describing it from Microsoft’s documentation, not a live run:
- It lists every site the chosen users can reach, directly or through groups, and whether that’s the whole site or only some files.
- Each run covers one scope, either SharePoint or OneDrive. Run it twice for the full picture.
- It’s a snapshot. The data can be up to 48 hours old.
- You can re-run it every 30 days, so you can’t run it again next week to confirm your cleanup.
- You can have up to five reports. Both scopes for one person use two of them.
- The Site permissions across your organization report has to have run at least once first.
Past a few dozen sites, the hand checks stop being realistic and the report is worth the licence. With 20 sites, the free steps above cover it.
What this does not fix
It doesn’t catch “People in your organization” links. Microsoft explains that these links work like a key. A link sent through the share dialog, Outlook or a Teams chat is redeemed right away for up to 100 individual recipients. A link sent to a group, or posted in a Teams channel, isn’t redeemed until someone clicks it. Until then the person’s name isn’t on the item’s permissions, so Check Permissions can come back clean while the link sits in an inbox. The audit log records each use as CompanyLinkUsed, after the fact.
It doesn’t scale. Steps 2 and 3 are one site at a time, by hand. Past a few dozen sites, you need the paid report or a PowerShell script, and a script is its own project.
It doesn’t go back far. For most sharers the audit log covers 180 days. Anything shared before that is invisible to Step 4.
It doesn’t tell you what they opened. This is about what someone can open, not what they did. For that, you’re back in the audit log, searching file access events.
The bottom line
The groups list in the admin center is one layer out of four. Check Permissions on each site, follow every Limited Access row to the file behind it, and search the audit log for OneDrive shares. If the person is leaving, reset the password and block sign-in first, then do the cleanup.