05-23-2019 06:01 AM
05-23-2019 06:01 AM
Guest users we invite to our teams aren't able to use the chat functionality in Teams. Conversations in the channels are working fine but not using the chat (the chat icon is missing). They also appear offline all of the time. For other tenants they say it is working fine and when we switch over to other tenants we have the possibility to chat. In Admin Center -> Guest Access is set to allow chat. Have anyone else experienced this?
05-23-2019 07:58 AM
05-23-2019 09:07 AM
05-23-2019 09:11 AM
05-23-2019 09:17 AM
05-23-2019 09:32 AM
@Par Linderoth- The only thing I've run into is that I, as a guest in other tenants, can't contribute to chat during a meeting, if I haven't switched over to their tenant. Use Case: I get a meeting invite for a meeting in another tenant. When I click on that invite, sometimes (don't know the circumstances), Teams doesn't switch over to that tenant, but instead, joins the meeting while I'm still in my tenant I can contribute voice and video, but not the chat conversation.
05-23-2019 10:13 AM
05-23-2019 10:53 AM
05-28-2019 06:00 PM - edited 05-28-2019 09:44 PM
@Par Linderoth Hi Par.
We are seeing the same issue. It looks like it was working a few weeks ago and now it has stopped.
The chat toggle is also enabled in the admin portal (same as you).
I've checked all the other settings that I can think of but no avail.
On the guest client the chat icon is missing.
05-29-2019 02:26 AM
@peadard Have you reported it to MS? I had a ticket but the technician I was talking to claimed that it was as it should be and at the moment I didn't have the possibility to prove him wrong (through screen shots or similar) so I asked them to archive the ticket while I gathered "proof". I will open a new ticket when I have this and hopefully get a more knowledgeable technician.
05-30-2019 04:34 PM
@Par Linderoth had a support call with MS and they are going to come back to me.
They can see that the chat (guest ) is not working for us even though it is turned on for Guests.
Interestingly the federated chat with the same user is working. (Search for the user Externally)
The guest user gets created as a guest user in Azure Active Directory whereas a federated user does not.
Perhaps it may be something to do with licensing of that guest user in AAD?
05-30-2019 04:41 PM
05-30-2019 05:35 PM
05-30-2019 05:42 PM
@Chris Webb Thanks Chris. Yes they are a member of a Team and can interact as expected with that Team. The only thing they cant do is private chat. I have disabled (guest ) chat and left it for 24 hours and then re-enabled it but it didn't help. That old setting under Services & add-ins for Teams no longer has 'Guest' Listed as an option (or even greyed out) it only has Faculty and Staff and Students. Perhaps something has changed from a licensing standpoint...
05-30-2019 06:32 PM
05-30-2019 09:38 PM
05-30-2019 09:51 PM
@Chris Webb Thanks Chris. I was hoping that was not the case as it would be a bit of a headache for us.
The guest user is set to Teams only and I was hoping this would take override the SFB Only as it has done for all our Teams only POC users.
We set our org default to SFB Only as we found that users in Teams Only mode could not make pstn calls to SFB users in Islands mode. Setting the org Default was the quickest way to move all on Prem users to back to SFB Only.
05-30-2019 10:25 PM
05-31-2019 05:34 AM
@Steven Collierabout two months ago, we had this problem as well. Especially when having meeting with Microsoft. But about month ago I found they have fixed the issue. Also technical folks on Microsoft told there has been some fixes done for this. So it is surprising to see the issue is back for you, but e.g. not for us.
05-31-2019 06:58 AM
05-31-2019 07:40 AM
Please keep us posted, this is affecting our tenant and customers as well. For larger orgs, I have been recommending starting with SfB-only modes, and migrate users to Teams only as pilots progress, but as of now that is basically killing off the guest access feature.
05-31-2019 08:01 AM
05-31-2019 08:15 AM
Ideally we would have SfB only, so that as new users get added they are automatically Skype only, as opposed to changing the user provisioning process which in some orgs is very tightly coupled to HR processes and not readily changeable. Having them default to Teams and then changing them to Skype, especially when sometimes the changes take a day or two to go through, isn't ideal. We've considered the opposite, but typically it hasn't been feasible.
05-31-2019 08:32 AM
05-31-2019 09:00 AM
06-02-2019 02:53 PM
@Chris Webb Thanks Chris. That's good to know and you are right it kind of makes sense. The reason that guest user is showing up in our Admin Centre is I licensed that user to change its mode to Teams Only to override the global default. The rest of the guests do not show up in there.
I will pass the info on to the Ticket in Microsoft.
At the moment its not feasible to change all the users still on Prem to Skype only individually just to fix chat for guest users. As somebody else pointed out its easier if new users get the Org Wide default.
Until Microsoft change this then at least the users can still do federated chat to these external users..
Thanks again for your help.
06-10-2019 03:43 PM
06-13-2019 02:53 PM - edited 06-13-2019 02:53 PM
I assume you guys told them why it's busted? :p Skype Modes and that it works via Teams Only org mode but you can't do that, or just link them to my blog, might help them figure it out.
06-13-2019 11:44 PM