12-07-2018 12:08 AM
12-07-2018 12:08 AM
We're planning a complete migration from Skype onprem to Teams with outbound calling.
One of the things that I'm testing before the migration is chatting with people outside the organization as this is a heavily used feature.
Most of the times messages don't get delivered.
I've tested it with our corporate tenant to external tenants and only 1 in 10 tests succeeded (and that user is still a Skype for Business user).
I've also tested it from several test, dev and other 'normal' tenants in various settings and in about 90% it fails.
Any solution to this?
12-07-2018 08:47 AM
If you have high usage of federated chat/calls, I would strongly recommend you to postpone the migration to Teams for the time being. There are tons of issues with it, starting from the simple scenario of being able to see your federated contacts in the Contacts list.
12-10-2018 12:44 AM
Thanks for responding. Is this personal experience or do you have more information on this?
12-10-2018 09:51 AM
So you don't trust me eh? :) Simply do a search in this space, you will find numerous threads with examples. In all fairness, they are working on improving things, but it's sure taking a lot of time...
12-10-2018 10:47 AM
12-11-2018 04:41 AM
I'm planning to set the whole tenant to be Teams only. For testing purposes I've set one user to teams only and after a while with Microsoft Support, I come to the conclusion that the only case that doesn't work is Teams only to Teams only in another tenant.
All other cases seem to work now, or have worked in the passed (I just put them all together as one issue).
12-11-2018 05:14 AM
Testing with somebody else (lets say firstname.lastname@example.org) I get this error message in Teams when I use a user that's teams only and the other is on Skype:
"We can't set up the conversation because your organizations are not set up to talk to each other."
And when I chat with the same user (email@example.com) from another skype account in my tenant I can chat without any issues.
04-11-2019 12:34 PM
@Irene Lappalainen I’ve looked into this in some detail with Microsoft and they think that the issue is to do with missing DNS records against the other company's tenant (which presumably Teams relies on, but Skype for business doesn’t).
They’ve sent the following link to the relevant support documentation and suggested that the other company need to add the ‘lyncdiscover’ and ‘sip’ CNAME records for Teams-to-Teams messaging with external organisations such as ourselves to work:
Don't know if this is the solution yet as it will take time for a multi-national to change DNS settings, but keeping my fingers crossed. They also suggested adding the other company's domain to our trusted list (even though we're set up to message anyone), but that didn't appear to work.
03-24-2020 09:06 AM
few years late though in case someone else is having the same issue and searching for responses, I would first recommend to check the Org-wide settings via Teams Admin center -> "Org-wide settings" -> "External access":
05-14-2020 11:03 AM
We have the external access enabled in teams site org. when someone external to our company tries to chat, it defaults to the onmicrosoft.com account rather than our domain name...not sure if that's why. But they then get a message that the user is unavailable or offline. Any help would be appreciated
09-10-2020 07:48 AM
It is Sep 10th 2020 and this same problem persists.
To create a communication eco-system one must first consider legacy upgrade paths and consider communication channels must (not should or could) be resilient aka a priority. Meaning if we used Skype Business and then transition comms. channels to teams it should migrate without any problems. And yes it's achievable.
From Teams, you cannot chat with anyone external
From Skype for business, you cannot chat with anyone external
Please fix this.
Try setting up a vanilla infra with Teams and Skype for business, then try and contact anyone via Teams chat who uses a Skype ID or Gmail ID or Yahoo ID
<----- Why in 2020 ?
No not try again, State the error so someone can troubleshoot.
No not try again, Say we are not yet done testing (UAT or TDD our projects here).
Anything other than this please!