Teams: Microsoft is finally working on performance improvements

Microsoft says it has significantly improved the performance of its Teams communications platform. In the past few weeks, several optimizations have been rolled out that make teams faster. However, the high memory consumption remains.

Lags are designed to shrink

As the company announced the delay when switching between chats has been reduced by around 20 percent. This should allow users to access conversations more quickly, especially on computers with only 8 gigabytes of RAM or with slow network connections. Microsoft has also fixed errors that caused Teams to temporarily stop responding to input or get stuck while scrolling. This problem mainly affected users on MacOS.

Microsoft had already introduced extensive changes to the technical architecture of Teams at the end of 2025. A combination of web and native components made it possible to accelerate the display of video content. Internal measurements showed a ten percent reduction in loading time for videos in meetings, while frozen video images fell by 36 percent. This is how the new AI agents work in Microsoft Teams

Despite these improvements, Microsoft is sticking with the controversial WebView2 technology on which Teams is based. There are no plans to switch to a fully native application for Windows or MacOS. Microsoft cites a uniform technical basis across different platforms as well as a faster introduction of new functions as justification. The common code base also makes development and troubleshooting easier.

RAM usage remains high

At the same time, the group continues to work on optimizing the WebView2 integration. According to the company’s own information, this made it possible, among other things, to significantly reduce memory usage when idle and speed up chat switching. Another bug, which was attributed to the loading of a dynamic library from WebView2, is now also said to have been fixed. Nevertheless, the resource requirements of teams continue to cause criticism. Even on a test system without active conversations or notifications, the application used almost a gigabyte of RAM.

During ongoing video calls, consumption can even increase to up to two gigabytes. Microsoft admits that the application’s shared infrastructure can lead to performance degradation and therefore plans to move certain calling functions into separate processes in the future.