Forum Discussion
When the meeting starts, we’ll let people know
- Oct 22, 2021
For starters, this is not a bug. Rather it's the Teams app that doesn't handle multi-accounts / multi-tenants particular well at this point. In general you should be signed in to Teams desktop and Outlook desktop with the same account to avoid issues. When clicking a meeting link and being signed in to Teams, you need to be signed in with the associated account/org. to which the invite was sent (or enter as anonymous guest not signed in). If not Teams is going to use the signed in account/org. credentials trying to access a meeting in which they weren't invited to, hence being stuck in the lobby as not being recognized (that is if not "everyone" is allowed).
So this is a combination of using the Lobby options as an organizer and which tenant you're currently signed in to.
Using InPrivate / Incognito browser sessions is an alternative if having issues with the app.
Choose who can bypass the lobby
Change participant settings for a Teams meeting (microsoft.com)
For a deep dive Meeting Lobby Behavior in Microsoft Teams : Jeff Schertz's Blog
When a Microsoft Teams meeting is organized by person in Company A with somebody in Company B, the organizer sometimes receives the following message. "When the meeting starts, we'll let people know you're waiting".
Neither the organizer or the participant can enter the meeting. However, this does not occur on every occasion indicating that this is bug rather than an admin setting.
A workaround is for the person in Company B to set up the meeting inviting the person from Company A. However, this is not ideal since you don't know which meetings this bug will effect.
When will Microsoft fix this issue?
PS this issue never occurs with Zoom (or other competitor products), reflecting the superior market share enjoyed by Zoom!
- Nikolini91Sep 30, 2021Copper Contributor
Same issue here. The whole team can't work properly with clients accounts because of it.
The outlook is synched with both email addresses but we can only use one Teams account without an issue. Usually the one we are logged in on the Teams app.
I'm guessing allowing additional clients accounts on Teams would solve the issue.
When will Microsoft fix it?
- Sarah_G210Oct 04, 2021Copper ContributorThis is major problem with Teams and it is driving me crazy with wasted time and embarrassing inefficiency. There is no apparent cause or user attribution so it's impossible to fix and I end up using zoom which is far more reliable. Sort this out Microsoft it is pathetic.
- Sarah_G210Oct 25, 2021Copper Contributor
Simon_Ogden it's madness isn't it ?! Makes me angry that MS can't be bothered to sort it out they are so arrogant. And I agree Zoom far more reliable.
- Dec 14, 2021Hi there, instead of this complaining. Give us your exact scenario when this is happening, step-by-step and walk us through and I will assist. Who's inviting who, what account is signed into Teams, which account was the invite sent to, which meeting lobby setting is used and so on..
It's not a bug, and it's not difficult when you know what you are doing.
In general, sign out manually from the top right corner in Teams and back in with the account which you want to use. Preferably the same account as you use with your Outlook client. Then either schedule your meeting in your calendar or enter an already scheduled meeting in your calendar.- Sarah_G210Dec 28, 2021Copper Contributor
Gosh that's an arrogant and dismissive response.
I'm not stupid and I use Teams and many other forms of digital communication regularly with no difficulties whatsoever. This issue arises intermitently and with no apparent correlation between each instance. It's also not consistent between users. Which is why I'm assuming it's some kind of bug. It never happens with Zoom.
I've obviously looked for answers myself before resorting to using this forum which to date has never been helpful in answering my issues. Having drawn a blank using my own (obviously limited) intelligence I thought I'd request support. More than happy to be proved wrong (or stupid) as long as it gets fixed.
- Kendrick1280Dec 14, 2021Copper Contributor