If you manage Teams and rely on the Ownerless Team report in the Teams admin center, you may notice it stops listing certain teams after you change the Microsoft 365 group that backs a team. The report only shows teams that have no owners, but a change to the group owner or membership can leave the report stale or incomplete. This article explains why the report becomes incomplete and gives you a step-by-step method to fix it. You will also learn how to verify the report data and avoid the same problem in the future.
Key Takeaways: Restoring the Ownerless Team Report After Group Edits
- Teams admin center > Teams > Manage teams > Ownerless team report: Shows the current list of teams with no owners, but the data can become stale after a Microsoft 365 group change.
- Refresh the report page after any group modification: Forces the admin center to re-read group ownership data and removes outdated entries.
- PowerShell command Get-Team -GroupId: Lets you verify the actual owner count for a specific team so you can confirm whether the report is wrong.
Why the Ownerless Team Report Becomes Incomplete After a Group Change
The Ownerless Team report in the Teams admin center is generated from the owner information stored on the Microsoft 365 group that backs each team. When you edit the group through the Microsoft 365 admin center, Azure AD, or PowerShell, the group’s owner list can change. For example, you might add a new owner, remove an existing owner, or transfer ownership to a different user. These actions directly alter the underlying group object that Teams reads to determine whether a team has an owner.
The report does not update in real time. Instead, the admin center caches the report data and refreshes it at regular intervals. If you run the report immediately after a group change, the cached data may still show the previous owner state. In some cases, the report also fails to pick up changes if the group was modified through a tool that does not send a change notification to Teams, such as a direct Graph API call or a bulk PowerShell script. As a result, a team that now has an owner still appears in the Ownerless Team report, or a team that lost its owner does not appear at all.
Another cause is the way the report filters teams. The report only includes teams that are not archived and that have no owners. If you changed the group’s membership but not its owner list, the report may remain correct. But if you changed the owner list, the report can become incomplete until the cache refreshes or you force a manual update.
Steps to Refresh and Correct the Ownerless Team Report
Follow these steps to fix an incomplete Ownerless Team report after you change a Microsoft 365 group. The steps assume you have Teams admin permissions and the necessary PowerShell modules installed.
Step 1: Refresh the Report in the Teams Admin Center
- Open the Teams admin center and navigate to the report
Go to Teams admin center > Teams > Manage teams. Select the Ownerless team report tab. The report may take a moment to load the current data. - Refresh the browser page
Press F5 or click the refresh icon in your browser. This forces the admin center to re-request the report data from the backend instead of using the cached version. - Wait for the report to regenerate
After refreshing, the report may show a loading indicator. Wait until the list updates. If the report still shows the same incomplete data, proceed to the next step.
Step 2: Force a Cache Refresh Using PowerShell
- Connect to Microsoft Teams PowerShell
Open Windows PowerShell as an administrator. RunInstall-Module MicrosoftTeams -Forceif you have not installed it. Then runConnect-MicrosoftTeamsand sign in with your Teams admin account. - Identify the affected team
RunGet-Team -DisplayName "Your Team Name"to find the GroupId for the team that is missing from the report. Note the GroupId value. - Check the current owner list
RunGet-TeamUser -GroupId "GroupId" -Role Owner. This shows the actual owners for that team. If the command returns no owners, the team truly has no owner and should be in the report. If it returns at least one owner, the team should not be in the report. - Force a refresh by updating the group
If the owner list is correct but the report is still wrong, runSet-Team -GroupId "GroupId" -DisplayName "Same Name". This triggers a change event that prompts Teams to re-evaluate the group and update the report data.
Step 3: Verify the Report After the Refresh
- Go back to the Ownerless Team report
Return to Teams admin center > Teams > Manage teams > Ownerless team report. Refresh the page again with F5. - Check if the missing team now appears
Search for the team name in the report. If the team has no owners, it should appear. If it has an owner, it should not appear. - Repeat for other teams if needed
If you changed multiple groups, repeat the PowerShell steps for each affected team. The report will update after each forced refresh.
If the Report Still Shows Wrong Data After the Main Fix
Sometimes the report remains incomplete even after you refresh the page and force a change. The following issues explain why and how to resolve them.
Teams Admin Center Cache Is Slow to Update
The admin center caches report data for up to 24 hours. Even after a refresh, you may see old data. To work around this, use PowerShell to confirm the true owner status. If the group has an owner, the report will eventually correct itself. If you need the report immediately, you can manually note the correct status and check back later.
Group Change Was Made Through a Non-Standard Tool
If you used the Microsoft Graph API or a third-party tool to change the group owner, Teams may not receive the change notification. In that case, run the PowerShell command Set-Team -GroupId "GroupId" -DisplayName "Same Name" to force a notification. This is the same step from the main fix and is the most reliable way to trigger a report update.
You Changed the Group Owner but Not the Group Membership
The Ownerless Team report only looks at the owner role, not the membership role. If you added a member but did not assign the owner role, the team will still appear as ownerless. Use Add-TeamUser -GroupId "GroupId" -User "user@domain.com" -Role Owner to assign an owner. Then refresh the report.
Ownerless Team Report vs PowerShell Owner Check: Key Differences
| Item | Ownerless Team Report | PowerShell Owner Check |
|---|---|---|
| Data source | Cached admin center data | Live Microsoft 365 group data |
| Update speed | May lag up to 24 hours | Immediate |
| Accuracy after group change | Can be incomplete | Always current |
| Required permissions | Teams admin | Teams admin and PowerShell access |
| Best use | General overview | Verify a specific team |
You can now refresh the Ownerless Team report and verify its data after any Microsoft 365 group change. Use the PowerShell commands to check the true owner status when the report looks wrong. For ongoing accuracy, run the report after each group modification and compare it with PowerShell output. To avoid future mismatches, make group owner changes through the Teams admin center or the Teams PowerShell module, which send the proper notifications to Teams.