Microsoft 365 Alert – Service Degradation – Microsoft Teams – Some users may encounter intermittent crashes when using the Microsoft Teams desktop client – RESOLVED

04/08/2023 08:53:00 AM (GMT)

Microsoft Reference : TM664795

Issue Status : RESOLVED

Issue Description : Users may encounter intermittent crashes when using the Microsoft Teams desktop client.

More Info : The mitigation being deployed may not immediately remove existing large files created by the excessive logging issue. For some users this may cause the impact to continue until the local log.txt files are rolled over automatically. It is safe for affected users or admins to navigate to the location %appdata%\Microsoft\Teams\ folder and delete logs.txt or old_logs_XYZ.txt (where XYZ is a numerical timestamp) and perform a manual deletion. This action is only necessary if the file size is still having a negative impact on the user. Eventually the local logs.txt created by the issue will roll over to a smaller size automatically, and the old old_logs_XYZ.txt file will become deleted each time Teams restarts (by design).

Final Update : 09/08/2023 08:42:00 AM – The fix deployment has completed, and Microsoft have confirmed that the issue is now resolved.

Scope of impact : Impact is specific to some users that are utilizing Skype for Business and Microsoft Teams simultaneously on their desktop devices.

Root cause : A recent service change, introduced to address an unrelated issue, contains a code regression that’s causing excessive logging to be generated when users are using Skype for Business and Microsoft Teams simultaneously. The increased logging is causing excessive device disk space and CPU usage consumption, thus resulting in Microsoft Teams client crashes. Additionally, our original fix deployment was misconfigured and didn’t target all affected environments to properly address this problem as originally communicated in TM663429.

Next steps : Microsoft are reviewing their fix deployment processes to ensure all environments are properly targeted in the future. They are also reviewing the offending service change to better understand why impact wasnt detected during testing and validation processes.