External Teams-to-Browser Transition Causes Silent Loss of Participant Audio Recording

[jnsmkl]

Title

External Teams-to-Browser Transition Causes Silent Loss of Participant Audio Recording

Summary

When a Microsoft Teams meeting recording is started in the Teams desktop client and the meeting session is subsequently continued in a browser, the recording may silently lose access to the incoming participant audio stream while continuing to capture the local microphone. No warning or error is presented to the user, resulting in incomplete recordings and unusable transcripts.

Impact

This issue can lead to:

• Loss of all participant audio.
• Incomplete meeting recordings.
• Inaccurate or unusable transcripts.
• Delayed discovery of the problem, often after the meeting has concluded.

Because local microphone capture continues to function, the recording appears healthy and provides no indication that participant audio is missing.

Environment

• Microsoft Teams (Desktop Client)
• Browser-based Teams meeting session
• Bluetooth headset used for meeting audio playback
• Built-in microphone used as recording input
• Organization policy configured to prevent external Teams meeting links from opening in the Teams desktop client

Reproduction Steps

1. Open an external Microsoft Teams meeting link.
2. Launch the Teams desktop client.
3. Start recording.
4. Discover that organizational policy prevents the external meeting from opening in the desktop client.
5. Reopen the meeting link in a browser.
6. Continue the meeting in the browser without stopping or restarting the recording.
7. Conduct the meeting normally for an extended period.
8. Review the recording and transcript after the meeting.

Actual Behavior

• Local microphone audio is successfully captured.
• Incoming participant audio is not recorded.
• Transcript generation is incomplete because remote participant speech is missing.
• No warning, alert, or health indicator is presented during the recording.
• The user is unaware that participant audio is not being captured.

Expected Behavior

One of the following should occur:

Option A - Recording Session Migration

When the active meeting session transitions from the Teams desktop client to the browser, the recording pipeline should automatically reattach to the active meeting audio streams.

Option B - Recording Failure Notification

If a required audio source becomes unavailable, Teams should display a prominent warning indicating that incoming participant audio is no longer being recorded.

Example:

Warning: Participant audio stream is not being captured. Only local microphone audio is currently being recorded.

Option C - Recording Health Monitoring

Teams should continuously validate that all expected audio streams contain audio data.

Potential validation signals:

• Incoming participant audio stream activity.
• Audio-level monitoring on subscribed meeting channels.
• Detection of prolonged zero-level audio on expected streams.
• Recording source and active meeting session mismatch detection.

Root Cause Hypothesis

The recording pipeline appears to remain attached to the original Teams desktop client audio session after the user transitions to the browser-based meeting experience. As a result, the recording service continues receiving microphone input but loses access to the active participant audio streams hosted by the browser session.

Additional Context

The issue was not immediately apparent because:

• Audio playback through the Bluetooth headset worked correctly.
• All participants could be heard throughout the meeting.
• No audio device errors were reported.
• No recording health warnings were shown.
• The recording continued running normally for approximately one hour.

Suggested Enhancement

Introduce recording-health diagnostics that monitor actual recorded audio streams rather than only configured input devices. This would allow Teams to detect and surface broken audio-routing scenarios before significant recording data is lost.

Severity

Medium

The meeting itself remains functional, but the resulting recording and transcript may be partially or completely unusable, with no indication to the user until post-meeting review.