check before: 2026-01-01
Product:
Teams, Windows
Platform:
Online, US Instances, Windows Desktop, World tenant
Status:
Change type:
Admin impact, Feature update, Updated message, User impact
Links:
Details:
Summary:
Microsoft Teams Desktop Client for Windows will introduce a new process, ms-teams_modulehost.exe, to handle calling features separately, improving performance and startup time. Rollout begins January 2026. Admins should allowlist the new process in security software and inform helpdesk staff; no user workflow changes expected.
Details:
Updated November 26, 2025: We have updated the content below to provide additional information. Thank you for your feedback.
[Introduction]
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). This change optimizes resource usage and enhances meeting experiences.
[When this will happen:]
Worldwide, GCC, GCC High, and DoD: Rollout will begin early January 2026 and complete by late January 2026.
Note: Timelines may shift due to year-end feature flag rollout freeze.
Change Category:
XXXXXXX ... free basic plan only
Scope:
XXXXXXX ... free basic plan only
Release Phase:
Created:
2025-11-25
updated:
2025-11-27
Task Type
XXXXXXX ... free basic plan only
Docu to Check
XXXXXXX ... free basic plan only
MS How does it affect me
XXXXXXX ... free basic plan only
MS Preperations
XXXXXXX ... free basic plan only
MS Urgency
XXXXXXX ... free basic plan only
MS workload name
XXXXXXX ... free basic plan only
summary for non-techies**
XXXXXXX ... free basic plan only
Direct effects for Operations**
Performance Issues
If the new process is not allowlisted in security software, it may be blocked, leading to degraded performance or failure of calling features in Teams.
- roles: IT Admin, Helpdesk Staff
- references: https://learn.microsoft.com/microsoftteams/qos-in-teams
User Confusion
Helpdesk staff may be unprepared for user inquiries regarding the new process, leading to increased support tickets and user frustration.
- roles: Helpdesk Staff, End Users
- references: https://learn.microsoft.com/microsoftteams/qos-in-teams
Documentation Gaps
Internal documentation may become outdated if not updated to reflect the new process, causing confusion among IT staff and users.
- roles: IT Admin, Helpdesk Staff
- references: https://learn.microsoft.com/microsoftteams/qos-in-teams
Quality of Service (QoS) Misconfiguration
Failure to apply the same QoS settings to the new process may result in poor call quality and user experience during Teams meetings.
- roles: IT Admin, End Users
- references: https://learn.microsoft.com/microsoftteams/qos-in-teams
Increased Support Load
Without proper communication and preparation, the helpdesk may experience a surge in support requests related to the new process and its functionality.
- roles: Helpdesk Staff, IT Admin
- references: https://learn.microsoft.com/microsoftteams/qos-in-teams
Configutation Options**
XXXXXXX ... paid membership only
Opportunities**
Enhanced Performance Monitoring
With the introduction of ms-teams_modulehost.exe, there is an opportunity to implement enhanced performance monitoring tools specifically for this process. This can help identify performance bottlenecks and improve user experience during calls.
- next-steps: Research and select a performance monitoring tool that integrates with Windows processes. Schedule a pilot program to test the monitoring on a small group of users before full deployment.
- roles: IT Administrators, Helpdesk Staff, Network Engineers
- references: https://www.techradar.com/news/best-performance-monitoring-tools
Training and Documentation Updates
Updating internal documentation and providing training sessions for helpdesk staff on the new process will reduce troubleshooting time and improve response efficiency when users encounter issues related to Teams calls.
- next-steps: Create training materials that cover the new process and its implications. Schedule training sessions and update the internal knowledge base with the new documentation.
- roles: Helpdesk Staff, IT Administrators, Training Coordinators
- references: https://www.cio.com/article/243648/it-training-10-best-practices-for-it-training.html
Quality of Service (QoS) Optimization
Ensuring that the same QoS settings are applied to ms-teams_modulehost.exe as those applied to ms-teams.exe presents an opportunity to optimize network performance for Teams calls, potentially reducing latency and improving call quality.
- next-steps: Review current QoS settings and develop a plan to implement them for the new process. Collaborate with network engineers to ensure proper configuration and testing.
- roles: Network Engineers, IT Administrators, Operations Managers
- references: https://learn.microsoft.com/microsoftteams/qos-in-teams
Potentional Risks**
XXXXXXX ... paid membership only
IT Security**
XXXXXXX ... paid membership only
explanation for non-techies**
XXXXXXX ... free basic plan only
** AI generated content. This information must be reviewed before use.
a free basic plan is required to see more details. Sign up here
A cloudsocut.one plan is required to see all the changed details. If you are already a customer, choose login.
If you are new to cloudscout.one please choose a plan.
change history
| Date | Property | old | new |
| 2025-11-27 | MC Messages | Updated November 25, 2025: We have updated the content below to provide additional information. Thank you for your feedback.
[Introduction] 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). This change optimizes resource usage and enhances meeting experiences. [When this will happen:] Worldwide, GCC, GCC High, and DoD: Rollout will begin early January 2026 and complete by late January 2026. Note: Timelines may shift due to year-end feature flag rollout freeze. | Updated November 26, 2025: We have updated the content below to provide additional information. Thank you for your feedback.
[Introduction] 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). This change optimizes resource usage and enhances meeting experiences. [When this will happen:] Worldwide, GCC, GCC High, and DoD: Rollout will begin early January 2026 and complete by late January 2026. Note: Timelines may shift due to year-end feature flag rollout freeze. |
| 2025-11-27 | MC Last Updated | 11/25/2025 19:41:09 | 2025-11-26T19:18:12Z |
| 2025-11-27 | MC prepare | Update endpoint management and security software to allowlist ms-teams_modulehost.exe alongside ms-teams.exe.
Communicate this change to helpdesk staff to avoid confusion during troubleshooting. Update internal documentation if you reference Teams process names. Make sure the same QoS settings applied to ms-teams.exe are also applied to ms-teams_modulehost.exe. Refer to this page for details: Implement Quality of Service (QoS) in Microsoft Teams [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. https://learn.microsoft.com/microsoftteams/qos-in-teams | Update endpoint management and security software to allowlist ms-teams_modulehost.exe alongside ms-teams.exe.
Communicate this change to helpdesk staff to avoid confusion during troubleshooting. Update internal documentation if you reference Teams process names. Make sure the same QoS settings applied to ms-teams.exe are also applied to ms-teams_modulehost.exe. Refer to this page for details: Implement Quality of Service (QoS) in Microsoft Teams DO NOT remove QoS settings of ms-teams.exe. Only add QoS settings for ms-teams_modulehost.exe. [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. https://learn.microsoft.com/microsoftteams/qos-in-teams |
| 2025-11-26 | MC prepare | Update endpoint management and security software to allowlist ms-teams_modulehost.exe alongside ms-teams.exe.
Communicate this change to helpdesk staff to avoid confusion during troubleshooting. Update internal documentation if you reference Teams process names. Learn more about Teams performance improvements: https://learn.microsoft.com/microsoftteams/Microsoft Teams documentation. [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. | Update endpoint management and security software to allowlist ms-teams_modulehost.exe alongside ms-teams.exe.
Communicate this change to helpdesk staff to avoid confusion during troubleshooting. Update internal documentation if you reference Teams process names. Make sure the same QoS settings applied to ms-teams.exe are also applied to ms-teams_modulehost.exe. Refer to this page for details: Implement Quality of Service (QoS) in Microsoft Teams [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. https://learn.microsoft.com/microsoftteams/qos-in-teams |
| 2025-11-26 | MC IsMajorChange | False | True |
| 2025-11-26 | MC Last Updated | 11/25/2025 01:01:09 | 2025-11-25T19:41:09Z |
| 2025-11-26 | MC Messages | [Introduction]
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). This change optimizes resource usage and enhances meeting experiences. [When this will happen:] Worldwide, GCC, GCC High, and DoD: Rollout will begin early January 2026 and complete by late January 2026. Note: Timelines may shift due to year-end feature flag rollout freeze. | Updated November 25, 2025: We have updated the content below to provide additional information. Thank you for your feedback.
[Introduction] 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). This change optimizes resource usage and enhances meeting experiences. [When this will happen:] Worldwide, GCC, GCC High, and DoD: Rollout will begin early January 2026 and complete by late January 2026. Note: Timelines may shift due to year-end feature flag rollout freeze. |
| 2025-11-26 | MC Title | Upcoming Change to Teams Desktop Client on Windows | (Updated) Upcoming Change to Teams Desktop Client on Windows |
| 2025-11-26 | MC MessageTagNames | Feature update, User impact, Admin impact | Updated message, Feature update, User impact, Admin impact |
Last updated 6 days ago ago
