Microsoft Teams Meeting — Audio, Video, Camera, and Screen-Share Failures (Device, Driver, Permission, Network)

Indicators

• No audio output or input during a Teams meeting while the same device works correctly in other applications
• One-way audio — remote participants cannot hear the local user, or the local user cannot hear remote participants
• Camera preview shows a black or blank screen in Teams Settings > Devices or during a live meeting
• Screen share appears blank or grey to remote participants despite appearing active on the sharing machine
• Teams reports 'Camera is being used by another application' or fails to enumerate the camera as an available device
• Choppy, robotic, or dropped audio reported by remote participants
• macOS: screen share permission prompt never appears, or share fails silently without content being transmitted
• Meeting joins successfully (chat and roster visible) but media (audio and/or video) never establishes — indicative of blocked media ports

Likely causes

• OS-level privacy permissions blocking Teams access to microphone or camera — Windows: Settings > Privacy > Microphone/Camera toggles; macOS: System Preferences > Security & Privacy > Privacy
• Another application holding an exclusive lock on the audio device or camera (Zoom, Webex, OBS, Skype, virtual camera software) preventing Teams from acquiring the device
• Outdated, corrupt, or incompatible audio or video/camera device drivers — visible as yellow warning icons in Device Manager under 'Cameras' or 'Imaging Devices'
• Firewall or network policy blocking UDP ports 3478–3481 or TCP port 443 outbound to Microsoft Teams media IP ranges, forcing media to fail while signalling (chat, join) succeeds
• Teams client cache corruption causing incorrect device enumeration or media stack initialisation failure — resolved by clearing %appdata%\Microsoft\Teams on Windows
• GPU hardware acceleration conflict causing blank video preview or blank/grey screen share rendering — common after GPU driver updates
• macOS: missing Screen Recording permission in System Preferences > Security & Privacy > Privacy preventing screen share from capturing any content
• VPN or split-tunnel misconfiguration routing Teams media traffic through a congested or policy-blocked VPN path rather than direct internet
• Incorrect default playback or recording device selected in OS sound settings or in Teams Settings > Devices, causing Teams to target a non-functional or absent device

Diagnostic steps

1. Identify the failing modality precisely. In the Teams client, search for 'echo123' and call it, or go to Settings > Devices > Make a test call. Test microphone (speak and listen for loopback), speaker (listen for prompt playback), and camera preview (observe live video). Record exactly which device(s) fail.
   Narrows the problem to a specific media type and device, preventing unnecessary steps on unaffected components and establishing the scope of impact.
2. Check OS-level privacy permissions for the failing modality. Windows: Settings > Privacy > Microphone — confirm 'Allow apps to access your microphone' is ON and the Microsoft Teams toggle is ON; repeat under Privacy > Camera. macOS: System Preferences > Security & Privacy > Privacy > Microphone / Camera / Screen Recording — confirm Microsoft Teams is checked in each relevant section.
   OS privacy controls silently block device access; Teams will show no device or a persistent black camera preview without surfacing an explicit error message if these toggles are disabled.
3. Close all competing conferencing and capture applications — Zoom, Webex, Skype, OBS Studio, any virtual camera or virtual audio software. On Windows, open Task Manager (Ctrl+Shift+Esc) or Process Explorer (Sysinternals) and verify no process retains a handle on the camera or audio device. Relaunch Teams and re-test.
   Exclusive device locks are a leading cause of 'camera unavailable' and audio failures; releasing the lock typically resolves the issue immediately without further steps.
4. Verify default audio device configuration. Windows: right-click the speaker icon in the taskbar > Sounds > Playback tab — confirm the correct speaker is set as both 'Default Device' and 'Default Communications Device'; status must read 'Working properly'. Repeat on the Recording tab for the microphone. Camera: open Device Manager (devmgmt.msc), expand 'Cameras' and 'Imaging Devices', check for yellow warning exclamation marks.
   Misconfigured default devices or driver-level errors are inherited by Teams; a yellow warning icon confirms a driver fault requiring update or rollback.
5. Test Teams from the web client in Microsoft Edge or Google Chrome (teams.microsoft.com) and attempt a test call or meeting with the same user account and the same devices. Note whether the web client succeeds or fails identically.
   If the browser client works but the desktop client does not, the fault is isolated to the desktop client (cache corruption, installation, or driver interaction with the client). If both fail identically, the problem is network, device driver, or OS permission.
6. Verify network reachability for Teams media traffic. Confirm UDP 3478–3481 and TCP 443 are permitted outbound to Microsoft IP ranges. Run the Microsoft Teams Network Assessment Tool to measure connectivity, packet loss, and jitter. If Wireshark is available, capture during a call attempt and filter for UDP traffic to confirm media packets are leaving the machine and receiving responses.
   Blocked media ports produce the characteristic symptom of 'joined the meeting but no audio or video' — signalling (HTTPS/443) succeeds while media (UDP 3478–3481) is silently dropped by an upstream firewall or proxy.
7. Within the Teams desktop client, navigate to Settings > Devices and confirm the correct microphone, speaker, and camera are explicitly selected in each dropdown (not set to 'Same as system'). Click 'Make a test call' and observe whether audio loops back correctly and the camera preview renders video.
   Confirms whether Teams can enumerate and access the selected devices after permissions and locks have been addressed, isolating remaining client-side device selection mismatches.

Resolution path

• 1. PERMISSIONS FIX — Enable OS-level permissions for Teams. Windows: Settings > Privacy > Microphone: set 'Allow apps to access your microphone' ON and Microsoft Teams toggle ON; repeat under Privacy > Camera. macOS: System Preferences > Security & Privacy > Privacy > Microphone, Camera, and Screen Recording — check Microsoft Teams in each. Fully quit and restart Teams after enabling.
• 2. DEVICE CONFLICT — Close all competing applications that may hold the audio or camera device (Zoom, Webex, OBS, Skype, virtual camera/audio drivers). If conflict is persistent, disable virtual audio/camera drivers via Device Manager (right-click > Disable device) if not operationally required, then relaunch Teams.
• 3. DRIVER UPDATE — Open Device Manager (devmgmt.msc). Under 'Cameras'/'Imaging Devices' and 'Sound, video and game controllers', right-click the affected device > Update driver > Search automatically for drivers. Alternatively, download the latest driver directly from the device manufacturer's support site. Reboot after installation.
• 4. TEAMS CLIENT CACHE CLEAR — Quit Teams completely (right-click taskbar icon > Quit). Windows: delete all contents of %appdata%\Microsoft\Teams (preserve the 'meeting-addin' subfolder if present). macOS: delete ~/Library/Application Support/Microsoft/Teams. Relaunch Teams and sign in again.
• 5. HARDWARE ACCELERATION DISABLE — In the Teams desktop client, go to Settings > General and check 'Disable GPU hardware acceleration'. Restart Teams. This resolves blank screen share and black camera preview caused by GPU driver rendering conflicts. Re-enable if it causes display degradation.
• 6. NETWORK/FIREWALL FIX — Work with the network team to permit UDP 3478–3481 and TCP 443 outbound to Microsoft 365/Teams IP ranges (published at aka.ms/o365ips). If the user is on a full-tunnel VPN, configure split tunnelling to exclude Teams media traffic so it reaches Microsoft's network directly rather than traversing the VPN path.
• 7. TEAMS REINSTALL (last resort) — Uninstall Teams: Windows: Settings > Apps > Microsoft Teams > Uninstall. macOS: drag Teams to Trash and delete ~/Library/Application Support/Microsoft/Teams and ~/Library/Preferences/com.microsoft.teams.plist. Download the latest installer from microsoft.com/en-us/microsoft-teams/download-app and reinstall.

Prevention

• Deploy a Teams-aware firewall/proxy policy pre-granting UDP 3478–3481 and TCP 443 outbound to Microsoft 365 IP ranges (aka.ms/o365ips) before Teams rollout, preventing media failures at scale on day one.
• Configure VPN split tunnelling on managed devices to exclude Teams media traffic from the VPN tunnel so audio/video traffic reaches Microsoft's network directly — publish split-tunnel routes aligned to Microsoft's published O365 endpoint categories.
• Use Microsoft Endpoint Manager (Intune) or GPO to pre-grant microphone and camera permissions for the Teams application on managed Windows devices, eliminating permission-prompt failures on first use in locked-down environments.
• Establish a quarterly driver update cadence for audio and video devices tied to the endpoint patch cycle, reducing driver-related Teams media failures after OS updates.
• Monitor the Teams Call Quality Dashboard (CQD) proactively to identify rising audio/video failure rates by subnet, building, or device type before they escalate to widespread user-reported incidents.

Tools

• Teams Settings > Devices > Make a test call — built-in audio/video/camera device test
• Windows Device Manager (devmgmt.msc) — driver status, update, rollback for audio and camera devices
• Windows Sound Settings / macOS Sound Preferences — default playback and recording device configuration
• Task Manager (Ctrl+Shift+Esc) / Sysinternals Process Explorer — identify processes holding exclusive device locks
• Microsoft Teams Network Assessment Tool — validate media UDP port connectivity, packet loss, jitter, and round-trip time
• Wireshark — capture and confirm Teams media UDP packet flow on ports 3478–3481
• Microsoft Support and Recovery Assistant (SaRA) Teams scenario (aka.ms/SaRA-TeamsProblems) — automated diagnostics and repair

References

• Microsoft Teams Troubleshooting Documentation
• Microsoft Teams Network Connectivity Principles and Port Requirements
• Microsoft Support and Recovery Assistant (SaRA) — Teams Scenario