Guide to Orphaned Teams in Microsoft Teams
Introduction
A common problem we see with customer Microsoft Team environments are Orphaned Teams.
So, let us discuss what they are, how to find them, and then how we plan to get rid of them.
Update: 20th April 2026
Recently Microsoft has provided an update where you can configure orphaned detection of orphaned sites and send notifications to users to take over the ownership.
This blog post has been updated to reflect that. Additionally, we will talk about this feature below and the approach to configure this feature.
More information can be found in this Microsoft Support article.
What is an orphaned Team?
So, an orphaned team is a team where no one can administer the team anymore. This is normally when all the site owners have left the organisation.
How can I detect orphaned Teams?
This is difficult to do as to detect an orphaned Team you need the following information.
- A list of teams with their site owners (no problem).
- When each of those site owners last logged on (this is trickier).
Fortunately, Microsoft have released a new feature which allows administrators to detect orphaned Microsoft Teams and Microsoft 365 Groups and notify the members of the group that they can become owners.
Now this is a good feature, but it might lead to users who should not have access to information being able to get access to information because they become owners of the Microsoft Team or Microsoft 365 Group. So use this feature by all means but use with some caution.
To get a list of Teams from Microsoft 365 is quite straight forward using the Microsoft Graph API. However, the challenge comes with understanding when the user last logged on. This information is not held against a user object. Instead, the most reliable approach is to read and record the last time they logged using sign-in information.
The challenge comes from the fact that depending on your Azure Active Directory licensing, there are different retention periods. By default, sign-in logs are held for 7 days, however, if you purchase Azure Active Directory Basic or P1 license then they are held for 30 days.
More information can be found here.
Therefore, the sign in information needs to be checked regularly so that you can accurately capture the last time a user logged in and then store that information somewhere for processing.
How do I resolve an Orphaned Team?
If you don’t have the Orphaned Microsoft 365 Group feature enabled then you will need to resolve this issue manually. To do this you will need to be an administrator for Microsoft 365, someone who is part of the Groups Admin or Global Admin role will need to update and assign new site owners.
What can I do to reduce the likelihood of orphaned Teams?
Governance and process
The first thing is that you need to put in place governance and a process around creating a Microsoft Team.
That process should require that when a Team is created there are at least two owners provided. This helps if one of the owners is on holiday or off sick. Also, the owners should be educated so that they know that if one of them leaves that they should assign a new owner to take over from the owner who is leaving.
Reporting
Secondly, put some reporting in place so that you notified when a Microsoft Team has only one Site Owner. This will allow you to capture those exceptions. Use the sign-in information to check and identify Microsoft Teams where one of the owners has not logged in, in 30 days.
The report data can be established using the Microsoft Graph [] to retrieve the site owners for a Team. This information along with the sign-in information can be used to highlight those Teams which have more than one Site Owner but where the Site Owners have left.
Notify
Lastly, using the reports, you can identify the Teams and then reach out to the owners and ask them to provide a new Site Owner which can add an owner or replace the existing one.
Tooling
You can use tooling to tackle this problem, examples of tools that will help you control Orphaned Teams are:
Try them out and see which one works for you.
If you are suffering from Orphaned Sites, you might be suffering from this.
If you are suffering issues with Microsoft Teams Orphaned Sites, you might also be suffering from some of these issues as well.
Want to Know How We Can Support Your Business?
Here at iThink 365 our expert team helps organisations unlock the full potential of Microsoft 365, leveraging AI, Copilot extensibility, and custom agents to build intelligent, automated solutions. From streamlining workflows to eliminating repetitive tasks, we deliver automation that saves time, boosts productivity, and adds real business value.
Get in touch today to see how AI-powered support could work for you.



