Dec 07 2019 04:44 AM
We're facing a quite annoying problem with Teams meetings that causes all participants that were invited - irrespective of their response (unknown, decline, tentative) - to be brought into the meeting chat when the organiser begins the meeting and types in the chat box. We're getting a lot of users being confused as to how they ended up in a meeting chat and getting annoyed about chat notifications. Imagine how bad this is when you schedule a meeting for 'all' staff.
Steps:
1 - Schedule meeting "Test meeting" in outlook or teams and select multiple participants - either through a distribution group or one by one
2 - Have one of the requested participants 'Decline' the invite
3 - Begin the meeting as the organiser
4 - Write 'Hi folks' in the meeting chat
5 - The person that declined the invite then get's a notification for 'Hi folks' for the meeting chat of "Test meeting"
They then need to leave the meeting or mute it.
Has anyone else had this and got any fixes or workarounds? Currently for large meetings, we're copying a link from another meeting and pasting it in the the invite in outlook so neither Teams or Outlook realises that it's a Teams meeting.
May 20 2021 02:12 PM
Jun 24 2021 07:17 AM
Does anyone know if this is still on the roadmap? The previously linked Roadmap number doesn't seem to there any more?
Thank you
Jul 08 2021 07:14 AM
@MAlpha I sure hope it is..
We are still seeing this issue at least.
Jul 08 2021 07:17 AM
I've discovered the "Webinar" feature of meetings where people have to actively sign up to the meeting which arrives at a similar conclusion but still has it's drawbacks (chat only works in meeting, and only if you look for it...unless I'm doing something wrong)
Jul 08 2021 07:22 AM
Jul 08 2021 08:01 AM
@Andreas_F Ideally we should not be doing workarounds, instead Microsoft should fix this behaviour, how difficult could that be?
Jul 08 2021 08:18 AM
@dannygm - Ideally there are three options: 1) Attending, 2) Not attending but I'd like to read the chat later, 3) Not going, leave me alone, I have too much work to do, Yes I am being anti-social.
Seriously, option 2 should be an "Opt-In". By default, if I am attending I should get the chat. If I decline the meeting, I do not get any of the notices about the meeting, or the attendant meeting features.
I work with a part of the company in Europe. My phone goes crazy at 4am because someone set up a meeting badly. DIng...Ding!!... Ding-ding!... di-ding-din-ding-ding! (Dings coming in so fast the last one doesn't finish...)
Jul 08 2021 08:26 AM
Oct 21 2021 06:29 AM
@dannygm This is still happening, late October 2021. I declined a meeting, which was a repeat of a previous meeting I did attend, and I am getting notice of every post on their chat. I never joined the meeting, have no option to 'leave' the meeting and it is showing as muted, but I still get the buzzing. I made the mistake of asking to be removed from the chat, which only served to make me get EVERY post notification. This is not tenable.
Oct 21 2021 06:51 AM
Nov 03 2021 07:30 PM
Extremely frustrating that Microsoft don't seem to be looking at this one! We do a lot of "Everyone" invites for brown bag sessions or mandatory training where you select one of 4 sessions to join.
Would love to be able to not have to Leave and hide the chat for the sessions I decline!
Nov 10 2021 04:23 PM
@vijayjois I noticed that people who are invited to multiple team sessions and who accept, decline or not accept, still get notification 'ping' sounds when those attending the session engage on chat. This is quite annoying to those who did not even accept, or decline the invite issued, or accepted the first session, and did not accept the other invite sessions offered. It seems if you sent an invite, you get all the chat sounds/notification, which seems illogical to me. How can I fix this so that those invited, who did not accept or decline a teams meeting does not constantly hear or see the chat notifications. Thank-you Tracey
Nov 30 2021 12:12 AM - edited Nov 30 2021 12:16 AM
Almost December 2021 and this problem still persists... this should not be that hard to fix, it's completely counter-intuitive that the issue exists in the first place
Nov 30 2021 12:14 AM
@Zaldenski I know right!
Dec 09 2021 11:15 AM - edited Dec 09 2021 11:16 AM
It's 2021 and I'm still having this issue. And I don't want to mute it, if I decline, I don't want anything to do with it. Is that an option?
Dec 09 2021 12:06 PM
Jan 24 2022 12:55 AM
Mar 21 2022 08:30 AM
Is this bug still not acknowledged by Microsoft?
May 06 2022 08:19 AM
Jun 09 2022 01:54 AM