Additional meeting and call-related features and issues within Microsoft Teams for business
+1 for this feature. Ridiculous that this isn't a feature. Grade school level of app design.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Can you mute by default whenever you enter a TEAMS meeting? I know this option is available in WebEx, but can't seem to find it in the settings in TEAMS.
Additional meeting and call-related features and issues within Microsoft Teams for business
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
+1 for this feature. Ridiculous that this isn't a feature. Grade school level of app design.
Nicolle,
The option/window is NOT available when the organizer has the "Lobby" functionality turned on nor are you notified you have been admitted to the meeting which I recently learned the hard way :(. There needs to be a default setting as I would much rather be talking on mute for 5 minutes than be heard dropping an expletive regarding an issue unrelated to my current call because I was trying to multi-task.
This! I was just on a call with approximately 15 others only to discover that talking to myself was overheard when someone agreed with what I said.
Users should have the option to set a default rather than having to go in each and every time.
Or waiting in the lobby, looking at something on another screen and dropping an "F" bomb not knowing you had been admitted to the meeting :(. This feature is available on pretty much EVERY conferencing app in existence.
This! I was just on a call with approximately 15 others only to discover that talking to myself was overheard when someone agreed with what I said.
Users should have the option to set a default rather than having to go in each and every time.
Well put MickyB_2021.
I've only used Teams for a short time. When I ran into this issue, I searched for answers and found this thread. I am so disappointed to find there is no solution and the issue was communicated to MS almost 2 years ago. Come on MS!