In this post I point out where to start troubleshooting and where logs for a Microsoft Teams (windows) client are located by default. Where to start (client) troubleshooting? Well, this depends at which deployment state you are. If you are evaluating Teams in a PoC and all PoC Teams users are affected you might start to check your infrastructure and connectivity before digging deeper into client log analysis.
First of all you should verify and validate that your infrastructure and network connectivity towards Microsoft Cloud Edge is alright. To do this you can verify that all “Office 365 URLs and IP address ranges” are accessible via your network and internet breakout. Ensure that you have configured the required proxy exceptions and firewall rules allowing to connect to Microsoft Cloud services. Common misconfigurations are missing proxy exceptions, firewall rules, firewall (ssl) interception or deep packet inspection mechanisms. Also, an unbenifical and/or legacy network design can cause increased latency, roundtrip times (rtt), jitter, packet loss and lead to bad user experience. So, you should better make your infrastructure and especially your network ready for cloud communication and collaboration (see “Prepare your organization’s network for Microsoft Teams”).
Easy ways to check your network connectivity towards Microsoft Cloud Data Center edges is the “Skype for Business Network Assessment Tool”. It’s a powershell-based tool and helps you to get a snapshot on certain network performance parameters (latency, rtt, packet loss, jitter) as well as a list of blocked or unreachable “Office 365 URLs and IP address ranges”.
I assume that your general (hybrid) cloud configuration with all related topics (AD Connect, DNS, … user license assignment) is fine, also to keep this post short. Otherwise, having infrastructure issues, you’d probably have not only an issue with Teams.
Teams Client Logs on Windows
Where to find client logs for Teams? What’s the Teams client logs path?
Teams desktop logs
- (Windows) Open Teams client
- Press STRG+SHIFT+ALT+1 on the keyboard
- Find logs here: %userprofile%\Downloads
Teams media logs
These logs provide insights regarding media communication flows.
- (Windows) %appdata%\Microsoft\Teams\media-stack
Teams debug logs
Debug logs shows flows regarding login, connection, call and conversations.
- (Windows) right click the Teams app icon in the tray bar
- notepad opens and shows the log data
Conclusion, opinion and summary
In case your infrastructure and connectivity is alright, the client logs may help to dig deeper into the issue analysis. Although, in my experience I rarely need these logs because often it comes down to an infrastructure and connectivity issue towards Microsoft Cloud services either for a single or multiple client endpoints.
- Prepare your organization’s network for Microsoft Teams
- Office 365 URLs and IP address ranges
- Skype for Business Network Assessment Tool
- Use log files in troubleshooting Microsoft Teams