Surface Hub 2s with microphone limitations observed during an active Teams meeting

Question

Surface Hub 2s with microphone limitations observed during an active Teams meeting

Rahul Joshi 0

We have recently noticed that within an active team meeting the microphone limitation as to how far the mic can capture the audio of the person speaking.

When a person is sitting on the further end of the room and a remote participant joins the meeting, the audio cuts off during the conversation for the remote participants. This limitation has not been seen for a person sitting closer to the Hub and speaking.

The Hub 2S has been used for various meetings and events and had no issues encountered where a remote participants mentioned that they are not able to hear the conversation from the room properly. The Hub is currently running 22H2 with Teams rooms.

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Answer accepted by question author

1 additional answer

Your answer

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Answer 1

Dear @Rahul Joshi,

Microsoft documents that Surface Hub 2S is certified as an all‑in‑one device for huddle and collaboration spaces, with defined distance expectations. For larger rooms, Microsoft explicitly recommends external, Teams‑certified audio peripherals. If your room has grown in usage (more people, larger layout, different seating), the built‑in microphones may simply be outside their optimal capture range. For larger rooms or meetings where participants sit far from the device:

Add a Teams‑certified external microphone or audio system, such as:

Yamaha YVC series
Sennheiser EXPAND
Other peripherals listed by Microsoft for Surface Hub environments

User's image

For reference: Microsoft Teams certified peripherals for Surface Hub

Your feedback has been duly noted and is highly valued, as it provides with essential insights to continue improving and refining the products and services in the future. In this case, I sincerely recommend you go to Feedback community to vote this similar feedback: (find out similar feedback, if not provide the feedback forum link Ideas · Community). Our product team is in charge of the site, and they constantly check customer reviews and feedback. The higher votes, the more attention the related team will pay on. And a lot of the features are developed and improved based on customer feedback.

Additionally, the best approach in this case is to contact Microsoft Teams Rooms Pro Management for assistance.

The support team over there has higher permission than us to investigate the issue from background, they have more resource and correct escalation channel in handling this kind of issues. This would be a more efficient way in handling the case for you.

Please notice and accept my apologies that as moderators in the community, we are not supported for the product design and have limited resources for the advanced info for Microsoft products. To help you send your feedback and requirement to the related development team, we have redirected you to the correct path.

Again, I truly appreciate your patience and understanding. If you have any further questions or need clarification, please feel free to reach out.

Sorry for the inconvenience again. Your patience and understanding are highly appreciated. I hope you have a great day!

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Rahul Joshi 0 Reputation points

2026-03-12T01:14:06.8066667+00:00

HI Jade, completely agreed for a larger room - external audio peripherals are required. We haven't had these limitations before and recently started experienced such so the initial thought process was something was wrong.
Jade Ng 9,370 Reputation points Microsoft External Staff Moderator

2026-03-12T06:53:16.12+00:00

Dear @Rahul Joshi,

Thank you for the clarification, and I completely understand your concern especially since the Surface Hub 2S had been functioning as expected in similar meetings previously. It’s reasonable to initially suspect that something may be wrong when a change in behavior is observed.Based on Microsoft’s documentation and known design behavior, the built‑in microphones on the Surface Hub 2S are optimized for huddle and collaboration spaces with a defined capture range. Over time, even subtle changes such as room layout adjustments, seating positions, number of participants, or meeting dynamics can make these limitations more noticeable, particularly for participants seated farther from the device.

In scenarios like this, the behavior you’re seeing does not necessarily indicate a fault with the device itself, but rather that the current room usage may now exceed the optimal range of the built‑in microphones. This aligns with Microsoft’s recommendation to use Teams‑certified external audio peripherals for larger rooms or when participants are seated further away, to ensure consistent audio pickup for remote attendees.

To move forward, I recommend:

Adding a Teams‑certified external microphone or audio system to extend the capture range, and

Engaging Microsoft Teams Rooms Pro-Management Support, who have deeper diagnostic access and can validate whether there are any environmental or configuration factors contributing to the change in experience.

I truly appreciate you sharing this observation, as feedback like this is valuable for both support and product teams. Please let me know if you’d like assistance with selecting compatible audio peripherals or with initiating a support case through the appropriate escalation channel.

Thank you again for your understanding and cooperation. I am here to help if you need anything further.

Answer 2

Based on the described symptoms (remote participants intermittently not hearing in-room participants on a Surface Hub 2S), focus on known audio issues and configuration checks for Teams Rooms on Windows/Surface Hub:

Check for the known Surface Hub 2S microphone issue (Windows 24H2) If the Hub 2S is running Windows 24H2 (build 26100.5074 or newer) with Teams Rooms on Windows, there is a known issue where the microphone becomes unusable or effectively stuck at very low volume due to an incompatible Voice Clarity Audio Processing Object (APO).

To fix this on the Hub 2S:

Open Device Manager on the Hub.
Expand Audio Processing Objects.
Right-click Voice Clarity and select Uninstall device.
When prompted, select Attempt to remove the driver for this device.
Reboot the Hub.

This removes the problematic APO so it is not reinstalled via Windows Update and restores normal microphone behavior.

Disable audio enhancements for the Hub’s audio device Audio “enhancement” features in the driver stack can degrade or distort audio over time, including cutting in and out or reducing pickup range.

On the Teams Rooms/Hub device:

On the console, select Settings → Windows Settings and sign in as an administrator.
Open Control Panel → Hardware and Sound → Sound.
On the Playback tab, select the Hub’s speaker device → Properties → Advanced.
In Signal Enhancements, clear Enable audio enhancements → OK.
On the Recording tab, select the Hub’s microphone device → Properties → Advanced.
In Signal Enhancements, clear Enable audio enhancements → OK.
Close Control Panel and restart the device.

This addresses known issues such as echo, low quality, and degraded audio over the course of a call, which can manifest as remote participants intermittently losing audio.

Validate room and meeting configuration If the Hub is used in a coordinated or hybrid setup (for example, with a separate Teams Rooms device in the same room):

Ensure only one device in the room has an active microphone during meetings to avoid echo and aggressive echo-cancellation that can “cut out” distant voices.
Confirm that the Hub’s microphone is the intended active mic and that other in-room devices are muted, as recommended for Coordinated Meetings.

Check physical room conditions Hybrid meeting guidance emphasizes that room acoustics and microphone placement affect how far voices can be picked up:

Reduce background noise and reverberation (carpet, acoustic panels, closing doors, etc.).
Ensure participants at the far end of the room are facing the Hub and speaking clearly.

If, after applying the driver/APO fix and disabling enhancements, the issue persists, collect details (Windows/Teams Rooms build, when the behavior started, and whether it coincides with OS updates) and open a support request so logs from the Hub can be analyzed.

References:

Share via

Surface Hub 2s with microphone limitations observed during an active Teams meeting

1 additional answer

Your answer