MacBook Pro microphone silent in Microsoft Teams while Voice Memos records OK after macOS 13.6 privacy update

Environment

MacBook Pro 2021 (M1 Pro), macOS Ventura 13.6 (installed latest minor security update), Microsoft Teams desktop app (Electron-based) v1.5x installed from Microsoft website, Voice Memos and QuickTime record microphone successfully, Teams shows microphone permission granted in System Settings > Privacy & Security.

Symptoms

In Teams calls the local microphone input level indicator stays flat and remote participants hear silence. Teams shows selected input device 'MacBook Pro Microphone' and preferences list the correct device. Voice Memos records and playback contains expected audio. Reinstalling Teams doesn't change behavior.

Observations

Audio MIDI Setup shows an Aggregate Device present for another app; the built-in microphone device sample rate is 44.1 kHz. Console logs during Teams launch show repeated 'kTCCDenied' entries for 'kTCCServiceMicrophone' for a child process 'Electron Helper (Renderer)'. System Settings indicates Teams has Microphone permission. Running Teams from terminal shows environment variables referencing AVFoundation. Using Teams web app in Chrome with microphone access works and remote participants can hear audio.

Already attempted

Tried toggling microphone permission off/on for Teams in System Settings, restarted Teams, rebooted Mac. Deleted Teams app and removed ~/Library/Application Support/Microsoft/Teams then reinstalled. Created a fresh macOS user account and installed Teams — same silent microphone behavior. Removed Aggregate Device in Audio MIDI Setup and set built-in mic as default — voice memo still records but Teams quiet. Tested Teams web in Chrome — works, indicating system-level permission OK.

Question

What steps can isolate whether Electron-based Teams is blocked from microphone capture by macOS privacy enforcement for helper processes, and how can I restore microphone capture in the desktop Teams app without disabling system privacy protections?

Post timeline

COMMUNITY RESPONSES

Verified community troubleshooting

0 replies

No answers yet..

Showing 0 of 0 community responses

AI DIAGNOSTICS

Incident analysis

Updated 1w ago• Trouble ID

Most likely causes

TCC permission record for the Electron renderer/helper process is missing or corrupted after macOS update, causing denial despite UI showing main app allowed. 90%

Teams' helper binaries are unsigned or their code signatures changed (post-update) and macOS treats them as different processes not covered by the original permission grant. 75%

A third-party security/privacy tool or MDM policy is restricting microphone access for specific helper binaries. 30%

Summary

Desktop (Electron) apps use helper processes to access hardware; macOS TCC (Transparency, Consent, and Control) maintains per-binary permissions. Evidence: Voice Memos (native) works and Teams web works, but Electron helper shows kTCCDenied in logs — suggests macOS is blocking the renderer/helper binary even though the main app is allowed. Reinstalling and resetting permissions didn't clear the denial; possible causes include code signing mismatch after update, helper binary path changed, or cached TCC entries corrupted. Aggregate device removal not affecting Teams suggests device config is OK.

Suggested Fixes

Diagnostic step 1

Check exact binary paths mentioned in Console logs (Electron Helper) and verify code signature: codesign -dv --verbose=4 /path/to/helper. If signature invalid, reinstall Teams from official signed installer. Do not run unsigned binaries.

Diagnostic step 2

Reset TCC microphone database for Teams: in Terminal run tccutil reset Microphone com.microsoft.teams (this resets grant and forces re-prompt). Then launch Teams and accept microphone prompt. Note: resetting affects only the specified bundle id and is reversible.

Diagnostic step 3

If Console shows kTCCDenied for helper paths that differ from com.microsoft.teams, file a bug with Microsoft and avoid granting microphone access to unknown binaries. If you have MDM/policy, check MDM-provided plist restricting microphone for specific helper binaries.