FULL AI ANALYSIS

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

Generated Oct 3, 2026, 12:35:03 AM

Analysis 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.

Possible 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%

Audio device sample rate mismatch or aggregate device conflict causes Electron to select an unusable audio unit (less likely given logs).

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.

Diagnostic step 4

As a temporary safe workaround, use Teams web in a secure browser or the native Voice app for calls while investigating. If code signatures appear valid but problem persists, collect Console logs and codesign output and escalate to Microsoft support and Apple if TCC appears corrupted. Do not disable System Integrity Protection or global privacy features; instead collect evidence for vendor escalation.

Contact • Help • API Docs • Careers • Terms • Privacy • Cookies • Ads