This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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.
Just to add my voice here, this feature is important to me as well, and would have saved me from annoying my teammates on several occasions. Having the option to change a single meeting's setting is not sufficient.
I agree this functionality is important.
Heather,
Just to clarify, this is not intended behavior...its a bug or issue with Teams. The end user is auto-muted by Teams when joining any call regardless of group size or 1 on 1 calls.
Microsoft Admins, can you look into this issue and comment on this thread?
Actually, it does depend on how many people are on a bridge call when you join that decides on muting or not. I think 4 is the limit. It tells you in a popup when you are auto muted.Direct calls are not auto muted. There is not an option to auto mute by default which I think was the reason for this post.
This thread has been open for nearly 2 years with 6 pages of responses on a single posting....and that is not including the countless people who have found this issue, read the thread, and left when they realized there was no action to take. To date there are currently 43,388 views of this single request.
While I appreciate sharing the link, I don't see how this has 1) not already been requested countless times or 2) how providing feedback in that link is going to change anything with MS response to this basic function.
This very much feels like flipping the responsibility on end users saying that it is our fault for this basic feature not being delivered because we did not give feedback in "the right way".