Forum Discussion
"When the meeting starts, we’ll let people know" Bug
I do know though that there is continuous work in progress when it comes to the "meeting join experience" so I hope that will sort this out.
I am not sure I track this chain of events. To clarify:
* I am accessing the link via webmail (Exchange 2016). This webmail is not the same one as my Teams org account. There is no Outlook installed on this computer, so there is no way to match up the accounts.
* If I sign out of MS Teams as an app, I will be totally signed out. There is no "other profile" that matches the email invitation.
Does this clarify things a bit?
On the browser (even when signed in to the same Org account!), I reach the meeting waiting room as expected. However, the Teams Windows app simply refuses to admit that a meeting even exists. It also does not inform anyone that I am in the waiting room. From my experience, I have not yet found a workaround. Also from my experience, this behavior is not fully stable (e.g., sometimes you can connect to a meeting properly, sometimes it puts you in this nether-world).
Are you saying there *is* a workaround to get the Teams app to work consistently? (again, there is no Outlook installed on this machine, and the email which recieves the meeting invite is *not* the one associated with the Teams org, so I will always be a guest).
Maybe put another way, is there any way that the Teams app will just let a guest account connect to a meeting? (no login) Which I assume is why the browser works (both in a regular window and in incognito mode).
- Feb 11, 2022It sounds odd with the no existing meeting part. You should at least end up in the lobby. I would probably reach out to the official support, if they cannot see anything backed perhaps send them some logs for analysis. They will provide guidance for that and if you're not an administrator reach out to that person for assistance with a support ticket creation.