Track Teams call quality across your Microsoft 365 tenants, by site, user, and call, and see whether a poor call comes from your network or from a Microsoft service issue.
Microsoft Teams monitoring reads call records from Microsoft Graph and shows how Teams calls performed in each tenant. Cloudmon polls each tenant every 15 minutes from a Linux probe, using an app registered in Microsoft Entra. Microsoft publishes a call record 15 to 30 minutes after the call ends, so results are near real-time. This article covers monitoring of Teams calls. To send Cloudmon alerts to a Teams channel, see Microsoft Teams integration.
| Requirement | Description |
| Probe | A Linux probe with internet access to graph.microsoft.com. |
| Entra app registration | An app registered in Microsoft Entra. Keep its Directory (tenant) ID, Application (client) ID, and a client secret Value. For the steps, see Microsoft's guides to registering an app and adding a client secret. |
| Graph application permissions | CallRecords.Read.All to read call records, and ServiceHealth.Read.All to list issues in the Microsoft Issues tab. For the steps, see Microsoft's guide to adding application permissions to Microsoft Graph, which also covers admin consent. |
| Field | Description |
| Name | Required. The display name for this tenant in Cloudmon. |
| Probe | Required. The Linux probe that polls this tenant. |
| Directory (tenant) ID | Required. Find it in Entra → App registrations → your app → Overview. |
| Application (client) ID | Required. Find it in Entra → App registrations → your app → Overview. |
| Client secret | Required. The secret Value from Certificates & secrets, not the Secret ID. It is stored encrypted. When editing a tenant, leave it blank to keep the current secret. |
| Secret expiry | The date the secret expires. Cloudmon uses it to raise an alarm before the secret expires. |
| Alarm Rule | The thresholds and severities for this tenant. Default Alarms for Microsoft Teams is selected by default. |
| User Groups | The user groups to notify when alarms are raised. |
| Third Party Services | The third-party integrations for alarm notifications. |
The Microsoft Teams page summarizes all tenants by state, and charts calls, poor call percentage, and average MOS (Mean Opinion Score) by tenant over the last 24 hours. The Microsoft Teams Tenants table lists each tenant.
| Column | Description |
| Name | The tenant. Click it to open the tenant page. |
| State | The monitor state, such as Critical. |
| Tenant ID | The directory (tenant) ID. |
| Probe | The probe that polls the tenant. |
| Status | Whether monitoring is active. |
| Calls (24h) | The calls in the last 24 hours, with the number that failed. |
| Poor % (24h) | The share of calls that were poor. |
| MOS (24h) | The average estimated Mean Opinion Score. |
| Last Polled | When the probe last polled the tenant. |
| Secret Expiry | The client secret expiry date. |
| Actions | Turn monitoring on or off, Poll Now, Subnet → Site Map, edit, and delete. |
A call is poor when at least one of its streams crosses one of the following thresholds.
| Metric | Poor when |
| Jitter | Over 30 ms. |
| Packet loss | Over 10%. |
| Round-trip time (RTT) | Over 500 ms. |
| Concealed audio | Over 7%. |
A MOS of 4.0 and above is good, and a value under 3.5 is poor. The average for a tenant uses the worst audio leg of each call.
Click a tenant to open its page. Use the time range control to change the period, and the page menu for Poll Now, Subnet → Site Map, and Edit.
| Item | Description |
| Calls | Teams calls that started in the selected range, split into peer-to-peer and group. Click to open the calls. |
| Healthy Calls | The share of classified calls where no audio, video, or screen-share stream crossed a poor threshold. |
| Poor Calls | The share of classified calls with at least one poor stream. |
| Failed Calls | The share of calls that failed during setup or dropped mid-call. |
| Avg MOS (est.) | The average estimated MOS. |
| Avg Jitter / Loss / RTT | The average network figures for the range. |
| Active Users | Distinct signed-in users, org users and guests, who joined at least one call. Phone and anonymous participants are not counted. |
| Call Health | Good, poor, and failed calls over time. |
| Average MOS (estimated) | The estimated MOS over time. |
| Quality by Modality | The share of audio, video, and screen-sharing streams with no poor metric. Screen sharing is judged on loss only, since low frame rates are normal for static content. Click a row with poor streams to open those calls. |
| Top Poor-Call Causes | The most common reason each poor call was flagged, such as packet loss, jitter, weak Wi-Fi, media over TCP, or device glitches. Click a cause to open those calls. |
| Platforms | Participant legs by Teams client platform, such as Windows, macOS, web, iOS, Android, and Teams Rooms. |
| Connection Types | Participant legs by network: wired, Wi-Fi, mobile, or tunnel/VPN. |
Summary cards show the number of sites, with those that have too many poor calls, and the average latency, jitter, packet loss, and UDP share. The Site Statistics table lists each location with its subnets, users, calls, good and poor calls, poor percentage, MOS, and inbound and outbound latency, jitter, and loss, along with its UDP share.
The table lists everyone who joined a call in the selected range, with the most poor calls first. Search by name or email, or filter by All, Org Users for users of your Microsoft 365 tenant, or Guests & External for guests, federated users from other tenants, bots and apps, and phone participants.
Each row shows the site, IP address, connection, protocol, calls, poor calls, MOS, platform, audio device, and when the user was last seen. Click a name to open their platforms, connections, Teams version, sites, IP addresses, subnets, audio devices, and recent calls.
The table lists each call with its health, type, participants, number of participants (No. of Participants), start time, duration, MOS, poor cause, and sites. Search by participant, organizer, or call ID, or filter by health and type. Health is Good, Poor, Failed, or Unclassified, and type is P2P or Group.
Click a call to open its details, as described in the following table.
| Section | Description |
| Summary | The health, type, date and time, number of participants, organizer, lowest MOS, and call ID. |
| Participants | One row per participant leg: client version, location, IP address and subnet, reflexive IP, relay IP, connection, protocol, audio received and sent as jitter, loss, and RTT, MOS, impact, and device. Click Calls beside a participant to open their calls. |
| Timeline | Quality over the call for each participant, marked good, poor, or no metrics. Switch between Received and Sent, and between Audio, Video, and Screen Sharing. |
This tab lists Microsoft Teams service issues from the last 30 days, with their status, ID, title, type, feature, start time, and last update. Click an issue to read its details and user impact. When an issue is active, a banner warns that poor calls in the period may not be caused by your network. The tab needs the ServiceHealth.Read.All permission.
Until subnets are mapped, calls are grouped by subnet. Map them so that the Sites tab shows named locations.
| Field | Description |
| Location | Required. The name of the site. |
| Subnet | Required. A CIDR such as 10.20.0.0/16 covers a whole range. Without a mask, a value such as 192.168.1.0 matches that subnet exactly as Teams reports it in the Sites tab. |
| Country | The country code of the site, such as IN. |
| Longitude | A number from -180 to 180. |
| Latitude | A number from -90 to 90. |
A CSV file has the columns Location, Subnet, Country, Longitude, and Latitude. The header row is optional. Click Export to download the current map.
To configure alarm rules, see How to Configure Alarm Rules.
To create a report, see Reports.