You use the Teams admin center guest review policy to automatically remove inactive guests from your tenant. After renaming your Microsoft 365 tenant, the guest review process stops working and inactive guests remain in your directory. This happens because the guest review policy stores the old tenant name in its configuration, and the cleanup job can no longer match the expected domain. This article explains the root cause, shows you how to repair the policy, and lists related failure patterns you may encounter.
The guest review feature is part of Teams meeting policies and relies on Azure AD to identify and remove guests who have not signed in for a set number of days. When you rename the tenant, the primary domain and the onmicrosoft.com domain change, but the policy may still reference the old values. You will learn how to verify the policy, update it correctly, and confirm that inactive guests are removed as expected.
Key Takeaways: Repairing Guest Review After a Tenant Rename
- Teams admin center > Meetings > Meeting policies > Guest review: Shows the toggle and the inactivity period that control automatic guest removal.
- Azure AD > Users > Guest users: Lists all guest accounts and their last sign-in time, which you use to verify the cleanup worked.
- Microsoft 365 admin center > Settings > Org settings > Organization profile: Displays the current tenant name and primary domain after the rename.
Why Guest Review Fails After a Tenant Rename
The guest review feature in Teams is a meeting policy that triggers a background job in Azure AD. That job scans all guest users in the tenant and checks their last sign-in date. If a guest has not signed in for more than the number of days you set, the job removes the guest account from the directory.
When you rename a tenant, Microsoft 365 changes the primary domain and the initial onmicrosoft.com domain. The guest review policy stores a reference to the tenant name and domain in its internal configuration. After the rename, the policy still points to the old tenant identifier. The Azure AD cleanup job tries to match the old domain against the current directory and finds no matches. As a result, the job completes without removing any guests, and you see no error message in the admin center.
Another factor is that the guest review policy is tied to the meeting policy object in Teams. The meeting policy object may retain the old tenant context after the rename. This is a known behavior when the tenant rename is performed through the Microsoft 365 admin center without updating all dependent services.
What the Guest Review Policy Actually Controls
The guest review policy has two settings: the toggle to enable or disable the feature, and the number of days after which a guest is considered inactive. The default is 30 days. The policy applies to all meetings in the tenant, not to individual users or teams. You cannot scope the policy to a specific team or channel.
Steps to Repair Guest Review After a Tenant Rename
Follow these steps in order. You need global admin or Teams admin permissions to complete the repair.
- Verify the current tenant name and primary domain
Sign in to the Microsoft 365 admin center at admin.microsoft.com. Go to Settings > Org settings > Organization profile. Note the current organization name and the primary domain. This is the new tenant name that the guest review policy must reference. - Open the Teams meeting policy that contains guest review
Go to the Teams admin center at admin.teams.microsoft.com. Navigate to Meetings > Meeting policies. Select the policy that has guest review enabled. Usually it is the Global (Org-wide default) policy, but it could be a custom policy. - Disable guest review and save the policy
Find the Guest review setting and turn it off. Click Save. This forces the policy to release the old tenant reference. - Wait 15 minutes
The policy change needs time to propagate across the Teams infrastructure. Do not skip this wait. - Re-enable guest review with the same inactivity period
Go back to the same meeting policy. Turn Guest review back on. Set the days to the value you used before, for example 30 days. Click Save. - Confirm the policy now references the new tenant name
Open the policy again and verify that the setting is on. There is no direct field that shows the tenant name, but the re-save action updates the underlying configuration. - Trigger a manual guest review check
In the Teams admin center, go to Users > Guest users. Review the list of guests and their last activity. You can also use Azure AD to check the last sign-in time for each guest. - Verify that inactive guests are removed
Wait 24 to 48 hours after re-enabling the policy. Then go to Azure AD > Users > Guest users. Confirm that guests with a last sign-in time older than your threshold are no longer in the list. If they are still present, repeat the disable and enable cycle and wait another 48 hours.
If Guests Still Are Not Removed After the Repair
Sometimes the repair does not work immediately. The following issues are common after a tenant rename.
Guest Review Is Enabled but No Guests Are Removed
Check the last sign-in time for the guest accounts. If the guest has signed in within the inactivity period, the policy correctly keeps them. Also verify that the guest is not a member of a group that has a separate retention policy. Azure AD may block removal if the guest is a member of a dynamic group.
The Guest Review Policy Toggle Turns Off by Itself
This can happen if another admin changes the policy after you re-enable it. Check the audit log in the Microsoft 365 admin center to see who modified the policy. If the toggle turns off repeatedly, create a new custom meeting policy and apply it to the users who need guest review.
Guest Review Removes the Wrong Guests
The policy removes any guest whose last sign-in is older than the threshold. If you have guests who are still active but have not signed in recently, they will be removed. Set a longer inactivity period, such as 90 days, to reduce the risk.
Guest Review After Tenant Rename: Policy States Compared
| Item | Before Tenant Rename | After Tenant Rename (Broken) |
|---|---|---|
| Policy reference | Old tenant name and domain | Still points to old tenant name and domain |
| Cleanup job behavior | Matches guests and removes inactive ones | Finds no matches, completes silently |
| Admin center status | Shows the policy as enabled | Shows the policy as enabled, no error |
| Guest accounts | Inactive guests are removed | Inactive guests remain in the directory |
You can now repair the guest review policy after a tenant rename. The fix is to disable the policy, wait, and re-enable it so it picks up the new tenant name. After the repair, verify that inactive guests are removed from Azure AD. If you manage multiple custom meeting policies, run the same disable and enable cycle on each policy that has guest review enabled. For a more robust approach, create a dedicated custom policy for guest review and assign it only to the users who need it.