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
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.- It's definitely a fecal display with respect to Teams. It's working well for us for Sharepoint. We've had some weird problem where MailUsers didn't get created for some sync'd users, and had to hard-delete those and provision-on-demand them to get the MailUsers created.
Side note, inter-company DM took all of 2 minutes to setup in Slack. Created a channel, shared it to an admin on the other side, and then added the channel to the default channel list for our respective "all users" Slack groups.
