Reporting and Usage Analytics

The Teams admin center provides built-in usage reports, including Teams usage, Teams device usage, PSTN usage, and PSTN blocked users reports, each viewable over 7-day, 30-day, or 90-day windows. By default, Microsoft conceals user-identifiable information such as display names and email addresses in these reports after a set period, showing them as anonymized identifiers instead, unless an administrator with the appropriate role explicitly enables the 'Display concealed user information in all reports' setting, which itself is a privacy-sensitive action that should be governed by policy.

The Call Quality Dashboard provides tenant-wide, aggregated call and meeting quality metrics, such as jitter, packet loss, and Mean Opinion Score (MOS), broken down by location, subnet, and network segment, primarily used by network engineers to identify systemic issues like a poorly performing WAN link at a specific office. Call Analytics, by contrast, gives per-user, per-call diagnostic detail, including device, network, and codec information for a single specific call, and is the tool a helpdesk agent uses to troubleshoot one user's reported 'my call kept freezing' complaint.

The Microsoft Graph reports API exposes usage endpoints such as getTeamsUserActivityUserDetail and getTeamsDeviceUsageUserDetail, letting administrators pull the same underlying usage data shown in the admin center programmatically, typically on a scheduled basis, for ingestion into custom dashboards or data warehouses. Microsoft also provides a downloadable Power BI template that connects to these Graph endpoints and visualizes usage alongside license assignment and adoption trend data, giving IT leadership a combined view of adoption momentum rather than requiring them to stitch together separate reports manually.

Usage report data retains user-identifiable names and email addresses for a limited window governed by the tenant's privacy configuration; by default, that identifiable information is concealed after a period unless explicitly enabled, and even when enabled, the underlying report data itself is not retained indefinitely by Microsoft. Because this data reveals individual communication and collaboration patterns, such as which specific employees are heavy or light Teams users, any decision to export it for long-term storage or combine it with other HR systems should go through the organization's formal data-retention and privacy review process rather than being treated as routine IT reporting.