1. Home
  2. Web Conferencing

How to generate Microsoft Teams logs for troubleshooting

Microsoft Teams can be used in an individual capacity but it isn’t the sort of app that makes casual conversations easy. There is far too much to set up in terms of the network or group of people you can communicate with. This is why, in most cases, Microsoft Teams is operated under a company-issued license where users are all part of the same network.

As with any app, Microsoft Teams is known to run into problems now and then. These problems may be related to signing in, making calls, sharing files, using the mic or camera in a meeting, and more.

 Microsoft Teams logs for troubleshooting

Microsoft Teams logs

Log files are often an essential tool when troubleshooting complex problems with an app or an OS. Microsoft Teams runs into problems now and then, and there are easy fixes for many of them. That said, for issues that do not resolve, you may ultimately need to generate logs for the app.

1. Generate Microsoft Teams logs – keyboard shortcut

Generating logs for Microsoft Teams logs is easy and an end-user with zero technical knowledge can do it.

  1. Open Microsoft Teams.
  2. Allow the app to run until it encounters an error.
  3. Generate a log file using the shortcut for your OS (see below).
    • Microsoft Teams log for Windows 10: Ctrl + Alt + Shift + 1
    • Microsoft Teams logs for macOS: Option + Command + Shift+1
    • Microsoft Teams logs for Linux: Ctrl + Alt + Shift + 1
  4. The file will be saved to the Downloads folder and you will see a desktop notification for it.

2. Generate Microsoft Teams logs – system tray icon

There is a second method that you can use to generate Microsoft Teams logs. This method works on Windows 10 and may also work on macOS and Linux.

  1. Right-click the Microsoft Teams icon in the system tray (or menu bar).
  2. Select Get logs from the menu.
  3. A new Notepad file will open and populate with log entries. 
  4. Save the file.

Other Microsoft Teams logs

The logs generated using the above method are called Debug logs and are useful for troubleshooting in general. Microsoft Teams maintains one other type of log; Media logs.

On Windows 10, the media logs are saved to one of the following locations:

  • %appdata%\Microsoft\Teams\media-stack\*.blog
  • %appdata%\Microsoft\Teams\skylib\*.blog
  • %appdata%\Microsoft\Teams\media-stack\*.etl

On macOS, the media logs are saved to one of the following locations:

  • ~/Library/Application Support/Microsoft/Teams/media-stack/*.blog
  • ~/Library/Application Support/Microsoft/Teams/skylib/*.blog

On Linux, the media logs are saved to one of the following locations:

  • ~/.config/Microsoft/Microsoft Teams/media-stack/*.blog
  • ~/.config/Microsoft/Microsoft Teams/skylib/*.blog

Conclusion

A log file for Microsoft Teams isn’t going to make much sense to end-users but it can be immensely helpful for anyone trying to help you troubleshoot the app. If the troubleshooting happening remotely, the log file can provide valuable insights into what may be preventing the app from working.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.