Microsoft 365 Enterprise Blog | Updates, News & Insights

Running a SharePoint permissions audit without full admin rights?

Written by Orchestry | Nov 17, 2026, 6:08:50 PM

To run Microsoft's tenant-wide permission reports, you sign in as a SharePoint administrator, a role that can give itself access to any site or OneDrive in your tenant. So the person checking who has too much access ends up with more access than almost anyone in the tenant. A SharePoint permissions audit doesn't have to work that way.

The fix is to separate seeing permissions from changing them. Run the tenant-wide snapshot once under a tightly controlled admin account, send site-level findings to the owners who can act on them, and give auditors scoped, read-only views of the part of the tenant they're responsible for. Orchestry's Enterprise roles and attribute-based access let a regional or departmental auditor see the workspaces they're responsible for without handing them the SharePoint admin role.

Why a SharePoint permissions audit usually needs full admin rights

Microsoft's tenant-wide view of SharePoint permissions lives in the data access governance reports. They include a site permissions report across every SharePoint and OneDrive site, a report of every site a specific user can reach, and activity reports for sharing links and "Everyone except external users" grants. To open them, you sign in to the SharePoint admin center with SharePoint administrator credentials, and the full set needs SharePoint Advanced Management.

SharePoint admin center data access governance reports used for a tenant-wide SharePoint permissions audit

Tenants on Microsoft 365 E5 without SharePoint Advanced Management get a thinner version: activity reports only, capped at 10,000 sites, with no snapshot reports and no remediation actions. Tenants with a Copilot license already have SharePoint Advanced Management included.

The role is the problem. Microsoft's description of the SharePoint Administrator role says these admins don't automatically have access to every site and OneDrive, but they can give themselves access to any of them. They can also change sharing settings and group owners across the tenant. Microsoft recommends using roles with the fewest permissions, but it doesn't document a lower-privilege role that runs these reports.

The newer item-level reports go the other way: they need the SharePoint Advanced Management Administrator role, which adds viewing file names and paths across every site to everything a SharePoint admin can do

The alternatives don't help much:

  • Site admins can manage their own sites, but they don't get the SharePoint admin center, so they can't see anything beyond the sites they run.
  • PowerShell and Graph scripts that enumerate every site run under an app registration with tenant-wide site permissions, which is access to all content, held by a script someone has to maintain.
  • Global admins have every SharePoint admin permission and more, which is the opposite of least privilege.

What SharePoint permissions an audit should cover

Before deciding who runs the audit, be clear about what it has to find. SharePoint permissions accumulate in layers, which is why they get messy in the first place. A complete audit checks five things:

  1. Who has access to each site. Direct grants, SharePoint groups, Microsoft 365 group membership, and nested Entra groups that add people indirectly.
  2. "Everyone except external users" grants. One permission that opens content to every internal account.
  3. Sharing links. Anyone, organization-wide and specific-people links, including old ones nobody remembers creating.
  4. Broken inheritance below the site. Microsoft's site permissions report counts the items with unique permissions on each site, but it doesn't list which folders and files they are so you need to find and fix broken permission inheritance separately.
  5. Who holds admin roles. SharePoint and Global admins sit outside every site's permission list, and they can give themselves access to any site.

The last item is the reason least privilege matters for the audit itself.

How to audit SharePoint permissions with least privilege

You can audit SharePoint permissions across the tenant without giving every auditor a tenant-wide admin role. These six steps work with native tools, and a governance platform makes steps 3 to 5 easier to run at scale:

  1. Separate who sees from who changes. Decide which people need to read permission data and which need to fix it. Most auditors only need to read, and most fixes belong to site owners.
  2. Run the tenant-wide snapshot under a controlled admin account. Use a dedicated SharePoint admin account reserved for audits, ideally made eligible through Privileged Identity Management so the role is activated just in time and expires after the run (PIM needs Entra ID P2). Run the site permissions report and export it. You get one baseline without handing standing admin rights to the audit team.
  3. Send site-level findings to site owners. Microsoft's site access review lets an admin route overshared sites from the reports to their owners, who review and fix permissions on their own sites. It covers SharePoint sites, not OneDrive.
  4. Give auditors scoped, read-only views. A regional compliance lead should see the sites in their region, not every site in the tenant. Natively, that means filtering and sharing exports; with a governance tool, it means roles that are scoped by design.
  5. Log who holds audit and admin roles, and when that changes. The access list for the people doing the audit is part of the audit.
  6. Repeat on a schedule. Microsoft suggests running snapshot reports quarterly and activity reports monthly, so new links and grants don't build up between audits.

Orchestry Access Control roles page with separate admin roles for workspaces, OneDrive, guests, templates and licensing

Orchestry is built for steps 3 to 5 at scale. On Enterprise, admin access splits into separate roles, such as Workspaces Admin, OneDrive Admin, Guests Admin, Templates Admin and Licenses Admin, so the person reviewing workspace permissions doesn't also manage licenses or guests. A history tab records role changes over time for your own audit trail.

Orchestry attribute-based access segments that limit workspace reporting to North America, EMEA and APAC audiences

Attribute-based access narrows the view further. You define segments from workspace metadata, such as location or department, and people in each segment see only the matching workspaces in Orchestry's workspace reporting and dashboards. A compliance lead for EMEA sees EMEA workspaces and nothing else.

Inside those views, Orchestry's permissions reporting shows each workspace's permissioned users, Entra groups, "Everyone except external users" grants, sharing links and broken inheritance on folders and files, and the Sharing Overview report ranks workspaces by sharing risk. Workspace reviews then send the fixes to owners on a schedule.

SharePoint permissions report options compared

Each way of producing a SharePoint permissions report needs a different level of access. Here's what each one shows and what it costs you in privilege:

Method What it shows Role it needs Watch out for
Data access governance reports Site permissions across the tenant, sites a user can reach, recent sharing links and "Everyone except external users" grants SharePoint admin, with SharePoint Advanced Management for the full set The role can give itself access to any site
Site permissions page Permissions on one site Site owner or site admin One site at a time; no tenant view
PowerShell or Graph scripts Whatever the script enumerates, down to items App registration with tenant-wide site access Scripts and app secrets need ongoing maintenance
Site access review Owner-confirmed fixes on overshared sites SharePoint admin starts it; owners complete it SharePoint sites only, no OneDrive
Orchestry Workspace permissions, sharing links, inheritance and sharing risk, scoped by role and attribute Orchestry role (Enterprise for scoped roles) Attribute segments use managed metadata, so workspaces need tags

SharePoint permissions audit: frequently asked questions

Can a site owner see who has access across SharePoint?

No. Site owners and site admins can manage permissions on the sites they own, but they don't have access to the SharePoint admin center, so they can't see permissions across other sites.

What role do I need to run data access governance reports?

You sign in to the SharePoint admin center as a SharePoint administrator and the full set of reports needs SharePoint Advanced Management. The item-level reports for "Everyone" and "Everyone except external users" need the SharePoint Advanced Management Administrator role, which a Global Administrator assigns. Tenants on E5 without SharePoint Advanced Management get activity reports for up to 10,000 sites, but no snapshot reports.

How do I check SharePoint permissions for one user?

Run the site permissions for users report in the data access governance reports. It lists every site the user can access and whether that access comes directly or through a group.

How often should you audit SharePoint permissions?

Microsoft suggests snapshot reports quarterly and activity reports monthly. Owner reviews in between catch new sharing links and grants before they pile up.

Does a SharePoint permissions audit fix oversharing?

No, it finds it. Fixing oversharing takes owner reviews, link cleanup and permission changes after the audit, which is why the audit should feed straight into site access reviews or scheduled workspace reviews.

If you're planning a SharePoint permissions audit, see how Orchestry gives auditors scoped views without handing them the SharePoint admin role. Book a 30-minute walkthrough in your own tenant.