Fix Teams Admin Center Usage Report Shows Zero Activity for One User

You open the Teams admin center usage report and see a single user with zero activity, even though that person uses Teams daily. This happens because the usage report pulls data from multiple sources, and a gap in any one of them can blank out the entire row. The report depends on the user having a valid Teams license, a properly assigned policy, and a client that sends the right telemetry. This article explains the root cause of the zero-activity row and gives you a step-by-step process to diagnose and fix it.

You will learn how to check licensing, policy assignment, sign-in status, and client telemetry, and then how to force the report to refresh. You will also see related failure patterns that affect the same report for other users.

Why the Teams Usage Report Shows Zero Activity for One User

The Teams usage report in the admin center aggregates data from the Teams telemetry pipeline. That pipeline receives signals from the Teams desktop, web, and mobile clients. For the report to show activity, three conditions must be true at the same time.

First, the user must have a valid Teams license. The report filters out unlicensed users entirely, but a misassigned license can cause a row to appear with zero values. Second, the user must have a Teams policy that allows activity tracking. Some policies, like the messaging policy, can disable certain features that generate telemetry. Third, the user’s client must actually send telemetry to Microsoft 365. If the client is not signed in, is offline, or has a corrupted cache, no data reaches the pipeline.

The report refreshes every 24 to 48 hours. That delay means a user who started using Teams yesterday may show zero activity for up to two days. This is normal and not a fault.

The Role of the Licensing Filter

The usage report reads from the Microsoft 365 user object. If the Teams service plan is not assigned to the user, the report cannot match the user to any telemetry. A common cause is a user who has a Microsoft 365 license but with the Teams plan disabled in the license options. Another cause is a user who has a Teams license but is in a different tenant than the one you are viewing.

How Policy Assignments Block Telemetry

Teams policies control which features are available. For example, the messaging policy includes a setting called Allow chat. If that is turned off, the user cannot send chat messages, and the chat activity metric stays at zero. Similarly, the meeting policy controls whether the user can start or join meetings. If the policy blocks all meetings, the meeting count will be zero even if the user is active in other ways.

Client Telemetry Gaps

The Teams desktop client sends a heartbeat every few minutes while it is running. The web client sends telemetry only when a tab is active. The mobile client sends telemetry when the app is in the foreground. If the user runs Teams only in a browser tab that is not focused, the telemetry stream is sparse. Also, if the client is not updated, it may fail to send the newer telemetry events that the report expects.

Steps to Diagnose and Fix a Zero-Activity User in the Teams Usage Report

Follow these steps in order. Each step verifies one link in the telemetry chain.

1. Verify the user has a Teams license
   Open the Teams admin center at admin.teams.microsoft.com. Go to Users > Manage users. Find the user in the list and select their name. In the user pane, click Licenses. Confirm that the Microsoft Teams service plan is toggled on. If it is off, toggle it on and click Save. Wait 30 minutes for the license change to propagate.
2. Check effective policy assignments
   In the same user pane, click Policies. Review the assigned messaging, meeting, and calling policies. Click each policy name to open the policy settings. Ensure that Allow chat, Allow meeting, and Allow calling are set to On. If any is off, assign a different policy that has those settings enabled. Use the Edit button next to each policy type.
3. Confirm the user is signed in to the correct tenant
   Ask the user to open Teams and click their profile picture in the top right. The email address shown must match the user object you are inspecting in the admin center. If the user is signed in with a personal account or a different work account, sign them out and sign in with the correct account. Also check the user’s Microsoft 365 sign-in status in the Microsoft 365 admin center at admin.microsoft.com. Go to Users > Active users, select the user, and verify that Sign-in status is Allowed.
4. Clear the Teams client cache
   A corrupted cache can stop telemetry from being sent. On the user’s Windows machine, close Teams completely. Right-click the Teams icon in the system tray and choose Quit. Then open File Explorer and navigate to %appdata%\Microsoft\Teams. Delete the contents of the Cache, Code Cache, and GPUCache folders. Restart Teams. The client will rebuild the cache and resume sending telemetry.
5. Force the usage report to refresh
   After the previous steps, wait at least 24 hours. The usage report refreshes on a daily cycle. You can check the last refresh time at the top of the report page. If the report still shows zero after 48 hours, use the Export button on the report page to download a CSV file. The CSV may contain more granular data than the on-screen table.

Alternative Method: Use PowerShell to Check Telemetry

If the admin center steps do not reveal the cause, use PowerShell to inspect the user’s license and policy directly. Connect to Microsoft Graph with the Connect-MgGraph cmdlet and run the Get-MgUser command to retrieve the user’s assigned licenses. Then use Get-MgUserTeamwork to see the effective policy assignments. This method is faster when you have many users to check.

If Teams Still Shows Zero Activity After the Main Fix

Teams Usage Report Shows Zero for a User Who Only Uses the Web Client

The web client sends telemetry only while the tab is active and in focus. If the user switches to another tab for more than a few minutes, the telemetry stops. Ask the user to keep the Teams tab active during a test session. Also, the web client requires the latest version of Edge, Chrome, or Firefox. An outdated browser can block the telemetry scripts. Have the user update the browser and refresh the Teams tab.

Teams Usage Report Shows Zero for a User Who Uses Teams on a Mobile Device

The mobile app sends telemetry only when the app is in the foreground. If the user checks Teams briefly and then switches to another app, the activity may not register. Also, the mobile app must have push notifications enabled. Go to Settings > Notifications in the mobile app and turn on notifications. Then ask the user to keep the app open for at least 10 minutes during a test.

Teams Usage Report Shows Zero for a User Who Is in a Different Data Region

If the user is in a different geographic region, the telemetry may be routed to a different data center. The admin center report aggregates data from all regions, but there can be a delay. Check the user’s location in the Microsoft 365 admin center. If the user is in a region that is not served by the same data center as your tenant, wait an additional 24 hours for the data to sync.

Teams Admin Center Usage Report vs Teams Client Activity: Key Differences

Item	Teams Admin Center Usage Report	Teams Client Activity Feed
Data source	Aggregated telemetry from all clients	Real-time local activity from the signed-in client
Refresh frequency	Every 24 to 48 hours	Immediate, as events occur
Granularity	Per-user daily totals for messages, meetings, and calls	Per-conversation and per-meeting details
License filter	Only licensed users appear	Any signed-in user appears
Policy impact	Policies can block telemetry	Policies can block features but not the activity feed
Use case	Administrative reporting and compliance	User self-service and troubleshooting

You can now verify every link in the telemetry chain, from licensing to client cache. Start with the license check, then move to policy assignments, and then clear the client cache if needed. After each fix, wait 24 hours and re-export the report to confirm the change. For a faster check, use the PowerShell method to inspect multiple users at once. If the issue persists, compare the admin center report with the user’s client activity feed to isolate the break.