Dec 04

Microsoft Teams – Connectivity & Client logs

The Skype for Business Client had various connections to components:

  • Edge Server for Media Traversal
  • HTTPS for address book download and various other components
  • HTTPS to the Exchange Web Services to get Free Busy etc.
  • SIP/PSOM to the Edge Server for remote connectivity and data conferencing

Microsoft Teams client also has various connections, but no longer connects to the Exchange Web Services (as client). This is all handled in the Team services as part of Office365.

In order to validate client connectivity, you can download or access the logs and this is how to do so:

Web client:

Windows – Press (CTRL + ALT + SHIFT + 1) in the client to download the logs. The Logs will be downloaded to %downloads%\MS Teams Diagnostics Log <timestamp>.txt

MAC – Press (Command + Option + SHIFT + 1) in the client to download the logs. The Logs will be downloaded to Downloads\MS Teams Diagnostics Log <timestamp>.txt

Desktop client:

Windows – The Logs are located here: %appdata%\Microsoft\Teams\logs.txt (as example Guest Access or ADAL login)

MAC –The Logs are located here: ~/Library/Application Support/Microsoft/Teams/logs.txt

Media stack (encrypted, required in case of support):

Windows – The logs are located here: %appdata%\Microsoft\Teams\media-stack\*.*

MAC –The Logs are located here: ~/Library/Application Support/Microsoft/media-stack/*.*

Actual tracing

In Skype for Business we used to use Snooper and an application to trace HTTPS traffic such as Fiddler or Charles Proxy. As the Microsoft Teams client does not use SIP, we no longer require Snooper to view the traces. Personal preference of Fiddler or any other type of HTTPS traffic inspection application will help you out on troubleshooting any issues. If you want to decrypt HTTPS traffic, you will be required to install the Root CA of the application such as Fiddler.

Permanent link to this article: http://www.reijling.nl/?p=1248

Leave a Reply

Your email address will not be published.