10-11-2018 03:49 PM
10-11-2018 03:49 PM
Is there a way to turn off the "lobby" feature when creating a meeting in Teams? I don't want to have to "admit" each person as they join the meeting.
10-11-2018 08:38 PM
10-11-2018 09:21 PM
10-12-2018 10:34 AM
11-29-2018 12:54 PM
Yes, it does not appear to be working. Need to get this fixed soon. Not sure why Microsoft is pushing teams so hard when there is still much to fix and get ready.
01-02-2019 01:34 AM
I have asked for similar settings as we have for Skype for Business, where end users can override the default policy for lobby settings, please vote for it: https://microsoftteams.uservoice.com/forums/555103-public/suggestions/36427201-have-end-users-change...
02-27-2019 07:07 AM
Hey Microsoft, any idea when the "automatically admit users" will work like Skype? When someone is stuck in the lobby because they dialed in before someone started the meeting with a computer everyone is automatically added with Skype. In Teams everyone stays stuck in the lobby even though this setting says to admit "Everyone" automatically.
02-27-2019 09:26 AM
02-27-2019 09:30 AM
Are you dialing in to the meeting over a phone or connecting with the app? When I dial in with a phone I am stuck in the lobby until someone uses the app (mobile, desktop or web) to start the meeting. In Skype when that happens I am then automatically added to the meeting. In Teams I am still in the lobby until the person admits me. If I dial in after the meeting has been started by someone using the app I am still waiting in the lobby until I am admitted. At no time am I automatically added to the meeting without getting stuck in the lobby. My tenant is not on first release, it is on standard release.
02-27-2019 09:32 AM
03-13-2019 10:28 AM
Just to make sure I understand correctly, the policy to allow anonymous join either has to be applied tenant-wide or at the user-level? That's a bummer, this is something that our users would like to allow for some of the meetings they setup but would prefer to disable for some specific meetings that are a little more sensitive.
03-15-2019 02:04 AM
I got the news that this is being worked upon by Microsoft:
Thanks all for voting on this!
@Deleted
03-15-2019 06:32 AM
Thank you. Just to post an update for my comments, the issue that I was referencing was that the setting in the global meeting policy did not appear to be working. We disabled the lobby, understanding it was disabling it globally with no opportunity to override at the individual meeting level, but it was still forcing people to wait in the lobby. We discovered that for some reason a good share of our Teams users were not set to use the global policy but instead were set to an older policy that had the lobby enabled. Once we set all of our users to the global policy it appears to be honoring the setting. Will be glad to see the setting allowed for individual meetings but wanted to clear up my comments about it not working globally.
03-28-2019 08:20 AM
Thanks Joost! This is actually preventing me from scheduling 70+ MSFT interviews in the next three weeks, since I'm currently working off my vendor domain until late summer. Without this ability, the candidate and MSFT interviewer are both considered external users (as they should be), and are shunted into the lobby. With the number of overlapping interviews, I cannot realistically admit everyone from the lobby. We're currently looking at other options, but it's definitely more of a "work-around" than a process update at this point.
03-28-2019 08:43 AM
Currently your only option if you don't want external users to wait in the lobby is to turn it off as @Chris Webb wrote earlier in this thread. Change the Automatically admit people to "Everyone".
03-28-2019 08:51 AM
Acknowledged, and thanks for the response. Unfortunately, I am not one of the O365 admins, and isn't that a "global setting?" Since my vendor supports multiple employers (not just MSFT), having them change it for all their Teams meetings is not realistic. I'm in the process of submitting a request for a custom user policy, but that may fall outside the scope of our contract agreement. As a security fan, I'm not big on "one-off" solutions like that either, since they tend to snowball into an avalanche of problems down the road.
03-28-2019 09:33 AM
It is a Policy so you could have different policies for different users, so you don't have to change it for all users.
03-28-2019 09:54 AM
@Linus CansbyCorrect - however, if my company decides that creating said policy falls outside the scope of our contract agreement, it may not get done (unless Microsoft agrees to amend their contract to include it.... for an additional fee, of course).
It's all the loopholes and stuff that techy folks like us tend to avoid like the plague - and why there's so many lawyers!