Overview
Choppy or dropping Teams calls are commonly caused by unstable Wi-Fi, packet loss, congestion, poor bandwidth, VPN routing, device resource pressure, or audio/video device problems.
Why this happens
Teams audio and video are real-time traffic. They are sensitive to latency, jitter, packet loss, wireless interference, and overloaded devices.
Before you begin
- Record whether audio, video, or both are affected.
- Note whether the issue happens on every call.
- Confirm whether others on the same network are affected.
- Do not disable security software or QoS policy.
Click-by-click troubleshooting
Step 1: Check Teams device settings
Action: Open Teams > Settings > Devices and confirm the intended microphone, speaker, and camera.
Why this matters: Wrong or failing peripherals can mimic network-quality problems.
What to look for: Look for missing devices, very low input level, or unexpected USB/Bluetooth selections.
Expected result: Teams should use the intended working devices.
Step 2: Check Wi-Fi signal and connection
Action: Open Settings > Network & internet > Wi-Fi and review the current network. Move closer to the access point if practical.
Why this matters: Weak or unstable Wi-Fi causes packet loss and latency spikes.
What to look for: Look for low signal strength, frequent reconnects, or connection to an unintended network.
Expected result: The device should have a stable connection to the intended network.
Step 3: Reduce competing traffic temporarily
Action: Pause large cloud uploads, software downloads, or nonessential streaming during a test call.
Why this matters: Heavy network usage can consume available upstream or downstream bandwidth.
What to look for: Note whether call quality improves when large transfers stop.
Expected result: Improvement suggests local bandwidth contention.
Step 4: Check device resource usage
Action: Press Ctrl+Shift+Esc and review Task Manager > Processes for CPU, Memory, and Disk pressure.
Why this matters: A heavily loaded device can drop audio/video frames even when the network is healthy.
What to look for: Look for sustained CPU near 100 percent or memory exhaustion.
Expected result: The device should have enough available resources for a Teams call.
Step 5: Compare VPN versus approved direct path
Action: Follow organizational policy for Teams traffic. If Teams is not required to traverse VPN, compare call quality using the approved normal connection path.
Why this matters: VPN routing can add latency or congestion when real-time media is unnecessarily tunneled.
What to look for: Note whether quality changes with the organization's approved routing model.
Expected result: The test should identify whether the VPN path contributes to the issue.
Step 6: Compare another network
Action: If policy allows, test a short call using a trusted wired connection or mobile hotspot.
Why this matters: This isolates the local Wi-Fi or ISP from the laptop and Teams client.
What to look for: Compare drops, audio breakup, and video freezing.
Expected result: Better quality elsewhere points to the original network path.
What to look for
- Weak Wi-Fi: wireless problem.
- High CPU: device-performance issue.
- Improves without large transfers: bandwidth contention.
- Improves on alternate network: local Wi-Fi or ISP problem.
When to stop
When to contact IT
Contact J3 Systems Group if Teams quality remains poor on multiple networks, multiple users are affected, the device shows healthy resources, or the issue appears tied to VPN or office network design. Include article code KB-15.004 and the test results.
Need help with this issue?
J3 Systems Group supports small businesses and nonprofits with Microsoft 365, Google Workspace, cybersecurity, devices, documentation, and day-to-day IT operations.
Contact J3 Systems GroupAuthoritative references
Vendor interfaces, licensing, and security guidance can change. Verify current platform behavior against the primary documentation below before making high-impact production changes.