ChangeIntelIT change radar
Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 272/272 feeds/APIs · 469/469 docs · 8/9 advisories · checked 17:51 UTC Customize Public modeDiscuss ChangeIntel on Discord
MC1189656 Plan for changeUpdated messageFeature updateUser impactAdmin impact

Upcoming Change to Teams Desktop Client on Windows

From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.
Microsoft Teams
Microsoft 365 admin center

Rollout

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

Schedule dates changed in the text

Date phrases in schedule sentences differ between the versions this installation saw
  • Seen 15 Jan 2026 January 2026 → early January 2026
  • Seen 12 Dec 2025 early January 2026 → January 2026

Read from date phrases in Microsoft's text, not from notice metadata. A changed phrase can be a moved rollout, a new milestone or just rewording; "What changed" below shows which.

What the notice says

Microsoft’s text, safely structured

Updated January 15, 2026: We are canceling a proposed change related to renaming the existing Calling and Meetings executable.

No action is required from administrators. This change did not introduce a new binary. It involved renaming the existing executable used for Calling and Meetings as a workaround for a Windows compatibility issue.

What Happened?

To reduce administrative effort, we partnered with the Windows team to deliver the fix for a Windows compatibility issue. With the Windows fix now fully rolled out in Windows 24H2 and 25H2, the executable name change is no longer required and has been rolled back.

Was this a security, reliability, or compliance issue?

  • This was not a security or compliance issue.
  • It was a platform compatibility issue in Windows.
  • No customer data, identity, or tenant configuration was at risk.

Was my tenant impacted?

Only organizations participating in our Technology Adoption Program (TAP) were affected. Specifically, the change applied only to the TAP Admin earlyadopter subset (Ring 1.5).

If your organization does not participate in the Microsoft Technology Adoption Program, you were not impacted in any way. The change has been fully rolled back for TAP participants, with no lasting configuration or behavioral changes on client machines. No administrator action is required.

What if we haven’t deployed recent Windows updates yet?

We understand that many enterprises deploy Windows cumulative updates on managed timelines.

  • There is no risk or degradation if the referenced Windows KBs are not installed.
  • New features that depend on these Windows updates will explicitly check for the presence of the required KBs and will only enable when they are available.
  • If the KBs are not installed, those features simply remain disabled—no functionality breaks and no admin action is required.

Windows updates that include the fix

The Windows compatibility fix is included in Windows updates for versions 24H2 and 25H2, delivered through KB5068861.

What to expect next?

  • No changes to admin configuration or tenant settings
  • No service disruption

---Original message---

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

Rollout will begin early January 2026 and complete by late January 2026.

Note: Timelines may shift due to year-end feature flag rollout freeze.

How this affects your organization

  • Who is affected: All users running the Teams Desktop Client on Windows.
  • What will happen:
    • A new process (ms-teams_modulehost.exe) will appear in Task Manager under the main Teams process (ms-teams.exe).
    • This process is dedicated to calling features and improves performance.
    • No changes to user workflows or UI; however, admins should ensure endpoint and security software allow this new process.

What you can do to 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
    • 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.

What changed

Between archive captures, newest first

  1. Updated December 17, 2025:January 15, 2026: We understand that implementingare canceling a proposed change related to renaming the current guidance involves considerable effortexisting Calling and Meetings executable. No action is required from administrators. This change did not introduce a new binary. It involved renaming the existing executable used for administrators,Calling and Meetings as a workaround for a Windows compatibility issue.  What Happened?  To reduce administrative effort, we are actively workingpartnered with the Windows team to reduce this impact. We are exploring ways to make policy changes as seamless as possible,deliver the fix for a Windows compatibility issue. With the Windows fix now fully rolled out in close partnership withWindows 24H2 and 25H2, the Windows team. Givenexecutable name change is no longer required and has been rolled back.  Was this ongoing work, we recommend pausing any testinga security, reliability, or compliance issue?  This was not a security or compliance issue.  It was a platform compatibility issue in Windows.  No customer data, identity, or tenant configuration updates relatedwas at risk.  Was my tenant impacted?  Only organizations participating in our Technology Adoption Program (TAP) were affected. Specifically, the change applied only to this feature. Updated instructions and revised guidance will be shared as part ofthe TAP Admin earlyadopter subset (Ring 1.5).  If your organization does not participate in the formal communication plannedMicrosoft Technology Adoption Program, you were not impacted in any way. The change has been fully rolled back for January 2026. Thank youTAP participants, with no lasting configuration or behavioral changes on client machines. No administrator action is required.  What if we haven’t deployed recent Windows updates yet?  We understand that many enterprises deploy Windows cumulative updates on managed timelines.  There is no risk or degradation if the referenced Windows KBs are not installed.  New features that depend on these Windows updates will explicitly check for the valuable feedback we’ve received. Wepresence of the required KBs and will only enable when they are available.  If the KBs are currently reassessingnot installed, those features simply remain disabled—no functionality breaks and no admin action is required.  Windows updates that include the rollout timelines to ensure alignment with your needsfix  The Windows compatibility fix is included in Windows updates for versions 24H2 and operational requirements. You can25H2, delivered through KB5068861.  What to expect a formal update from us by mid to late January 2026.next?  No changes to admin configuration or tenant settings  No service disruption  ---Original message--- Introduction We’re improving the performance and startup time of calling features in … change optimizes resource usage and enhances meeting experiences. When this will happen: Updated rollout timing will be announced inRollout will begin early January 2026 and complete by late January 20262026. Note: Timelines may shift due to year-end feature flag rollout freeze. How …

  2. Updated December 12,17, 2025: We understand that implementing the current guidance involves considerable effort for administrators, and we are actively working to reduce this impact. We are exploring ways to make policy changes as seamless as possible, in close partnership with the Windows team. Given this ongoing work, we recommend pausing any testing or configuration updates related to this feature. Updated instructions and revised guidance will be shared as part of the formal communication planned for January 2026. Thank you for the valuable feedback we’ve received. We are currently reassessing …

    • Major change Yes → No

    Updated November 26,December 12, 2025: Thank you for the valuable feedback we’ve received. We have updatedare currently reassessing the content belowrollout timelines to provide additional information. Thank you for your feedback.ensure alignment with your needs and operational requirements. You can expect a formal update from us by mid to late January 2026. Introduction We’re improving the performance and startup time of calling features in … change optimizes resource usage and enhances meeting experiences. When this will happen: Worldwide, GCC, GCC High, and DoD: Rollout will begin early Updated rollout timing will be announced in January 2026 and complete by late January 2026. Note: Timelines may shift due to year-end feature flag rollout freeze. How …

  4. Updated November 25,26, 2025: We have updated the content below to provide additional information. Thank … to this page for details: Implement Quality of Service (QoS) in Microsoft TeamsTeamsDO 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.

  5. Updated November 25, 2025: We have updated the content below to show as intended.provide additional information. Thank you for your feedback. Introduction We’re improving the performance and startup … 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.

    • Tags Feature update, User impact, Admin impact → Updated message, Feature update, User impact, Admin impact

    Updated November 25, 2025: We have updated the content below to show as intended. Thank you for your feedback. Introduction We’re improving the performance and startup time of calling features in … 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.

    • Major change No → Yes
  8. · first version seen

Learn more

Links from the notice and their documentation checks

No related evidence found in this installation's recent collection. This does not establish that no announcement exists.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
  • 2 linked pages have not been read yet.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 27 Oct 17:51 UTC · 272 of 272 readable · 270 fully read · documentation 469/469 current

No accounts or analytics; your preferences stay in your browser. Information, not advice. ChangeIntel is an independent tool and is not affiliated with or endorsed by Microsoft, Apple, Google, Broadcom (VMware), Jamf, Oracle, Mozilla, or any other vendor it covers. Product names are trademarks of their owners. Built by Evotec.