CONNECTHelp Center

Configure Connect with Microsoft Teams

Configure Microsoft Teams call devices and disable overlapping audio enhancements for Connect translation.

7 min readUpdated September 6, 2026Desktop application

Prepare Microsoft Teams

Prepare the physical and virtual audio paths before changing Microsoft Teams. Connect the wired headset, open Connect, and confirm that the real microphone and speaker work in How I Sound?. Keep a record of the original Microsoft Teams devices so the configuration can be reversed if the test is unsuccessful.

  • Connect: select the physical headset and the correct source and destination languages.
  • Operating system: confirm that Connect Mic and Connect Speaker are present.
  • Microsoft Teams: sign in with an account allowed to change audio settings.
  • Test participant: use a colleague or second device that can confirm both directions.
Configuration path: Settings → Devices → Audio settings. Labels may move between application versions, so look for the active call microphone and speaker when the exact wording differs.

Choose the device pair

The correct speaker depends on which side of the conversation must be translated. Always use Connect Mic for translated outgoing speech, then route incoming speech through Connect Speaker only when Connect needs to process that direction. Keep alerts and ringtones on the physical headset whenever Microsoft Teams provides a separate selector.

Translation directionMicrosoft Teams microphoneMicrosoft Teams speaker
BidirectionalConnect MicConnect Speaker
Outgoing onlyConnect MicPhysical headset
Incoming onlyPhysical headsetConnect Speaker
Never select the Connect virtual devices as the physical microphone and speaker inside Connect itself. They belong in Microsoft Teams and can create silence or a loop when selected on both sides.

Configure Microsoft Teams

Follow the application-specific path below after Connect is ready. Save the device selection, then reopen the relevant settings to confirm that Microsoft Teams did not revert to a system default or a previously connected headset. Complete the sequence before enabling Connect on a live conversation.

  • Open Connect, attach the physical headset, and verify the local preview before launching Teams.
  • Open Microsoft Teams, select the profile or menu control, and choose Settings.
    Microsoft Teams menu with Settings highlighted
    Open Settings from the Teams menu.
  • Select Devices and locate Audio settings.
    Microsoft Teams Settings navigation with Devices highlighted
    Select Devices to open Audio settings.
  • Choose Connect Mic as the microphone. Choose Connect Speaker for bidirectional translation, or the physical headset for outgoing-only translation.
    Microsoft Teams Audio Settings with Connect Speaker and Connect Mic selected
    Choose Connect Mic and the output required by the translation direction.
  • Disable automatically adjusted microphone sensitivity, Noise suppression, High fidelity music mode, and Spatial audio during the baseline test.
    Microsoft Teams Audio Settings with microphone sensitivity, noise suppression, high fidelity music, and spatial audio disabled
    Disable the four competing audio enhancements for the controlled baseline test.
  • Use Make a test call when available, then verify the same devices again inside the real meeting or call.

Control extra processing

A calling platform can apply automatic gain, echo control, noise suppression, or voice enhancement before Connect receives the signal. Begin with the simplest stable path and disable overlapping processing during the baseline test. Re-enable one control only when the real call environment requires it and the recipient confirms a measurable improvement.

  • Turn off automatically adjusted microphone sensitivity during baseline testing.
  • Set Teams Noise suppression off so it does not compete with Connect processing.
  • Keep High fidelity music mode and Spatial audio off for standard translated speech.

Validate the complete call

A saved setting is not proof that the integration works during an active call. Test the physical headset, Connect processing, the Microsoft Teams virtual route, and remote playback as one complete chain. Use the same account, network, VPN, and headset that will be used in production so the result represents the real workflow.

  • Use How I Sound? to confirm a clean physical microphone signal.
  • Join an internal call and verify the active Microsoft Teams devices inside the call surface.
  • Press CONNECT-ON and confirm that the timer starts and live transcription responds.
  • Speak a complete sentence and ask the remote participant what they hear.
  • Test the reverse direction when using bidirectional or incoming-only translation.
  • Reconnect the headset once and confirm that Microsoft Teams keeps or correctly restores the saved route.
The integration is ready when both participants hear only the expected signal, Connect remains active, transcription responds, and a headset reconnect does not leave Microsoft Teams on the wrong device.

Resolve common issues

Use the symptom to identify the layer that needs attention instead of reinstalling every component. Confirm the current device names before changing them, then make one correction and repeat the same test. If the issue continues, record the application version, operating system, selected devices, translation direction, and the exact point where audio stops.

SymptomLikely causeNext check
Connect devices are missingMicrosoft Teams cached its device listOpen Connect first, then restart Microsoft Teams.
The recipient hears natural speechThe physical microphone is activeSelect Connect Mic in the active call settings.
Incoming translation is silentThe call speaker bypasses ConnectSelect Connect Speaker for the incoming path.
Speech is clipped or metallicCompeting audio processingDisable one gain, suppression, or enhancement control and retest.

Frequently asked questions

These answers cover the decisions most likely to change the Microsoft Teams result. Confirm the translation direction before applying a recommendation because outgoing-only and bidirectional calls do not use the same speaker route. Keep the last working configuration available so a failed adjustment can be reversed without disrupting the next call.

Why should Teams Noise suppression be off?

Teams suppression can remove or reshape parts of the signal before Connect completes its own processing. Start with it off, run a test call, and re-enable only one extra control if the actual environment requires it and the result improves.

Which devices should I select in Microsoft Teams?

Select Connect Mic whenever outgoing speech must be translated. Select Connect Speaker when incoming speech must also pass through Connect; otherwise keep the physical headset as the call speaker.

Why are Connect devices missing from Microsoft Teams?

Close Microsoft Teams, confirm that Connect Mic and Connect Speaker appear in the operating system, keep Connect open, and relaunch the desktop application. Applications and browser tabs often keep the device list that existed when they started.

How do I know the Microsoft Teams integration is ready?

Run How I Sound?, place a real test call, press CONNECT-ON, confirm that the timer and transcription respond, and verify what both participants hear. A saved device name alone does not prove the complete route.

Support

Need help? Get in touch with our Support Team for assistance. Include the calling application, operating system, selected microphone and speaker, translation direction, and the exact step that failed. A short description of the expected result and what happened instead helps the team respond more quickly.

The following articles continue this workflow with setup instructions, troubleshooting checks, and feature-specific guidance. Start with the resource that matches your next task, keep the current configuration available for comparison, and validate each change in a short test call before applying it to a live conversation.

Was this article helpful?