Forum Discussion
Teams meeting policy "allow everyone" not working - anonymous users stuck in lobby
PeterRising Hello mate! Guess what? It's working!
I've done nothing since Friday, so I suppose it was a case of waiting for it to take effect (but it shouldn't take that long!).
Hey mate. Ah that would make the difference. My Gmail is indeed already a guest. I'll give it a try with another Gmail account and see what results I get. Will be tomorrow when I next get the chance now though. I'll let you know though!
OK, now got a brand new test Gmail account, changed my Global Teams Meeting policy as below;
Sent a Teams meeting invite to the Gmail user, and tried to start the meeting as the Gmail guest user.
Despite the meeting settings though, I'm getting this when starting the meeting as the guest user;
Which I believe is what you are getting right? And I agree, this should not happen.
have you checked if the meeting organizer has that same Global Policy assigned to them? I checked and although my organization had it, I (the organizer of the meetings) did no. Also I've read somewhere the setting applies only to new meetings. Thanks for the great input!
My solution worked, now we are able to schedule meetings with anon users starting the meeting. Should you want to create different types of meetings - some having the setting to be joined by anons, some not, then you'd have to have different policies associated with different users.
E.G. According to policy assigned:
User 1 has permission to create meetings where all anons can start the meeting (Custom policy)
User 2 has permission to create meetings where the meeting can only be started by signed in users (guests or otherwise - according to policy setting - it's usually AllOn)
User 3 has permission to create meetings where it is always mandatory that an organization member is present to let people in. (GlobalPolicy normal settings)
- Hello, thanks for the reply. As you can see from the conversation (and the ”best response”) this was solved in June. I just had to wait ~48 hours for the policy to be synchronized. No issue with assigned policies.
PeterRising Hello mate! Really appreciate your input and testing. Thank you for confirming that the setting doesn't work as intended. It seems as if I have to open a ticket with premier support. Unfortunately it's such an exhausting process trying to explain to them (every time) what's going on.
Thanks again for investing your time. I'll update this conversation when I get a proper response. Take care and have a nice weekend!
- I can see why it’s driving you crazy. I want to know how to fix it now too. Let me know how you get on. 😀
PeterRising Hello mate! Guess what? It's working!
I've done nothing since Friday, so I suppose it was a case of waiting for it to take effect (but it shouldn't take that long!).
