Additional features, settings, or issues not covered by specific Microsoft Teams categories
For intermittent Teams desktop disconnects that affect only some computers or network segments, the most likely causes in the provided guidance are network instability, unsupported audio devices, or environment-specific network configuration issues.
Recommended next checks:
- Confirm whether the disconnect is a full network drop or only the Teams session drops.
- If internet access remains available while Teams disconnects, focus on Teams media/network path issues.
- If the whole connection drops, focus on the local wired/Wi-Fi path, dock, adapter, cable, or site network.
- Check connection quality on the affected network loops.
- Microsoft guidance identifies dropped calls and meeting disconnects as likely due to network issues.
- Verify stable internet connectivity and adequate throughput for both sides of the call.
- Review latency, packet loss, and jitter on the affected segments, especially during meetings.
- Validate network infrastructure behavior for Microsoft 365 traffic.
- Check whether firewalls, proxies, or other network devices are blocking or degrading HTTPS or WebSocket connectivity to Microsoft 365 domains.
- If TLS inspection/decryption is enabled, review whether Microsoft 365 traffic is being intercepted, because this can affect service connectivity.
- If VPN is in use, test without it.
- Microsoft provides admin guidance for VPN split tunneling for Microsoft 365 and Teams.
- Check endpoint-specific hardware on affected devices.
- If the issue is limited to certain computers, test with a different network adapter, dock, Ethernet cable, or a direct connection instead of the dock.
- Update dock firmware and network adapter drivers where applicable.
- Verify Teams-certified audio devices.
- Call drops can occur with non-certified devices, including scenarios such as clicking a call notification or resuming from hold.
- Restart Teams and confirm the latest Teams version.
- This is recommended for temporary client-side issues.
- Check for service-side incidents.
- Review Microsoft 365 Service Status to rule out an active service incident.
- Collect logs from an affected device if the issue continues.
- For calls and meetings, Teams diagnostic logs can be collected with Ctrl + Alt + Shift + 1.
- In Azure Virtual Desktop environments, logs are written on the host VM to %userprofile%\Downloads\MSTeams Diagnostics Log DATE_TIME.txt and desktop app logs can also be reviewed under %appdata%\Microsoft\Teams\logs.txt.
- Escalate through the Microsoft 365 admin center if needed.
- If the issue persists after the network and device checks, the Microsoft 365 administrator should contact Microsoft Teams support from the Microsoft 365 admin center for deeper diagnostics.
For network administrators, the most relevant areas to review are:
- VPN split tunneling for Microsoft 365/Teams
- Firewall, proxy, and antivirus handling of Microsoft 365 traffic
- Teams network preparation guidance
- QoS configuration for Teams media traffic
References: