Fix Teams Admin Center Usage Report Shows Zero Activity After a Bulk Policy Assignment

You assigned Teams policies to hundreds of users in bulk, but the Teams admin center usage report now shows zero activity for those users. This problem typically happens when the policy assignment does not apply correctly or when the report has not refreshed. The root cause is often a mismatch between the assigned policy and the user’s effective policy, or a delay in telemetry processing. This article explains why the report shows zero activity and provides step-by-step fixes to resolve it.

Why Teams Usage Reports Show Zero Activity After a Bulk Policy Assignment

The Teams admin center usage report relies on telemetry data sent from the Teams clients to Microsoft 365. When you assign a policy in bulk, the assignment may not take effect immediately. The policy assignment process is asynchronous, meaning it can take up to 24 hours to propagate to all users. Additionally, the usage report itself has a refresh delay, often up to 48 hours, before new activity appears.

Another common cause is that the bulk assignment overwrites a user-specific policy that was previously set. For example, if you assigned a global policy to a group, but individual users had a custom policy assigned directly, the direct assignment takes precedence. The usage report then reflects the effective policy, which may not be the one you intended to apply.

Finally, the report may show zero activity because the users have not actually used Teams after the policy change. The report only counts active users who have joined a meeting, sent a chat, or made a call within the selected time period. If the policy change did not require users to restart Teams, they may continue using the old policy, but the report still records their activity.

Steps to Diagnose and Fix Zero Activity in Teams Usage Reports

Follow these steps in order. Each step addresses a specific cause of the zero activity display.

Step 1: Verify the Effective Policy Assignment

1. Open the Teams admin center
   Go to Teams admin center > Users > Manage users. Search for a user who shows zero activity in the report.
2. Select the user and view policies
   Click the user’s name, then select Policies in the left pane. Check the effective policy for each policy type, such as Meeting policy or Messaging policy.
3. Compare with the bulk-assigned policy
   If the effective policy does not match the policy you assigned in bulk, the assignment did not apply. Re-run the bulk assignment using the correct group or user list.

Step 2: Check the Report Date Range and Refresh Delay

1. Navigate to the usage report
   Go to Teams admin center > Reports > Usage reports. Select the Teams user activity report.
2. Set the date range
   Choose a date range that includes at least 48 hours after the bulk policy assignment. If the report still shows zero, wait another 24 hours and refresh.
3. Filter by the affected group
   Use the filter to show only the users who received the bulk assignment. This helps you see if the issue is isolated to that group.

Step 3: Confirm No Conflicting Policy Overrides

1. Review policy precedence
   In Teams, a user-level policy assignment overrides a group policy assignment. If you assigned a policy to a group, but some users have a direct assignment, the direct assignment wins.
2. Remove conflicting direct assignments
   Go to Teams admin center > Users > Manage users, select the user, and under Policies, clear any direct policy assignments that conflict with the bulk-assigned policy.
3. Re-run the bulk assignment
   After clearing conflicts, re-run the bulk assignment to ensure the intended policy is applied.

Step 4: Verify Users Are Actually Active

1. Ask users to sign out and sign back in
   Policy changes may not take effect until the user restarts Teams. Have users sign out and sign back in to force the policy refresh.
2. Check Teams client version
   Ensure users are running a supported version of Teams. Old clients may not send telemetry correctly.
3. Use the Teams admin center activity log
   Go to Teams admin center > Activity log to see if the policy assignment operation completed successfully.

If Teams Usage Reports Still Show Zero Activity

Teams Usage Report Shows Zero for Only Some Users

If only a subset of users shows zero activity, the cause is likely a policy conflict or a user who has not used Teams recently. Check the effective policy for each user as described in Step 1. Also, verify that those users have actually launched Teams and performed an activity within the report date range.

Teams Usage Report Shows Zero After a Group Policy Assignment

Group policy assignments apply to users in the group only if the group is synchronized with Azure AD. If the group membership changed after the assignment, users who left the group lose the policy. Re-check the group membership and re-run the assignment for the current members.

Teams Usage Report Shows Zero Because of Telemetry Delay

The usage report can take up to 48 hours to reflect activity. If you just assigned the policy, wait the full 48 hours before troubleshooting further. You can also use PowerShell to check the effective policy immediately, which does not depend on telemetry.

Teams Admin Center Usage Report vs PowerShell Get-CsOnlineUser

Item	Teams Admin Center Usage Report	PowerShell Get-CsOnlineUser
Data source	Telemetry from Teams clients	Direct from Azure AD and policy store
Refresh delay	Up to 48 hours	Near real-time
Shows policy assignments	No	Yes, effective policy per user
Best for verifying activity	Yes, after delay	No, only policy state

After following these steps, you can confirm that the bulk policy assignment applied correctly and that the usage report will populate once telemetry catches up. Use PowerShell to verify policy assignments immediately without waiting for the report refresh. For future bulk assignments, always check the effective policy for a sample of users right after the operation completes. This prevents the report from showing zero activity and saves troubleshooting time.