Microsoft is fundamentally restructuring the Teams client on Windows, separating telephony functions into a dedicated process to improve stability and performance.
Starting in January 2026, the application will offload calling tasks to a new executable, ms-teams_modulehost.exe. Engineers designed this split to isolate resource-heavy voice and video workloads from the main interface.
Separately, the company has halted a controversial login experiment. Plans to allow consumer sign-ins via Apple and Google credentials on Teams Web were paused this week following concerns over enterprise security confusion.
Promo
Architectural Overhaul: The Split Stack
Under the hood, the change involves decoupling the calling stack from the primary application thread. Currently, a single process handles both the user interface and real-time communication tasks, which can lead to performance bottlenecks during heavy usage.
By introducing ms-teams_modulehost.exe, Microsoft intends to prevent UI freezes or high memory consumption in the main app from degrading call quality.
According to the technical notification, this separation is designed to ensure that meeting experiences remain fluid even if the rest of the client is under load.
“We’re improving the performance and startup time of calling features in the Microsoft Teams Desktop Client for Windows. To achieve this, we’re introducing a new child process named ms-teams_modulehost.exe that will handle the calling stack separately from the main application process (ms-teams.exe).”
Microsoft states that the “change optimizes resource usage and enhances meeting experiences.” While specific performance benchmarks were not disclosed, the move aligns with broader efforts to optimize the client.
Rollout for the new architecture is scheduled to begin in early January 2026. Microsoft expects the deployment to reach all commercial tenants, including GCC and DoD environments, by late January.
Administrative Impact & Security Action Items
For system administrators, this update triggers immediate configuration requirements. Because the new module host operates as a distinct executable, it may not inherit existing security permissions automatically.
Endpoint protection software and application control policies must be updated to recognize ms-teams_modulehost.exe. Failure to allowlist the process could result in blocked calls or application crashes, as security tools might flag the unknown executable as suspicious activity.
Network administrators also need to replicate Quality of Service (QoS) policies. Traffic prioritization rules that currently apply to ms-teams.exe must be extended to the new process to guarantee bandwidth for voice and video packets. The official advisory outlines the operational scope:
“A new process (ms-teams_modulehost.exe) will appear in Task Manager under the main Teams process (ms-teams.exe).”
It further clarifies the impact on end users:
“No changes to user workflows or UI; however, admins should ensure endpoint and security software allow this new process.”
Beyond the technical restructuring, the company advises IT teams to inform helpdesk staff about the change. Without prior warning, support personnel might misdiagnose the new background process as malware or unauthorized software during troubleshooting sessions.
Identity Management: The Login Rollback
In a related development, Microsoft has reversed course on a feature intended to simplify access for external users. The company started testing a “Continue with Apple” and “Continue with Google” option for Teams on the web, aiming to reduce friction for guests and personal account holders.
However, the integration raised concerns among enterprise administrators. Allowing consumer login options on corporate sign-in pages risked blurring the lines between personal and organizational identities, potentially leading users to create shadow IT accounts. The original announcement described the intended functionality:
“We’re introducing a new sign-in experience that enhances flexibility and accessibility for a limited number of users on Microsoft Teams for the web. This change introduces new sign-in options—Continue with Apple and Continue with Google—on the sign-in page (teams.microsoft.com or teams.com) for users routed through login.microsoftonline.com/common.”
Following feedback, the feature status was officially changed to “on hold” as of November 24. Microsoft apologized for any inconvenience and stated that they “will communicate via Message center when we are ready to proceed.”