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)
When dialing out by clicking a hyperlink on a web page New Teams opens a prompt asking you to confirm that you would like to call the indicated number. The call is placed after clicking the blue Call button and the microphone is automatically muted. I can't seem to find any setting that allows toggling this behavior in New Teams. I also can't unmute the microphone until the call is connected. Here is a screenshot of the Call dialog from a web page:
This is really not ideal and only seems to be happening with the New Teams client. It also does not seem to happen automatically for inbound calls or those placed using the dial pad. Having to unmute for each outbound call (hundreds or thousands daily from our CRM and other systems) is really quite unacceptable. Has anyone else been able to figure out how to handle this?
This change is not mentioned in the What is changing in the new Microsoft Teams or Known issues in the new Microsoft Teams desktop client pages.
For those looking for some relief, there are reports (and works for me as well) of being able to click the Mute icon exactly once while the outbound call is ringing and when connected it will automatically unmute. Through our combined efforts there are also multiple tickets open with Microsoft that give hope that the issue has been identified and will be included in the fixes for R1.5 which is planned to be released around mid-January though may take longer for general availability.
From our support ticket with Microsoft here is the update from Feb 2024 we have from them:
"The issue is fixed till development ring. For next deployment, Product team still evaluating if they can enable the feature in second level for development ring by today (or if they need to wait for a couple of more days). This is under discussion. Given that many are impacted due to this issue, product team is trying a make a separate small change to resolve the issue faster for everyone. But still, this may take February end to get the fix fully deployed. So ETA for general ring will be by end of this February."
In early March 2024, here is the update from the support team:
I can see this case has taken quite a bit longer and we really apologize for this delay. As you aware this is a bug where the product team has already developed a fix, and the fix has been released for TAP customers, but due to some other issues the product team has stopped rollout of this fix for general customers. Also, the product team has not shared any ETA to complete the roll out. We have reached out again to the product team and asked them to share a tentative date for ETA.
Timeline:
Latest Updates:
This is started to be resolved as of the following Teams version:
You have Microsoft Teams version 24004.1307.2669.7070.
You've got the latest version. It was last updated on 2/14/2024.
The client version is 49/24010419130.
With the pause to the rollout, it is confirmed to still be an issue with the following version:
You have Microsoft Teams version 24004.1309.2689.2246.
You've got the latest version. It was last updated on 3/7/2024.
The client version is 49/24020205515.
Final Update (we all hope)
The most recent update as of April 8th seems to have resolved the issue again. While we didn't have to follow the additional steps, I am listing them here in case anyone needs to use them:
You have Microsoft Teams version 24060.2623.2790.8046. You've got the latest version. It was last updated on 4/8/2024.The client version is 49/24022924517.
No Longer Final Update
It would appear that the issue has returned. Clearing the associated APPDATA folder does not resolve the issue and we have reopened our ticket with Microsoft. Reports from this thread indicate it may have started with releases on April 16th, with numerous confirmed cases on April 17th.
You have Microsoft Teams version 24060.2623.2790.8046.
You've got the latest version. It was last updated on 4/17/2024.
The client version is 49/24031414718.
and still present up through this build:
You have Microsoft Teams version 24091.214.2846.1452.
You've got the latest version. It was last updated on 5/14/2024.
The client version is 49/24033101817.
According to our support rep the muting issue should be fixed in versions >=24041122310, which has expected release on the 15th of May.
It does appear to be mostly resolved with in the following build, though dialing a number from an Outlook contact card still has the call muted by default:
You have Microsoft Teams version 24091.214.2846.1452.
You've got the latest version. It was last checked on 5/15/2024.
The client version is 49/24041122315.
Note: The Teams versions won't necessarily increment, though the "last updated" date will often roll forward when checking. We have been on the same "version" for days despite the last updated date always moving forward. Maybe I should file that bug too? You can find lots more version info available here: https://learn.microsoft.com/en-us/officeupdates/teams-app-versioning and here https://github.com/ItzLevvie/MicrosoftTeams-msinternal/
According to the agent working our support ticket the fix was originally scheduled to be released to GA during the week of May 6-10, though it is now scheduled for the 15th.
Muting From Classic Outlook Contact Card
We have opened a new ticket with Microsoft on 2024-05-22 to address the issue of the outbound call initiated from a Contact Card in Classic Outlook (new Outlook uses browser-like behavior). We were initially told there was not a current engineering issue filed but have since received word it is in fact logged already. Not sure what to believe at this point but will continue to provide periodic updates.
The current messaging from our support ticket is that it should be fixed in the GA / Ring 4 rollout scheduled for June 20th. We are asking for build numbers to help confirm but have not received them yet.
Update: It appears that it has been fixed with versions rolling out the week of 15-July-2024. Hopefully there are no other regressions that bring the muting back.
Teams version: 24165.1414.2987.41 Client version: 49/24061318408
Managing sound and video settings during Teams meetings and calls for optimal communication
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.
Yes the SAME issue. No fix to this. I call and start talking and people are like Hello... hello. Before i remember it is muted they hang up. What a PAIN!!!
FIX THIS ISSUE MICROSOFT. STOP releasing DEFECTIVE and INCOMPLETE PRODUCTS.
Hi Philipp12312
The PSTN calling is the problem discussed in this thread, the other behaviour (muting when joining a meeting) is by design. I think if it detects lots of ambient noise from you you'll be muted when you join. But also if you join a meeting which already has a number of individuals (I think it's 5 or 6) the Join screen will have your microphone muted. You can unmute there, before you join, or after you've joined.
Initiating a call there is no 'join screen' so to be on mute before things connect and the recipient answers is infuriating and counter intuitive for many users. That is what this thread is generally for sharing information about.
Thanks Remo and thanks Goyuix for the update! Fingers crossed we see some progress.
But as we're 2-3 months since this Application change was introduced most of our users work around it now rather than switching back to Classic/old.
So basically means we're lost useful functionality (being able to click a phone number from an email/webpage/application and directly calling it).
I just realized that OP @Goyuix updated his post. I highly appreciate that you keep us in the loop and have a suggestion: maybe you could also post a reply when there are major developments, so we all get notified by email.
Thanks,
Remo