Published Feb 25, 2025
IT Administrators can now monitor Microsoft Teams desktop client health through a new page in the Teams admin center. This feature provides insights into client health metrics and allows monitoring of version adoption. The rollout begins late April 2025, with completion expected by early May 2025 for general availability and mid-June 2025 for GCC, GCC High, and DoD. No admin action is required.
Updated June 4, 2025: We have updated the timeline below. Thank you for your patience.
IT Administrators can now monitor the health of Microsoft Teams desktop clients for Windows and Mac through the new ‘Teams client health’ page in the Teams admin center.
This message is associated with Microsoft 365 Roadmap ID 478610.
When this will happen:
General Availability (Worldwide): We will begin rolling out late April 2025 (previously late March) and expect to complete by early May 2025 (previously late April).
General Availability (GCC, GCC High, DoD): We will begin rolling out late April 2025 and expect to complete by mid-June 2025 (previously late May).
How this will affect your organization:
When these capabilities and tools are released in Teams admin center, administrators will be able to access the ‘Teams client health’ page via the left navigation and be able to proactively monitor Teams client health and Issues impacting end users in their tenant as well as find actionable guidance on how to troubleshoot and resolve these user-impacting issues.
Administrators will also be able to proactively monitor which devices and users might be using outdated versions of the Teams client to be able to move them to the latest and most secure version
Additionally, this information can also be sorted, filtered, and exported to a .csv for further analysis and troubleshooting.
This will be only accessible to limited admin roles: Teams Administrator, Teams Communication Administrator, and Teams Communications Support Engineer.
What you need to do to prepare:
This rollout will happen automatically with no admin action required.
Ensure you and the required users have access to the above-mentioned roles or request to enable this new feature for more roles.
For more information, refer to our documentation: