Forum Discussion
MS Teams in Cross-Tenant synchronization
GSJLusky have you heard anything back yet? This is causing me the same issues and getting really noisy for me
Walmsleyj1 Ive had nothing yet but a also have a ticket in with MS so when I get something back I will post
- Nope Sorry I now done two requests with MS Support, and it seems to go into a black hole. I keep asking for a new engineer to look at it but I get no replies from MS Support....
For now, I have just reverted all changes. and maybe Ill look at it again in 6 months... hopefully this is a lot more polished by then....
- Same issues in Teams as mentioned above. Further, now that Cross Tenant Sync is configured, I can not add those synced users to Teams Shared Channels. Rather, if I enter their full email address it "sometimes" resolves as External and will allow me to add them otherwise the error message when adding a sync'd user is "Something Went Wrong".
Anyone else seeing this?
I have also tried syncing the users as Guests instead of Members to no avail. I cannot seem to find any good info on the differences/features of External Guest vs External Member. Anyone else?
Has anyone played with sip address in the attribute transformations?
I'm not home to test but could adding a mapping fix this?
Our ticket got escalated to the Teams team, and radio silence since then.
We have two workarounds that I'm giving to end-users. First, when they search for a name in Teams to send a DM, search for their email address in the search bar and DO NOT HIT ENTER. There will be a link in the search preview results to Search <email address> externally. Click on Search externally link, and then you'll see a Contact Name (External) result for them--clicking on that will send them a DM that they'll actually get.
The second workaround is to login to both tentants. I give them a link to https://teams.microsoft.com/_?tenantId=<OtherTenantID> and some explanation on logging in with their normal AzAD credentials. If they are logged into both, they can flip between tenants to see messages that have received in each. It's a headache, but it beats having DMs that you've never seen.
I started down the same road but it was too much of a change.
We saw this issue plus UPN mismatch causing sharing issues and cross tenant guests being added to Org wide Teams which was really fun...
I've had to revert back to mail contacts and allowing manual invites to create azure guests.
