04-22-2020 02:15 PM
04-22-2020 02:15 PM
Organizer created a single instance meeting using the Outlook Teams Add-in and sent out the invite to whole company. Total attendees would have been under the 250 limit.
10-15 mins before the meeting, organizer opened the calendar invite & clicked the Join Teams Meeting link in invite as did her fellow presenters starting the meeting a few mins early.
Rest of company either clicked the "Join Online" button from the Outlook meeting reminder or clicked the "Join Teams Meeting" link in the invite and some people ended up in the organizers "working" meeting with presentation, while others ended up in a completely different meeting with no organizer, no presentation. We ended up shooting the sh*t.
But, people in both meetings were in the same chat thread for the meeting and could chat to both groups.
No rhyme/reason of how people joined to what "audio" portion of meeting they joined, but essentially it had the same chat thread, just 2 separate audio portions. Kind of like what is described here: https://techcommunity.microsoft.com/t5/microsoft-teams/issues-join-a-meeting-creates-new-instances-o...
This is using M365 E3 instance. Anyone see anything like this before?
*Edit: After the meeting concluded, the IT team (3 users) and 2 organizers utilized the same invite and tested clicking Join Online or clicking the Join MS Teams link in the invite and every time ended up in same meeting.
05-13-2020 04:45 PM
We had exactly the same issue in a meeting today. There was no doubt that two separate audio/video meetings were spawned, with only one text chat. The only practical solution was for everyone to leave, to delete the calendar entry, and to create a completely new meeting, with a new link, which then worked fine (after about half an hour of struggling).
08-26-2020 11:58 PM
Same problem happened several days ago. 1 meeting request has been send but the moment we where doing the meeting we noticed 2 different groups with invited users. But 1 chat. The links to the meetings where also different.
Has Microsoft looked to this issue?