Forum Discussion
Teams Room System (formerly SRSv2) does not recognize externally hosted Teams meeting
MADrouin just joining the conversation here, with the same issue on a Logitech TAP system.
Internal invites can be forwarded, but external invites that are forwarded gives the 3 dots...
Looking forward to hear the finding from lvl2!
Dan Hansen Hi all, Microsoft ended up running a fix in the background in regards to safelinks. We couldn't get a straight answer to what they actually did, but I would suggest to open a ticket with Microsoft and reference the same issue that we had.
I would also reference our ticket # 19036011, hoping they might give someone else a complete answer.
I believe the main challenge on our side was basically just trying to understand their explanation.
Hi, not a single article, but a few that should describe everything I hope:
Set up Safe Links policies in Microsoft Defender for Office 365 - Office 365 | Microsoft Docs
Safe Links - Office 365 | Microsoft Docs
Manage your allowed and blocked URLs in the Tenant Allow/Block List - Office 365 | Microsoft Docs
Hope those help.
Thanks
Mark.
Is there a support document available on web which I can refer Mark Taylor
- I have been in touch with the head of product (partner director) Microsoft Teams Devices at Microsoft, mr. Ilya Bukshteyn. He told me they had pretty extensive code for SfB meetings to follow links and figure them out, but for Teams apparently they only implemented string matching. They are looking at this now. Hopefully a fix will be available pretty soon.
We have experienced the same kind of problems at a customer and found earlier this year that forwarding of meetings are working from Outlook Web Access, but not from Outlook on the computer. The Outlook version at this time was 1908 build 11929.20708. After upgrading to Outlook version 2004 build 12730.20520 the problem was fixed.
The problem has now however reappeared on Outlook version 2008 build 13127.20638. Forwarding of meetings by use of Outlook Web Access is still working Ok. Seems like the problem is related to the Outlook version on the computer.
Detailed walkthrough of the problem is described here:
https://skotheimsvik.blogspot.com/2020/05/teams-room-system-does-not-recognize.htmlI can also confirm this fix has worked.
We added teams.microsoft.com to safelinks ignore rewrite list and adjusted the mailbox settings as recommended in step 3 of this microsoft article: https://docs.microsoft.com/en-us/microsoftteams/rooms/with-office-365
After 30 mins we were able to forward external meeting requests to our Logitech Tap unit (SRS) and the join button was present.
Hi Dan
Thanks for the update, this *worked*!
The critical piece as everyone suspected is the Safe Links.
For reasons I cannot explain, any external meeting request inbound arrives and can be accepted by a user and Teams for the user will process it just fine.
However even with internal safe links disabled, if you forward that meeting to a Teams Room System it wont recognise it as a Teams meeting.
I added the 'teams.microsoft.com' to the external don't rewrite list, re tested and it worked.
Still works for the user, and now works for the Teams Room system as well.
Thanks to everyone for all of your suggestions and help!
Mark.
I just made the following changes here, which seems to have resolved the issue on our Logitech TAP for Teams setup:
- Under Safe Links settings, added teams.microsoft.com URL to not be rewritten
- The Delete Comments under get-Calendarprocessing is $false (has been the whole time)
We will now test more on all our Teams room setups, I'll post back here if we find other things...
Thanks everyone for the feedback and tips.
We already have all these settings in place (and have for a couple of months), still not working for us.
We will have to go with the ticket option, would be nicer if Microsoft just published something definitive about something so core to Teams.
Thanks again
Mark.
