When you create a new team in Microsoft Teams and run the guest review process, inactive guests may remain in the team instead of being removed. This happens because the guest review policy relies on the guest’s last activity date, which is not always populated for a newly created team. This article explains why the review fails for new teams and provides the exact steps to force a cleanup of inactive guests.
The guest review feature in Teams is part of the Azure AD access review system. It checks guest accounts against your organization’s sign-in and activity logs. For a new team, the guest may have no recorded activity yet, so the review marks them as active even if they have not used the team. You will learn how to adjust the review settings and manually remove guests when the automatic process does not work.
Key Takeaways: Force Guest Cleanup in a New Teams Team
- Teams admin center > Teams > Manage teams > Guests: View the guest list and identify inactive members manually.
- Azure AD > Identity Governance > Access reviews: Create a review that targets the team’s group and sets the inactivity threshold to 0 days.
- Microsoft Graph API > groupMembers: Remove guests programmatically when the review UI does not offer a removal option.
Why Teams Guest Review Does Not Remove Inactive Guests in a New Team
The guest review process in Teams is built on Azure AD access reviews. When you run a review, Azure AD checks each guest’s last sign-in date and last activity in the tenant. For a newly created team, the guest account may have been created at the same time as the team. In that case, the guest has no historical activity to evaluate. Azure AD treats this as an active guest because it cannot prove the guest is inactive.
Another reason is the review’s inactivity threshold. The default threshold is often 30 days. If the guest was added only a few days ago, they will not meet the threshold, so the review keeps them. Even if the guest never signed in, the system may not flag them because the minimum days have not passed.
A third factor is the review scope. When you create a review for a team, you must select the correct group. Teams stores members and guests in a hidden Microsoft 365 group. If you accidentally review the wrong group, the guests in your team will not appear in the review results.
How Azure AD Determines Guest Activity
Azure AD tracks guest activity through sign-in logs and audit logs. The last sign-in date is stored in the user object as the signInActivity property. For a new guest, this property is null. Azure AD access reviews interpret a null value as active, not inactive. This behavior is by design to avoid removing guests who have not yet signed in but are expected to use the team soon.
Why the Review Runs but Does Nothing
If you run a review and select “Remove guest from group” as the action, the review will only remove guests that meet the inactivity criteria. If no guest meets the criteria, the review completes with zero changes. This is normal. You need to change the criteria or manually remove the guests.
Steps to Diagnose and Force Guest Removal in a New Team
Follow these steps to check the guest activity and remove inactive guests from a newly created team. The steps use the Teams admin center and Azure AD portal.
- Open the Teams admin center and find the team
Go to Teams admin center > Teams > Manage teams. Search for your team name and select it. This shows you the team’s members and guests. - Check the guest list
In the team details, click the Guests tab. Note the guests you want to remove. Copy their email addresses for later steps. - Verify the guest’s last sign-in date
Go to Azure AD > Users > All users. Find the guest account and open its profile. Click Sign-in logs to see the last sign-in. If the log is empty, the guest has never signed in. - Create a new access review for the team’s group
Go to Azure AD > Identity Governance > Access reviews. Click New access review. Select the team’s Microsoft 365 group as the scope. Under Reviewers, choose Group owners or Selected users. - Set the inactivity threshold to 0 days
In the review settings, find Inactive users (within). Set the number of days to 0. This forces the review to flag any guest without recent sign-in activity, including new guests. - Review and apply the results
Start the review and wait for it to complete. Then click Apply to remove the flagged guests. If no guests are flagged, proceed to manual removal. - Manually remove guests from the team
In the Teams admin center, go to Teams > Manage teams, select your team, and click Guests. Select the guest and click Remove. This removes the guest immediately without waiting for a review. - Use PowerShell for bulk removal
Open the Teams PowerShell module and run the Remove-TeamUser cmdlet. Specify the team ID and the guest’s user principal name. This method is faster when you have many guests to remove.
If Teams Guest Review Still Does Not Remove Inactive Guests
Guests Do Not Appear in the Access Review
If the access review shows no guests, you likely selected the wrong group. Teams creates a hidden group with a name that often starts with the team name followed by a random suffix. In the access review creation wizard, click Select group and search for the exact team name. Verify the group type is Microsoft 365.
The Review Flags Guests as Active Even When They Never Signed In
This happens because the signInActivity property is null. Azure AD treats null as active. To work around this, change the inactivity threshold to 0 days and also check the guest’s Last activity in the audit logs. If the guest has no audit events, remove them manually.
Removal Takes More Than 24 Hours
When you apply a review, Azure AD schedules the removal. It can take up to 24 hours to complete. If you need immediate removal, use the Teams admin center or PowerShell instead of waiting for the review to apply.
Guest Cannot Be Removed Because They Own Content
If the guest owns files in the team’s SharePoint site, Teams blocks removal. First, transfer ownership of those files to a team member. Then remove the guest. You can check file ownership in the SharePoint site associated with the team.
Teams Admin Center vs Azure AD Access Review for Guest Removal
| Item | Teams Admin Center Manual Removal | Azure AD Access Review |
|---|---|---|
| Time to remove | Immediate | Up to 24 hours after applying |
| Inactivity detection | None manual check required | Automatic based on sign-in activity |
| Best for new teams | Yes because no activity history exists | No unless you set threshold to 0 days |
| Bulk removal | No one by one | Yes review applies to all flagged guests |
| Requires admin role | Teams administrator | Global administrator or Identity Governance administrator |
For a newly created team, manual removal in the Teams admin center is the most reliable method. Use Azure AD access reviews when you have an established team with clear sign-in history. If you must use a review, set the inactivity threshold to 0 days to catch guests who never signed in.
After removing guests, verify the team’s member list in the Teams admin center. Also check the SharePoint site to ensure the guest no longer has access to files. You can use the Get-TeamUser PowerShell cmdlet to confirm the guest is gone.
For ongoing management, create a recurring access review that runs monthly with an inactivity threshold of 30 days. This prevents inactive guests from accumulating in all your teams. Remember that new teams need manual cleanup until the guest activity data is populated.