Teams Meeting Chat issue

%3CLINGO-SUB%20id%3D%22lingo-sub-1785233%22%20slang%3D%22en-US%22%3ETeams%20Meeting%20Chat%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1785233%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20had%20a%20very%20unusual%20experience%20happen%20today%3A%3C%2FP%3E%3CUL%3E%3CLI%3EA%20user%20created%20a%20Teams%20meeting%20in%20Outlook.%20The%20meeting%20was%20not%20scheduled%20for%20a%20particular%20Team%20or%20Teams%20channel.%20There%20were%2014%20invitees.%3C%2FLI%3E%3CLI%3EPrior%20to%20the%20meeting%20start%2C%20she%20opened%20the%20meeting%20from%20the%20calendar%20icon%20in%20the%20Teams%20app%20menu%20bar.%3C%2FLI%3E%3CLI%3EShe%20clicked%20on%20Chat%20and%20typed%20in%20a%20message.%3C%2FLI%3E%3CLI%3EShe%20suddenly%20began%20getting%20replies%20and%20likes%20to%20her%20chat%20message%20in%20the%20meeting%20from%20people%20who%20were%20not%20included%20in%20the%20invitees%20on%20the%20original%20meeting%20request.%20In%20total%2C%2028%20non-invited%20people%20saw%20her%20chat.%20None%20of%20them%20got%20the%20original%20meeting%20request%3B%20it%20wasn't%20on%20any%20of%20their%20calendars.%3C%2FLI%3E%3C%2FUL%3E%3CP%3EThis%20is%20her%20normal%20behavior%20for%20creating%20meetings%20that%20are%20not%20specific%20to%20a%20Team%20or%20Teams%2FChannel.%20How%20could%20this%20have%20happened%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1785233%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1786859%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Meeting%20Chat%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1786859%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F341327%22%20target%3D%22_blank%22%3E%40LBumgarner%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHi%2C%20unless%20the%20meeting%20link%20has%20been%20shared%20with%20these%20extra%20people%2C%20this%20should%20be%20impossible.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI'd%20recommend%20opening%20a%20support%20ticket%20with%20Microsoft%20to%20see%20if%20they%20can%20offer%20any%20guidance%20on%20this.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1788036%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Meeting%20Chat%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1788036%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F616707%22%20target%3D%22_blank%22%3E%40PeterRising%3C%2FA%3E%26nbsp%3BThank%20you%20and%20I%20agree%20this%20should%20not%20have%20happened.%20None%20of%20the%20non-invited%20guests%20received%20the%20meeting%20request.%20The%20meeting%20chat%20just%20appeared%20in%20their%20chat%20list.%20One%20person%20attempted%20to%20join%20the%20meeting%2C%20but%20was%20not%20allowed%20to.%20Another%20person%20sent%20me%20a%20screenshot%20that%20had%20a%20message%20that%20she%20couldn't%20send%20a%20message%20because%20she%20was%20not%20a%20member%20of%20the%20chat.%20Very%20strange.%20I%20will%20take%20your%20advice%20and%20contact%20Microsoft%20support.%20I%20just%20wanted%20to%20try%20to%20troubleshoot%20it%20before%20doing%20so.%26nbsp%3B%20Thank%20you!%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

We had a very unusual experience happen today:

  • A user created a Teams meeting in Outlook. The meeting was not scheduled for a particular Team or Teams channel. There were 14 invitees.
  • Prior to the meeting start, she opened the meeting from the calendar icon in the Teams app menu bar.
  • She clicked on Chat and typed in a message.
  • She suddenly began getting replies and likes to her chat message in the meeting from people who were not included in the invitees on the original meeting request. In total, 28 non-invited people saw her chat. None of them got the original meeting request; it wasn't on any of their calendars.

This is her normal behavior for creating meetings that are not specific to a Team or Teams/Channel. How could this have happened?

 

Thank you.

 

5 Replies
Highlighted

@LBumgarner 

 

Hi, unless the meeting link has been shared with these extra people, this should be impossible.

 

I'd recommend opening a support ticket with Microsoft to see if they can offer any guidance on this.

Highlighted

@PeterRising Thank you and I agree this should not have happened. None of the non-invited guests received the meeting request. The meeting chat just appeared in their chat list. One person attempted to join the meeting, but was not allowed to. Another person sent me a screenshot that had a message that she couldn't send a message because she was not a member of the chat. Very strange. I will take your advice and contact Microsoft support. I just wanted to try to troubleshoot it before doing so.  Thank you!

Highlighted

@LBumgarner Hello, by any chance this was a recurring meeting invite being reused with another set of users? That would explain the behavior at least, meaning why the non-invited users had the meeting chat activated. Other than that I have to agree with what @PeterRising said. As for the meeting and lobby behavior they are controlled by either the individual meetings options or assigned meeting/messaging policies and the guest settings as well.

Highlighted

@bec064  Thank you for your input. This was not a recurring meeting invite that was re-used. Some of the users who received the meeting chat would not normally be part of meetings. For example, one of the users who that showed up in the list was our IT service account. It has a M365 account, but would never be invited to a meeting. Others were users who don't normally participate in meetings, other than their own departments or committees, but there's not a common denominator that I can find.

Highlighted

@LBumgarner Hello, ok good to know. If you're confident the meeting link hasn't been made available to these users then a support ticket should be opened, as previously mentioned.