Microsoft Teams

Where Microsoft Teams keeps its logs

Microsoft Teams logs to %LOCALAPPDATA%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\Logs\ on Windows. 1 other Windows log location is recorded below.

Microsoft Teams logs to ~/Library/Group Containers/UBF8T346G9.com.microsoft.teams/Library/Application Support/Microsoft/Teams/Logs/ on macOS. 1 other macOS log location is recorded below.

Microsoft Teams logs to ~/.config/Microsoft/Microsoft Teams/logs.txt on Linux.

Paths are printed exactly as Microsoft Teams writes them. Environment variables like %LOCALAPPDATA% and $XDG_STATE_HOME are never expanded, so a path can be pasted straight into a shell. Where a path differs between installer types or shipping flavours, each one is racked as its own card below - why that happens.

Finding your way around Windows, macOS and Linux.

How to turn on debug logging for Microsoft Teams

1. No switch is needed on a normal desktop: current Teams records media logs all the time.
2. VDI: open Teams Privacy settings and turn on Extended Logging.
3. VDI: reproduce the issue, then collect the logs.

How to collect Microsoft Teams logs

1. Windows: right-click the Teams icon in the system tray and choose Collect support files, or press Ctrl+Alt+Shift+1.
2. macOS: choose Help > Collect support files, or press Option+Command+Shift+1.
3. Wait until the Downloading web logs banner goes away.
4. Open your Downloads folder and zip the MS Teams Support Log Files folder.
5. Attach that zip and the Prod-Weblogs zip, which is already compressed. Other clouds use Life-Weblogs, GCCH-Weblogs or DOD-Weblogs.
6. Logs from every signed-in account are included, and times are in UTC.
7. Media and signaling logs are encrypted and only Microsoft Support can read them. Web logs are plain text.