Microsoft Teams new client usage report
The Microsoft Teams desktop client usage report gives you an overview of the Teams desktop clients in use within your organization. It highlights platform, version, and user type to help you better understand the current state of your user’s desktop clients.
How to get to the Microsoft Teams desktop client usage report
- In the Teams admin center, go to the Analytics & Reports > Usage Reports page.
- From the Usage Reports page, choose the Teams desktop client usage report, choose a date range selection, and select Run report.
Interpret the Microsoft Teams client usage report
The graph in the Teams desktop client usage report shows the usage of classic Teams and new Teams as a percentage within your tenant. These numbers are directly related, so if one number increases the other decreases. Take note of the important characteristics of this data:
- This data represents Windows or Mac Teams desktop clients and not web or mobile clients, but some Room devices may also show up. These devices can be filtered out if needed by using the Export functionality of the report. We're investigating ways to filter out these devices in a future version.
- This data may also contain Guest users if you allow, and use, Guest Access within your tenant. You'll see #EXT# on these users, which you can use to filter them out using the Export functionality of the report. We're investigating ways to filter out these users in a future version.
- This data is dependent on a user’s Teams desktop client being actively used. When a user isn't active on their desktop client or their data can't be reported in for any reason, their data won't be reported for that period. There will be no data reported if no data was available. This missing information can result in fluctuations in the data, for example during weekends or when users go on vacation.
- A user's data comes from their most recent usage when the snapshot is taken for each platform, Windows or Mac. If a user has multiple machines they use regularly on any single platform, whichever machine they used last will be represented for that day. For most people who have multiple machines, they usually have a primary device that gets the most use.
- In some scenarios, the classic Teams client reported may not show a version number. This lack of a version number only affects classic Teams and any new Teams clients listed will always show their version number. When the transition to new Teams is complete, this issue will be resolved.
The data in the table columns below the graph allow a more granular look at individual users and the state of their Teams desktop client. This data can be exported using the Export to Excel function in the top right corner, and columns can be shown or hidden using the Edit columns function also in the top right corner.
Column | Description |
---|---|
Username | UPN of the user. |
Display name | Display name of the user. |
Classic or new (Windows) | Whether or not a Windows user is using the classic Teams or new Teams application. |
App version (Windows) | The version number of the Windows Teams application for the user. |
Classic or new (Mac) | Whether or not a Mac user is using the classic Teams or new Teams application. |
App version (Mac) | The version number of the Mac Teams application for the user. |
User type | What deployment ring a user is assigned to. Differences between users in this column can explain why they may have different versions of the Teams application. The values that may display are: - TAP Admin: Administrators who participate in the Microsoft Teams TAP program. Sometimes referred to as R1.5. - Developer Preview: Developers who have opted into early preview of developer focused functionality for Teams app development. Sometimes referred to as R1.6. - TAP: Users who participate in the Microsoft Teams TAP program. Sometimes referred to as R3. - Public Preview: Users who participate in the Public Preview program. Sometimes referred to as R3.6. - Production: Regular users who don't have access to early preview functionality. Sometimes referred to as R4. - GCC Production: Regular GCC users who don't have access to early preview functionality. |
Example Scenarios for the Teams desktop client usage report
- While your organization is moving from classic Teams to new Teams, this report allows you to monitor progress along the way. You may have given your users the ability to toggle back and forth between classic and new Teams, or you may be moving groups of users to new Teams on a set schedule. In either case, this report allows you to see and confirm the transition as you proceed.
- If your organization allows users to toggle back and forth between classic and new Teams ahead of the automatic update coming on March 31 2024, this report will allow you to identify users who have chosen to remain on classic Teams. With that information, you can perform any relevant communication or change management campaigns to help those users make the switch.
- Using the export capability of the report, you can identify any Teams desktop clients in your organization stuck on an older version and that aren't automatically updating as they should. Becoming stuck and not automatically updating is often a result of some sort of network or machine issue or a configuration change. Identifying these users with this report allows you to proactively identify and engage with these users to investigate and resolve the issue.