New Teams Mutes Mic When Clicking Hyperlinks

Anonymous
2023-12-04T23:30:25+00:00

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:

  • Issue was first reported on Reddit on Sep 14, 2023
  • Rumblings at work but nobody sure what is going on other than don't use New Client
  • This post on MS Answers forum on Dec 4, 2023
  • Support Partner opens ticket with MS on Dec 11, 2024
  • MS first starts deploying fix around Feb 14, 2024
  • MS pauses rollout around March 7, 2024
  • MS resumes rollout around April 5, 2024
  • Builds suffer from regression and issue returns on April 16, 2024
  • Partially resolved (hyperlinks work, Outlook contact cards no) on May 15, 2024 with client version 24041122315
  • New ticket opened with Microsoft Support on May 22, 2024 to resolve muting issue when dialing from Classic Outlook Contact Contact cards - does not seem to impact New Outlook as it uses technology similar to the web browser
  • Builds released to general availability during the week of 2024-07-15 seems to have addressed final muting issue from Outlook

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:

  • If Teams is still running, right-click the Teams icon in the taskbar, and then select Quit
  • Open the Run dialog box by pressing the Windows logo key + R
  • In the Run dialog box, enter %appdata%\Microsoft\Teams, and then select OK
  • Delete all files and folders in the %appdata%\Microsoft\Teams directory
  • Restart Teams

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

Microsoft Teams | Microsoft Teams for business | Meetings and calls | Audio and video

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.

0 comments

84 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2023-12-20T12:15:41+00:00

    Problem has continued, although with Windows & Teams updates this week the prompting to switch to New Teams is less intrusive, so users who are on it and switch back to Old/Classic are not finding they need to switch daily (are just prompted every 2-3 days to upgrade to New Teams but can refuse/Opt out/say no). So it stays set.

    I've reached out to MS Support and had the following response - basically everyone needs to report this unwanted behaviour through 'Feedback' within the Teams app for the development teams to be more aware of the issue and it to become higher priority to resolve it in future versions.

    It is a change in functionality between 'new' and 'classic' Teams.

    "Thank you so much for your email, and I wanted to express our gratitude for the steps you've taken attempting to fix the Teams issue. After thorough investigation, it appears that the issue may be attributed to the behavior of the software, and we want to extend our sincere apologies for any inconvenience this may have caused. We understand that ongoing improvements are being made, and the transition to Teams New from Classic is a significant part of these developments.

    Our development team is actively working on implementing Teams New, and we want to assure you that every effort is being made to resolve the reported issue. We recognize that these improvements are essential for providing a seamless user experience.

    In the meantime, we recommend that users provide feedback through the Teams application. Microsoft values user input, and this avenue allows our team to submit insights directly to the development team. Users can access this feature by clicking on the (?) help icon and selecting "Give Feedback" within the Teams app.

    For immediate relief, we suggest having users utilize the Classic mode until the issue is fully addressed. We believe this will help mitigate any impact on daily operations.

    To stay updated on progress and additional information, we encourage you to monitor any updates through our community support at https://answers.microsoft.com/en-us. This platform is an excellent resource for the latest news, workarounds, and community discussions.

    Once again, thank you for your continued support and understanding as we navigate through these enhancements. We are confident that the transition to Teams New will ultimately result in a more robust and efficient collaboration platform for our team."

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-12-19T22:27:15+00:00

    We are having the same issue. Very annoying. People hangup before I realize and unmute.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  3. Anonymous
    2023-12-12T08:39:17+00:00

    We're having the same issue. Calls from Dialpad or People within Teams unaffected.

    Seems like a behaviour change between 'old' & 'new' Teams. Any number from a hyperlink (website) or embedded using the 'Call:' function (assigned in 'default application by protocol' in Windows 10 or 11) the call is initiated with the user muted. All current versions.

    Also includes when using the calling button within Microsoft Dynamics 365 Business Central (v14.32)

    60 Users with Hybrid Teams environment

    If a user goes back to Old teams through the settings slider then functionality is restored, yet usually has to change back every time they reboot or shut down (so switch every morning). Occasionally Teams switches back to New during the work day without a reboot, still trying to track the pattern for why that is (user idle, or screen locked?).

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2023-12-05T03:45:37+00:00

    Hello,

    My name is EngineTyme, an Independent Advisor and a Microsoft user like you and I would be glad to help you.

    I understand your concern. It seems that the new Teams app has changed the functionality of having to unmute mic when making outbound calls by clicking hyperlinks while calling from dial pad does not have the same problem.

    This could be a design change in the new app. I would recommend reporting this issue through the Teams app so that Microsoft can investigate and potentially resolve it. You can raise a support to the dedicated teams support who has more access to tools and resources to investigate this scenario by taking logs from you for further investigation.

    Here is the link to reach MS Teams support:

    Phone: https://support.microsoft.com/help/4051701 Chat: https://support.microsoft.com/contactus

    If you would like to suggest features the removal of the feature to the Microsoft design team, then you drop your suggestion on this link: https://feedbackportal.microsoft.com/feedback/forum/ad198462-1c1c-ec11-b6e7-0022481f8472

    Please let me know if you have any questions or concern.

    Best regards, EngineTyme.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments