SOLVED

Message could not be delivered. Your organizations are not set up to talk to each other.

%3CLINGO-SUB%20id%3D%22lingo-sub-1150506%22%20slang%3D%22en-US%22%3EMessage%20could%20not%20be%20delivered.%20Your%20organizations%20are%20not%20set%20up%20to%20talk%20to%20each%20other.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1150506%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20from%20a%20chat%20I%20tried%20with%20an%20external%20team%20member.%26nbsp%3B%20Why%20is%20this%20not%20working%20any%20lon%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1150506%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ETeams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1150615%22%20slang%3D%22en-US%22%3ERe%3A%20Message%20could%20not%20be%20delivered.%20Your%20organizations%20are%20not%20set%20up%20to%20talk%20to%20each%20other.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1150615%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F544733%22%20target%3D%22_blank%22%3E%40lknutson%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20is%20usually%20because%20users%20are%20in%20different%20tenants%2C%20and%20either%20your%20organisation%2C%20or%20their%20organisation%2C%20either%20has%20external%20access%20disabled%20in%20the%20Teams%20Admin%20Centre%20or%20only%20set%20to%20work%20with%20specific%20domains%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Teams%20External%20Access.PNG%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F168977i3C846CB9C0A91085%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22Teams%20External%20Access.PNG%22%20alt%3D%22Teams%20External%20Access.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESolution%20would%20be%20to%20raise%20to%20your%20IT%20admin%20to%20check%20and%20correct%2C%20and%20for%20them%20to%20also%20raise%20to%20their%20IT%20admin%20to%20check%20and%20correct%20to%20ensure%20your%20organisations%20can%20talk%20to%20one%20another.%20Unfortunately%2C%20this%20may%20be%20a%20policy%20in%20one%20of%20the%20organisations%20has%20knowingly%20applied%20so%20it%20would%20be%20up%20to%20them%20to%20allow%20you%20both%20to%20talk%20to%20each%20other.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHope%20that%20answers%20your%20question!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBest%2C%20Chris%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2502269%22%20slang%3D%22en-US%22%3ERe%3A%20Message%20could%20not%20be%20delivered.%20Your%20organizations%20are%20not%20set%20up%20to%20talk%20to%20each%20other.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2502269%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F169605%22%20target%3D%22_blank%22%3E%40Christopher%20Hoard%3C%2FA%3E%26nbsp%3BI%20know%20this%20is%20an%20older%20thread%2C%20but%20wanted%20to%20know%20what%20would%20cause%20it%20suddenly%20stop%20working%20when%20it%20had%20been%20working%20earlier%20in%20the%20day.%26nbsp%3B%20Both%20groups%20say%20that%20they%20have%20not%20changed%20anything%20knowlingly.%26nbsp%3B%20Are%20there%20specific%20setting%20to%20point%20the%20admins%20toward%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2505525%22%20slang%3D%22en-US%22%3ERe%3A%20Message%20could%20not%20be%20delivered.%20Your%20organizations%20are%20not%20set%20up%20to%20talk%20to%20each%20other.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2505525%22%20slang%3D%22en-US%22%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1092138%22%20target%3D%22_blank%22%3E%40malukalyk2%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EJust%20to%20clarify%20-%20In%20terms%20of%20federated%20chat%20not%20working%3F%20%3CBR%20%2F%3E%3CBR%20%2F%3EBest%2C%20Chris%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2505530%22%20slang%3D%22en-US%22%3ERe%3A%20Message%20could%20not%20be%20delivered.%20Your%20organizations%20are%20not%20set%20up%20to%20talk%20to%20each%20other.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2505530%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F169605%22%20target%3D%22_blank%22%3E%40Christopher%20Hoard%3C%2FA%3E%26nbsp%3B%20No%20federation.%26nbsp%3B%20I%20have%20been%20able%20to%20start%20a%20chat%20and%20look%20for%20an%20address%20that%20is%20external%20and%20communicate.%26nbsp%3B%20With%20Skype%20connectors%2C%20the%20abilities%20have%20been%20limited%2C%20but%20I%20have%20been%20able%20to%20chat.%26nbsp%3B%20With%20fellow%20Team%20users%2C%20no%20link%20between%20companies%2C%20there%20are%20more%20options.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYesterday%2C%20I%20had%20texted%20and%20I%20had%20sent%20some%20screen%20captures%20for%20that%20past%20few%20months.%26nbsp%3B%20Sometime%20after%2010am%20PDT%2C%20it%20all%20stopped.%26nbsp%3B%20The%20user%20was%20marked%20as%20unknown%20and%20messages%20sent%20that%20we%20could%20not%20communicate%20as%20our%20companies%20had%20not%20been%20set%20up.%26nbsp%3B%20Other%20outside%20contacts%20still%20work%20in%20both%20of%20our%20respective%20companies.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2505534%22%20slang%3D%22en-US%22%3ERe%3A%20Message%20could%20not%20be%20delivered.%20Your%20organizations%20are%20not%20set%20up%20to%20talk%20to%20each%20other.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2505534%22%20slang%3D%22en-US%22%3EI%20see%3CBR%20%2F%3E%3CBR%20%2F%3EIn%20this%20case%2C%20get%20both%20admins%20to%20check%3CBR%20%2F%3E%3CBR%20%2F%3E1.)%20That%20both%20orgs%20are%20in%20Teams%20Only%20in%20upgrade%20settings%3CBR%20%2F%3E2.)%20That%20external%20access%20is%20on%3CBR%20%2F%3E3.)%20That%20they%20haven't%20blocked%20this%20per%20domain%3CBR%20%2F%3E4.)%20Attempt%20to%20start%20a%20chat%20in%20the%20web%20and%20mobile%20app%20-%20does%20that%20work%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20it%20doesn't%20work%2C%20get%20them%20to%20raise%20a%20ticket%20to%20Microsoft%3CBR%20%2F%3E%3CBR%20%2F%3EBest%2C%20Chris.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2554233%22%20slang%3D%22en-US%22%3ERe%3A%20Message%20could%20not%20be%20delivered.%20Your%20organizations%20are%20not%20set%20up%20to%20talk%20to%20each%20other.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2554233%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1092138%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1092138%3C%2FA%3E%20Did%20you%20ever%20solve%20this%20issue.%20I%20had%20a%20similar%20experience%20back%20in%20May.%20I%20was%20talking%20to%20client%20in%20my%20tenant%20for%20over%20a%20year.%20Then%20this%20stopped%2C%20and%20eventually%20the%20clients%20tenant%20showed%20up%20at%20the%20top%20right%20of%20Teams%20and%20I%20could%20now%20chat%20with%20them%2C%20only%20when%20I%20switched%20tenants.%20Unfortunately%2C%20when%20someone%20chats%20with%20me%20now%2C%20I%20do%20not%20see%20notification%20unless%20I%20am%20connected%20to%20their%20tenant%20and%20not%20mine.%3CBR%20%2F%3EI%20went%20and%20checked%20the%20settings%20for%20both%20tenants%20and%20it%20looked%20liked%20the%20external%20access%20for%20allowed%20domains%20was%20gone.%20I%20reset%20for%20both%20tenants%20and%20waited%20a%20day.%20Tried%20to%20chat%20with%20user%20and%20received%20the%20error%20you%20posted.%3CBR%20%2F%3EJust%20checking%20if%20you%20found%20anything%20out.%20This%20was%20working%20since%20Jan.%202020.%3CBR%20%2F%3EThank%20you%2C%3CBR%20%2F%3EVictor%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

This is from a chat I tried with an external team member.  Why is this not working any lon

6 Replies
best response confirmed by Christopher Hoard (MVP)
Solution

Hi @lknutson 

 

This is usually because users are in different tenants, and either your organisation, or their organisation, either has external access disabled in the Teams Admin Centre or only set to work with specific domains

 

Teams External Access.PNG

 

Solution would be to raise to your IT admin to check and correct, and for them to also raise to their IT admin to check and correct to ensure your organisations can talk to one another. Unfortunately, this may be a policy in one of the organisations has knowingly applied so it would be up to them to allow you both to talk to each other. 

 

Hope that answers your question!

 

Best, Chris

@Christopher Hoard I know this is an older thread, but wanted to know what would cause it suddenly stop working when it had been working earlier in the day.  Both groups say that they have not changed anything knowlingly.  Are there specific setting to point the admins toward?

Hi @malukalyk2

Just to clarify - In terms of federated chat not working?

Best, Chris

@Christopher Hoard  No federation.  I have been able to start a chat and look for an address that is external and communicate.  With Skype connectors, the abilities have been limited, but I have been able to chat.  With fellow Team users, no link between companies, there are more options.

 

Yesterday, I had texted and I had sent some screen captures for that past few months.  Sometime after 10am PDT, it all stopped.  The user was marked as unknown and messages sent that we could not communicate as our companies had not been set up.  Other outside contacts still work in both of our respective companies.

I see

In this case, get both admins to check

1.) That both orgs are in Teams Only in upgrade settings
2.) That external access is on
3.) That they haven't blocked this per domain
4.) Attempt to start a chat in the web and mobile app - does that work

If it doesn't work, get them to raise a ticket to Microsoft

Best, Chris.

https://techcommunity.microsoft.com/t5/user/viewprofilepage/user-id/1092138 Did you ever solve this issue. I had a similar experience back in May. I was talking to client in my tenant for over a year. Then this stopped, and eventually the clients tenant showed up at the top right of Teams and I could now chat with them, only when I switched tenants. Unfortunately, when someone chats with me now, I do not see notification unless I am connected to their tenant and not mine.
I went and checked the settings for both tenants and it looked liked the external access for allowed domains was gone. I reset for both tenants and waited a day. Tried to chat with user and received the error you posted.
Just checking if you found anything out. This was working since Jan. 2020.
Thank you,
Victor