Home

Unable to chat with external people

%3CLINGO-SUB%20id%3D%22lingo-sub-297224%22%20slang%3D%22en-US%22%3EUnable%20to%20chat%20with%20external%20people%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-297224%22%20slang%3D%22en-US%22%3E%3CP%3EWe're%20planning%20a%20complete%20migration%20from%20Skype%20onprem%20to%20Teams%20with%20outbound%20calling.%3C%2FP%3E%3CP%3EOne%20of%20the%20things%20that%20I'm%20testing%20before%20the%20migration%20is%20chatting%20with%20people%20outside%20the%20organization%20as%20this%20is%20a%20heavily%20used%20feature.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMost%20of%20the%20times%20messages%20don't%20get%20delivered.%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20271px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F62082i7BFBC6898BFE0353%2Fimage-dimensions%2F271x250%3Fv%3D1.0%22%20width%3D%22271%22%20height%3D%22250%22%20alt%3D%222018-12-07%2009_04_42-Window.png%22%20title%3D%222018-12-07%2009_04_42-Window.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EI've%20tested%20it%20with%20our%20corporate%20tenant%20to%20external%20tenants%20and%20only%201%20in%2010%20tests%20succeeded%20(and%20that%20user%20is%20still%20a%20Skype%20for%20Business%20user).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20also%20tested%20it%20from%20several%20test%2C%20dev%20and%20other%20'normal'%20tenants%20in%20various%20settings%20and%20in%20about%2090%25%20it%20fails.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20solution%20to%20this%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-297224%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EChat%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-382613%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20chat%20with%20external%20people%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-382613%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F867%22%20target%3D%22_blank%22%3E%40Martijn%20Eikelenboom%3C%2FA%3E-%20we're%20experiencing%20exactly%20the%20same%20problem%20-%20did%20you%20find%20a%20solution%20please%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-300899%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20chat%20with%20external%20people%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-300899%22%20slang%3D%22en-US%22%3EYes%20you%20are%20exactly%20right%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-298866%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20chat%20with%20external%20people%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-298866%22%20slang%3D%22en-US%22%3E%3CP%3ETesting%20with%20somebody%20else%20(lets%20say%20personx%40acme.com)%20I%20get%20this%20error%20message%20in%20Teams%20when%20I%20use%20a%20user%20that's%20teams%20only%20and%20the%20other%20is%20on%20Skype%3A%3C%2FP%3E%3CP%3E%22%3CSPAN%3EWe%20can't%20set%20up%20the%20conversation%20because%20your%20organizations%20are%20not%20set%20up%20to%20talk%20to%20each%20other.%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EAnd%20when%20I%20chat%20with%20the%20same%20user%20(personx%40acme.com)%20from%20another%20skype%20account%20in%20my%20tenant%20I%20can%20chat%20without%20any%20issues.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-298853%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20chat%20with%20external%20people%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-298853%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20planning%20to%20set%20the%20whole%20tenant%20to%20be%20Teams%20only.%20For%20testing%20purposes%20I've%20set%20one%20user%20to%20teams%20only%20and%20after%20a%20while%20with%20Microsoft%20Support%2C%20I%20come%20to%20the%20conclusion%20that%20the%20only%20case%20that%20doesn't%20work%20is%20Teams%20only%20to%20Teams%20only%20in%20another%20tenant.%26nbsp%3B%3C%2FP%3E%3CP%3EAll%20other%20cases%20seem%20to%20work%20now%2C%20or%20have%20worked%20in%20the%20passed%20(I%20just%20put%20them%20all%20together%20as%20one%20issue).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-298426%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20chat%20with%20external%20people%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-298426%22%20slang%3D%22en-US%22%3EHi%2C%3CBR%20%2F%3E%3CBR%20%2F%3EIs%20it%20throwing%20any%20error%20while%20adding%20external%20users%3F%20something%20like%20%22%22We%20couldn't%20add%20member.%20We%20ran%20into%20an%20issue.%20Please%20try%20again%20later.%22%3F%3CBR%20%2F%3E%3CBR%20%2F%3EPlease%20have%20a%20looked%20at%20the%20thread%20here%20..%3CBR%20%2F%3E%22When%20I%20leave%20Skype%20closed%2C%20some%20users%20show%20up%20as%20Skype%20users%20but%20every%20message%20gets%20back%20%22Failed%20to%20send.%20We%20ran%20into%20a%20problem%20sending%20this%20message.%20Try%20again%20later.%22%20which%20forces%20me%20to%20use%20the%20Skype%20client%20to%20chat%20with%20the%20person%22%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-Teams%2FMigration-and-Skype-chat-migration-sync-tips%2Ftd-p%2F125783%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-Teams%2FMigration-and-Skype-chat-migration-sync-tips%2Ftd-p%2F125783%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EHope%20this%20helps!%3CBR%20%2F%3EThuyavan%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-298407%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20chat%20with%20external%20people%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-298407%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20you%20don't%20trust%20me%20eh%3F%20%3A)%3C%2Fimg%3E%20Simply%20do%20a%20search%20in%20this%20space%2C%20you%20will%20find%20numerous%20threads%20with%20examples.%20In%20all%20fairness%2C%20they%20are%20working%20on%20improving%20things%2C%20but%20it's%20sure%20taking%20a%20lot%20of%20time...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-298161%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20chat%20with%20external%20people%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-298161%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Vasil%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20responding.%20Is%20this%20personal%20experience%20or%20do%20you%20have%20more%20information%20on%20this%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-297448%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20chat%20with%20external%20people%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-297448%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20you%20have%20high%20usage%20of%20federated%20chat%2Fcalls%2C%20I%20would%20strongly%20recommend%20you%20to%20postpone%20the%20migration%20to%20Teams%20for%20the%20time%20being.%20There%20are%20tons%20of%20issues%20with%20it%2C%20starting%20from%20the%20simple%20scenario%20of%20being%20able%20to%20see%20your%20federated%20contacts%20in%20the%20Contacts%20list.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-439394%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20chat%20with%20external%20people%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-439394%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F867%22%20target%3D%22_blank%22%3E%40Martijn%20Eikelenboom%3C%2FA%3EAnd%20we%20are%20also%20experiencing%20this%20exact%20problem%20now.%20Any%20solutions%20yet%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-440388%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20chat%20with%20external%20people%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-440388%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F108638%22%20target%3D%22_blank%22%3E%40Irene%20Lappalainen%3C%2FA%3E%26nbsp%3B%3CSPAN%3EI%E2%80%99ve%20looked%20into%20this%20in%20some%20detail%20with%20Microsoft%20and%20they%20think%20that%20the%20issue%20is%20to%20do%20with%20missing%20DNS%20records%20against%20the%20other%20company's%20tenant%20(which%20presumably%20Teams%20relies%20on%2C%20but%20Skype%20for%20business%20doesn%E2%80%99t).%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EThey%E2%80%99ve%20sent%20the%20following%20link%20to%20the%20relevant%20support%20documentation%20and%20suggested%20that%20the%20other%20company%20need%20to%20add%20the%20%E2%80%98lyncdiscover%E2%80%99%20and%20%E2%80%98sip%E2%80%99%20CNAME%20records%20for%20Teams-to-Teams%20messaging%20with%20external%20organisations%20such%20as%20ourselves%20to%20work%3A%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Fadmin%2Fget-help-with-domains%2Fcreate-dns-records-at-any-dns-hosting-provider%3Fview%3Do365-worldwide%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Fadmin%2Fget-help-with-domains%2Fcreate-dns-records-at-any-dns-hosting-provider%3Fview%3Do365-worldwide%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EDon't%20know%20if%20this%20is%20the%20solution%20yet%20as%20it%20will%20take%20time%20for%20a%20multi-national%20to%20change%20DNS%20settings%2C%20but%20keeping%20my%20fingers%20crossed.%26nbsp%3B%20They%20also%20suggested%20adding%20the%20other%20company's%20domain%20to%20our%20trusted%20list%20(even%20though%20we're%20set%20up%20to%20message%20anyone)%2C%20but%20that%20didn't%20appear%20to%20work.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Martijn Eikelenboom
Contributor

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.

2018-12-07 09_04_42-Window.png

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?

10 Replies

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.

Hi Vasil,

 

Thanks for responding. Is this personal experience or do you have more information on this?

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...

Hi,

Is it throwing any error while adding external users? something like ""We couldn't add member. We ran into an issue. Please try again later."?

Please have a looked at the thread here ..
"When I leave Skype closed, some users show up as Skype users but every message gets back "Failed to send. We ran into a problem sending this message. Try again later." which forces me to use the Skype client to chat with the person"

https://techcommunity.microsoft.com/t5/Microsoft-Teams/Migration-and-Skype-chat-migration-sync-tips/...

Hope this helps!
Thuyavan

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).

Testing with somebody else (lets say personx@acme.com) 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 (personx@acme.com) from another skype account in my tenant I can chat without any issues.

Yes you are exactly right

@Martijn Eikelenboom- we're experiencing exactly the same problem - did you find a solution please?

@Martijn EikelenboomAnd we are also experiencing this exact problem now. Any solutions yet?

@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:

 

https://docs.microsoft.com/en-us/office365/admin/get-help-with-domains/create-dns-records-at-any-dns...

 

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.