SharePoint troubleshooting
SharePoint site owner leaves: who can fix the site, and how to stop it happening again
When a SharePoint site owner leaves the company, the site itself carries on. The files stay, members keep their access and pages still load. What stops is everything that needed an owner: access requests go to an inbox nobody reads, nobody can add a new colleague, and nobody can change permissions. Only a SharePoint admin can put an owner back, and the automated policy Microsoft offers for this needs licensing most small businesses do not have.
A departing person usually leaves more than one thing behind. Flows run on their owner’s licence and stop on their own, which is covered in what breaks when a Power Automate flow owner leaves. Reports and semantic models have their own refresh problem, covered in what happens when a Power BI report owner leaves, and canvas apps need PowerShell to change hands, covered in when a Power Apps owner leaves. Their personal files run on a separate deletion clock, covered in what happens to OneDrive when an employee leaves. This guide is about the site, and every rule below was checked against Microsoft’s documentation on October 31, 2026.
What actually stops working when the site owner leaves?
Administration, not content. Files belong to the site, so nothing is deleted with the owner’s account, and members keep the access they already had. What stalls is anything that needs an owner: approving access requests, adding or removing people, changing permissions or sharing settings, and deciding when the site should be archived or deleted.
Access requests are the part users notice first. By default they go to the site’s owners group on a communication or classic site, and to the group’s owners on a site connected to a Microsoft 365 group or a Microsoft Teams team. If the person who left was the only owner, a new hire asks for access and the request simply never gets answered. Where the site lives decides who can fix it:
| Kind of site | Where ownership lives | After the only owner leaves | How an admin restores an owner |
|---|---|---|---|
| Team site connected to a Microsoft 365 group | The group’s owners, plus any additional site admins | The group has no owner, so nobody can manage membership of the site or the group | Active sites › select the site › Membership, then add group owners; or add an owner to the group in the Microsoft 365 admin center |
| Site behind a Microsoft Teams team | The team’s owners, who are the Microsoft 365 group’s owners | The team and its site are both ownerless, so nobody can add people to the team or approve requests to join it | Add a group owner as above; the change carries through to the team. Teams-wide clean-up is a governance job, not a one-site fix |
| Communication site | Site admins (a primary admin plus additional admins) and the site’s Owners group | Nobody left can manage permissions, sharing or access requests | Active sites › Membership, then change the primary admin and add site admins or site owners |
| Classic site | Site collection admins and the Owners SharePoint group | Same as a communication site | Change site admins from Active sites; review the Owners group in site permissions afterwards |
Want this worked through for your own ownerless sites? A free consultation is the first step.
Book my free consultation →The pattern in a small business is familiar. One person created a site for a project or a department, never added a second owner, and IT disabled the account on their last day. The site works for months. Then someone needs a new starter added, the request disappears, and the office manager ends up sharing files by email until somebody notices.
Who can reassign a SharePoint site that has no owner?
Someone with the SharePoint Administrator role or above in Microsoft 365. Site members cannot promote themselves, because changing permissions is an owner action. The admin opens Active sites in the SharePoint admin center, selects the site, opens Membership, and adds owners or site admins. For group-connected sites they can also add an owner from the Microsoft 365 admin center.
Microsoft’s page on managing site admins (opens in new tab) sets out the split: for a group-connected team site the admin adds and removes group owners and additional site admins, and for other sites they add and remove site admins and change the primary admin. One detail catches people out. Removing someone as primary admin leaves them listed as an additional admin, so remove the departed account from that list as well.
- Pick a person, not just a name. The new owner should be someone who actually understands who belongs on the site. Usually that is the departed person’s manager or the most active member, not IT.
- Add two. Restoring one owner just resets the clock to the next departure.
- Clear the request backlog. Once an owner is back, they should go through pending access requests in site permissions, since people who asked while the site was ownerless never got an answer.
- Check for a recreated account. If the person returns and their account is recreated, the site may still hold their old identity. Microsoft documents this as a user ID mismatch that has to be fixed before their access behaves normally.
Does the site ownership policy cover your plan?
Probably not, if you run Microsoft 365 Business Basic, Standard or Premium. The site ownership policy is a SharePoint Advanced Management feature, and Microsoft lists its base subscriptions as Office 365 E3, E5 or A5, Microsoft 365 E1, E3, E5 or A5, or Microsoft 365 GCC, GCC-High or DoD. No Business plan is on that list.
Microsoft’s SharePoint Advanced Management prerequisites (opens in new tab) also require one of three things on top of that base: at least one user with a Microsoft Copilot licence, the SharePoint Advanced Management Plan 1 add-on, or Microsoft 365 E7. Where you do qualify, the site ownership policy (opens in new tab) lets an admin set a minimum number of owners or admins, run it once in simulation mode to see which sites fall short, and then switch it to active mode, where it runs monthly. It is useful, with three limits worth knowing before you rely on it:
- The manager notice expires. Microsoft says a user’s details are deleted 30 days after they leave, so managers may get only one email. A policy run after that point cannot notify them at all.
- Teams sites are a partial exception. The manager notice works only for owners added directly to the SharePoint site. If the owner came from the Microsoft 365 group, which is the normal case for a team, it is not sent.
- Enforcement only bites at zero. Read-only and archive actions apply only to sites with no owner at all. Single-owner sites get three monthly notifications, then a three-month pause, and are never locked.
How do you stop the next departure orphaning a site?
Make it an offboarding step that happens before the account is disabled, while the person can still explain who belongs where. List the sites, teams and groups they own, add a current owner to each one that matters, and keep at least two owners on every business site. That costs nothing and works on every plan.
In practice the checklist step is the part that goes missing, because SharePoint ownership sits between IT, who disable the account, and the department, who know the site. Our SharePoint support and maintenance service treats an orphaned site as a routine ticket: restore administration, assign at least two owners, and fix the offboarding step that let it happen. If the bigger problem is dozens of ownerless teams rather than one site, our Microsoft Teams governance consulting works through them as part of a fixed-fee remediation list.
FAQ
Questions people ask about an ownerless site
No. Files in a SharePoint site belong to the site, not to the person who uploaded them, so deleting the owner's account removes nothing from its libraries or lists. What is deleted with the account is that person's OneDrive, which is a separate site and needs its own hand-over before the account goes.
No. Members can edit content but cannot change permissions, so they cannot promote themselves. A remaining owner can add another owner. If there is none, it takes someone with the SharePoint Administrator role or above, working from Active sites in the SharePoint admin center, or a group owner change in the Microsoft 365 admin center.
It finds them and asks people to step in, but it does not pick a new owner for you. In active mode it emails the recipients you chose each month. With the read-only action, a site that stays at zero owners after three monthly notifications is locked until an admin unlocks it.
Usually timing or membership. Microsoft says user details are deleted 30 days after someone leaves, so a policy that runs later has no manager to notify. On a Teams site the manager notice only works for owners added directly to the SharePoint site, not owners who came from the Microsoft 365 group.
At least two people who are still with the business, and in different roles where possible, so one departure or one long absence never leaves the site without someone who can manage access. Microsoft's own ownership policy example uses a minimum of two, flagging every site that has only a single owner for remediation.
Want a second opinion on your ownerless sites?
A senior US-based engineer talks it through with you first, at no cost. If there is work worth doing, you get a written scope with one price, and you approve it before anything starts.
Free consultation · Written fixed price before any work starts · Reply within one business day
Tell us what you’re trying to fix — a report, an approval process, an intranet, a Copilot rollout. We scope it as a fixed-fee project, you approve, and a senior engineer delivers in 2–4 weeks.
- Fixed-fee scope agreed before any work starts
- Senior, US-based Microsoft engineers — no handoffs
- Typical 2–4 week delivery
- 30 days of post-delivery hypercare included
Related reading
Keeping sites, teams and flows owned after people move on
SharePoint Support & Maintenance
Orphaned sites, broken permissions and failed flows handled as routine tickets, with ownership fixed at the source.
Microsoft Teams Governance Consulting
Dead teams archived, ownerless teams assigned and stale guests removed, worked through as a fixed-fee list.
When a Flow Owner Leaves
Flows run on their owner’s licence and connections, so they break differently: how to find them and the fixes.