Issue with Teams Tenant Switching After Cross-Tenant Synchronization

Question

Issue with Teams Tenant Switching After Cross-Tenant Synchronization

Trong Khuat Dinh 20

Hi All,

We have successfully configured cross-tenant synchronization between our spoke and hub tenants. After performing the necessary configurations, we’ve verified that synchronized users can access both SharePoint and OneDrive resources in the hub tenant without any issues.

However, we are experiencing a problem with Microsoft Teams: While most users can switch to the hub tenant in the Teams client, a few synchronized users are unable to see the hub tenant in their Teams organization switcher, even though they can still access SharePoint and OneDrive in the hub without any problems.

We have already tried the following steps:

Verified that affected users are synchronized and licensed properly.

Confirmed that the users appear in the hub tenant’s Entra ID.

Cleared the Teams client cache and had users sign out and back in.

Despite these efforts, the issue persists for a subset of users only. Could you please help investigate why Teams is not recognizing the hub tenant for these specific users, even though SharePoint and OneDrive access is functioning as expected?

1 answer

Your answer

Answer 1

Alina-Le 1,760 Microsoft External Staff Moderator

Have a nice day @Trong Khuat Dinh

Welcome to Q&A forum!

Thank you for your detailed guidance and effort to troubleshooting this issue. This issue usually relates to Teams-specific service provisioning or consent settings. Let work together to sort it out:

1. Check if the user is a “Guest” or “Member” in the hub tenant

Go to Microsoft Entra admin center -> Users in the hub tenant.
Confirm the user’s user type:
- If they are listed as "Guest", try converting them to "Member".
- Some Teams features (like tenant switching) behave differently for Guests.

2. Trigger Teams Provisioning:

Temporarily assign a Teams license in the hub tenant to the affected user. You can assign any Microsoft 365 license that includes Microsoft Teams (Microsoft 365 E3/E5, Microsoft 365 Business Basic/Standard/Premium)
Wait up to 24 hours for provisioning to complete.

Then remove the license if not needed long-term.

3. Check Consent Prompt:

This step is meant to ensure that the user has accepted the required permissions to access Microsoft Teams in the hub tenant (after cross-tenant synchronization).

When a user logs into Microsoft Teamsfor the first time in a new tenant (like your hub tenant), Microsoft may show a consent prompt asking them to approve access. (When you sign in to Microsoft Teams, you’ll first land in your home tenant (in your case, the spoke tenant). If your account has been synchronized to another tenant (like the hub tenant) through cross-tenant synchronization, you’ll see the hub tenant listed in the Teams organization switcher—usually in the top-right corner of the Teams app.)
If the user skips or doesn’t complete this prompt, they might not be fully onboarded into Teams for that tenant.
As a result, they won’t see the hub tenant in their Teams organization switcher—even though they can access SharePoint or OneDrive.

4. Review Cross-Tenant Access Settings:

In Microsoft Entra admin center (hub tenant):

Go to External Identities → Cross-tenant access settings → Default settings -> Inbound Access Settings -> Edit inbound defaults.
Select the "spoke tenant".

User's image Under B2B direct connect, check:

Is Teams listed under allowed applications?
Are there user/group filters applied that might exclude the affected users?

Make sure the affected users are included in the allowed groups or conditions. User's image

5. Try removing and re-adding the user in the hub tenant

Remove the affected user from the hub tenant (if safe to do so).
Wait for 15–30 minutes.
Let cross-tenant sync re-add them.
This can reset any stuck provisioning state.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

User's image

Trong Khuat Dinh 20 Reputation points

2025-08-05T06:23:50.6333333+00:00

We realized that this issue only affects users who were previously added as guest users in Teams group chats before the MTO synchronization. When we try removing them from those groups, they are then able to see and switch to the hub tenant in Teams.

However, we don't believe this is a safe or scalable solution. We are looking for a proper and secure resolution. Could you please help us investigate and resolve this issue?
Alina-Le 1,760 Reputation points Microsoft External Staff Moderator

2025-08-05T10:50:42.19+00:00
Hi @Trong Khuat Dinh

Thank you for your update. That’s a helpful clue. It makes sense that this issue is tied to users who were previously added as guest users in Teams group chats before the Microsoft Teams Organization (MTO) synchronization.

If i understand correctly, this issue is likely caused by conflicting identity records in Microsoft Entra ID and Teams:

When users were added as guests before MTO sync, Teams stored them with a guest identity tied to their original tenant.

After MTO sync, these users now have a cross-tenant synchronized identity, but Teams may still prioritize the old guest identity for tenant switching.

This conflict prevents Teams from recognizing the new hub tenant as an available organization to switch to.

Even though SharePoint and OneDrive use Entra ID for access control, Teams uses cached identity metadata that can persist across sessions and cause switching issues.

Here are my suggestions for you in this situation:

Step 1: Find the Users Who Were Previously Guests

You’ll need to check if the affected users still exist as "guest accounts" in your system.

Go to the Microsoft Entra Admin Center

Click on “Users” in the left-hand menu

Use the Filter to Find Guest Users

At the top of the user list, click “Add filters”.

Choose “User type”.

Set the filter to “Guest”.

Click "Apply".

Step 2: Remove the Old Guest Account (Safely)

Once you confirm a user is still listed as a guest:

Click on their name in the list.

At the top, click Delete user (This only removes the guest version of the user, it won’t affect their synced account or access to SharePoint/OneDrive.)

After deleting, ask the user to:

Sign out of Teams.

Clear their Teams cache (or restart the app).

Sign back in.

They should now be able to switch to the hub tenant in Teams.

Step 3: Re-Add Them to Teams Groups (If Needed)

If the user was part of any Teams chats or groups as a guest, you can re-add them using their "new synced account". This ensures they still have access to everything they need.Please feel free to reach out me again if you still have any questions or concerns.

If you think my answer is helpful to you, please click "Accept Answer" and kindly upvote it. This helps highlight the response at the top, making it easier for others in the community to quickly find the information they need.

Be safe and happy,
Trong Khuat Dinh 20 Reputation points

2025-08-06T14:27:41.8566667+00:00

Today, we also tried adding a new user who was never a guest in any group, but they still can’t switch tenants in Teams.

we can find these users in Teams, but they are unable to switch to the hub tenant.
Alina-Le 1,760 Reputation points Microsoft External Staff Moderator

2025-08-07T15:09:12.9433333+00:00
Hi @Trong Khuat Dinh

Thank you for your update.

After synchronization, Teams provisioning can take up to 48 hours. If the user was just added today, it may still be processing.

If it is over 48 hours, let’s walk through a more complete set of checks to see if it helps:

Confirm Licensing

Ensure that synchronized users have a valid Microsoft Teams license assigned in the spoke tenant.

Teams switching requires that users are licensed in their home tenant.

Test with Teams Web Client

Ask affected users to log in at teams.microsoft.com

Sometimes the desktop client doesn’t reflect tenant switching properly due to cached tokens.

Besides, to make sure we are on the same page, may I confirm:

Have you completed the troubleshooting steps I previously shared?

Have you reviewed the cross-tenant access settings in Microsoft Entra for both inbound and outbound access?

Do the affected users appear twice in Microsoft Entra ID (once as guest, once as synchronized)?

Are the affected users part of any Teams groups or chats created before synchronization?

This will help me address your issue more effectively.
Alina-Le 1,760 Reputation points Microsoft External Staff Moderator

2025-08-08T15:11:04.3833333+00:00

Good day @Trong Khuat Dinh

I hope you're doing well and that this message reaches you at a good time.

If you still have any concerns or questions about this issue, feel free to share a few details, we’ll figure it out together.

In the meantime, I’ll be assisting others on the forum, but if you need a quicker response, just tag me in your message and I’ll jump in right away.

Stay safe & happy!

Share via

Issue with Teams Tenant Switching After Cross-Tenant Synchronization

1 answer

Your answer