Microsoft Tech Community Live:  Microsoft Teams Edition
November 09, 2021, 08:00 AM - 12:00 PM (PST)

Skype Consumer unable to message Teams users without Teams users first intiating contact

%3CLINGO-SUB%20id%3D%22lingo-sub-2787305%22%20slang%3D%22en-US%22%3ESkype%20Consumer%20unable%20to%20message%20Teams%20users%20without%20Teams%20users%20first%20intiating%20contact%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2787305%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20an%20issue%20where%20Skype%20consumer%20messages%20will%20not%20come%20through%20to%20teams%20users%20unless%20the%20teams%20user%20first%20messages%20the%20skype%20consumer%20user.%20In%20addition%2C%20after%20the%20teams%20user%20messages%20the%20skype%20user%2C%20back%20and%20forth%20messaging%20will%20work%20for%20awhile(6%20hours%20or%20so)%2C%20then%20the%20skype%20consumer%20user%20will%20once%20again%20not%20be%20able%20to%20message%20the%20teams%20user%20unless%20the%20teams%20user%20once%20again%20initiates%20the%20conversation.%20Regardless%20if%20the%20teams%20user%20initiates%20conversation%20or%20not%2C%20if%20the%20skype%20consumer%20user%20tries%20to%20call%20the%20teams%20user%2C%20it%20will%20fail%20100%25%20of%20the%20time.%20It%20rings%20on%20the%20teams%20user%20end%2C%20but%20when%20they%20answer%20the%20call%2C%20it%20still%20stays%20at%20%22ringing%22%20and%20will%20never%20connect.%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%202%20open%20tickets%20with%20Microsoft%20365%20support%20currently%2C%20they%20are%20unable%20to%20find%20a%20solution%20to%20this.%3C%2FP%3E%3CP%3EAll%20DNS%20entries%20are%20verified%2C%20all%20settings%20appear%20to%20be%20correct.%3C%2FP%3E%3CP%3EThis%20initially%20started%20when%20I%20created%20a%20new%20tenant%20in%20the%20Australia%20region%2C%20at%20first%20I%20thought%20it%20was%20isolated%20to%20the%20Australia%20region%20because%20I%20have%20set%20up%20over%20100%20tenants%2C%20I%20created%20test%20teams%20users%20on%20about%209%20of%20those%20tenants%2C%20and%20they%20all%20worked(these%20were%20all%20in%20the%20US%20region).%26nbsp%3B%3C%2FP%3E%3CP%3EI%20then%20migrated%20data%20from%20the%20Australian%20tenant%20over%20to%20a%20new%20US%20region%20tenant%2C%20however%20I%20still%20had%20the%20same%20issue.%20I%20thought%20there%20might%20be%20some%20things%20internal%20to%20Microsoft%20still%20pointing%20over%20to%20Australia%2C%20so%20I%20set%20up%20a%20new%20test%20tenant%20in%20the%20US%20region%2C%20however%20the%20same%20issue%20is%20happening%20to%20this%20test%20tenant%20as%20well.%3C%2FP%3E%3CP%3EIt%20appears%20any%20new%20tenant%20is%20having%20this%20issue%2C%20but%20not%20the%20old%20ones.%3C%2FP%3E%3CP%3EHas%20anyone%20else%20experienced%20this%20and%20does%20anyone%20have%20any%20ideas%20or%20know%20if%20something%20is%20going%20on%20with%20Microsoft%20on%20the%20backend%20for%20skype%20consumer%20and%20teams%20operability%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2787305%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdministrator%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ECalling%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMessaging%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2789990%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Consumer%20unable%20to%20message%20Teams%20users%20without%20Teams%20users%20first%20intiating%20contact%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2789990%22%20slang%3D%22en-US%22%3EIn%20the%20Teams%20Admin%20Center%2C%20using%20Users%20%26gt%3B%20External%20Access%2C%20do%20you%20have%20the%20%22Users%20can%20communicate%20with%20Skype%20users%22%20option%20checked%3F%20I'm%20sure%20you%20will%20have%2C%20but%20I%20Don't%20see%20this%20mentioned%20in%20your%20post.%3C%2FLINGO-BODY%3E
New Contributor

I have an issue where Skype consumer messages will not come through to teams users unless the teams user first messages the skype consumer user. In addition, after the teams user messages the skype user, back and forth messaging will work for awhile(6 hours or so), then the skype consumer user will once again not be able to message the teams user unless the teams user once again initiates the conversation. Regardless if the teams user initiates conversation or not, if the skype consumer user tries to call the teams user, it will fail 100% of the time. It rings on the teams user end, but when they answer the call, it still stays at "ringing" and will never connect. 

I have 2 open tickets with Microsoft 365 support currently, they are unable to find a solution to this.

All DNS entries are verified, all settings appear to be correct.

This initially started when I created a new tenant in the Australia region, at first I thought it was isolated to the Australia region because I have set up over 100 tenants, I created test teams users on about 9 of those tenants, and they all worked(these were all in the US region). 

I then migrated data from the Australian tenant over to a new US region tenant, however I still had the same issue. I thought there might be some things internal to Microsoft still pointing over to Australia, so I set up a new test tenant in the US region, however the same issue is happening to this test tenant as well.

It appears any new tenant is having this issue, but not the old ones.

Has anyone else experienced this and does anyone have any ideas or know if something is going on with Microsoft on the backend for skype consumer and teams operability?

 

2 Replies
In the Teams Admin Center, using Users > External Access, do you have the "Users can communicate with Skype users" option checked? I'm sure you will have, but I Don't see this mentioned in your post.
Yes that is set to external, I've also verified in powershell all the settings are correct. Maybe Microsoft making some moves on the backend? If anyone has recently(within the last month) set up a new tenant they could test this with it'd be appreciated.