Monitoring Benefit
The Simplified Teams Call Quality Dashboard summarises Microsoft Teams call reliability and quality for your tenant, and raises warnings and alerts against thresholds you set. The Daily view is the default working view: long enough to smooth out the noise of a single bad hour, short enough to still be actionable.
It exists because Microsoft's own Call Quality Dashboard is powerful but slow to interrogate. This condenses it to a handful of indicators that can sit on a monitoring dashboard and alert without anyone querying anything.
The same metrics are presented over three periods, each answering a different question:
- Hourly — is something wrong right now?
- Daily — this page. Is today worse than normal?
- Monthly — is call quality getting better or worse over time?
The page can be opened directly on the ENow web server:
http://localhost:20080/MailscapeWeb/MicrosoftTeamsCQDDaily.aspx?server=Office-365
Replace localhost with the web server's host name if browsing from elsewhere, and 20080 with your own port if it was changed at installation.
What is measured
The metrics divide into two groups. The distinction matters when you are triaging: reliability is about calls that failed, quality is about calls that connected but were bad.
Reliability — did the call happen at all?
| Metric | What it tells you |
|---|---|
| Total Call Setup Failure Percentage | Share of calls that never established. A rise here is usually infrastructure or client-side, not bandwidth. |
| Setup Failure Rate Percentage | The failure rate expressed against attempts, so it stays meaningful when call volume changes. |
| Total Drop Call Percentage | Share of calls that connected and then dropped. Drops and setup failures rising together points at the network path; drops alone often points at a specific site or client. |
Quality — how good were the calls that did connect?
| Metric | What it tells you |
|---|---|
| Audio Poor Stream Count | Streams Microsoft classified as poor. Audio is the one users complain about, so treat this as the primary quality signal. |
| Video Poor Stream Count | The same for video. Video degrades before audio under constrained bandwidth, so video rising alone can be an early warning. |
| Average Round Trip | Latency. High round trip with low loss and jitter suggests routing or distance rather than congestion. |
| Average Packet Loss Rate | The most direct cause of audio breaking up. |
| Average Jitter | Variation in packet arrival. Jitter rising while loss stays flat typically means congestion somewhere in the path. |
Reading them together is what narrows the cause. Loss and jitter together suggest a congested link; latency alone suggests a routing change; poor streams with all three normal suggests something local to the endpoints, such as wireless or audio devices.
Rate My Call
Alongside the telemetry, the page surfaces users' own Rate My Call responses, including a Tier 1 (executive) list driven by a directory group. This is the subjective counterpart to the measured metrics, and it is worth reading against them — telemetry that looks acceptable while users keep rating calls badly is a real finding.
For per-executive detail rather than a tenant summary, see Microsoft Teams - VIP Monitoring Status.
Where the thresholds are set
Each indicator is evaluated against warning and critical thresholds configured in the Office 365 thresholds section of the ENow Admin Console. They are per-install, so confirm the values in force in your own console before treating an indicator as unexpected.
"No test results have been received" is a different condition
When collection has not run, the page does not show a failure. It shows this instead:
No Microsoft Teams Simplified CQD Daily Tests Status test results have been received.
The two look similar at a glance and mean opposite things. A failed test means data arrived and breached a threshold — there is a call quality problem to investigate. This message means no data arrived at all, so nothing has been evaluated and no threshold could have fired. Investigating call quality at that point is wasted effort; the thing that is broken is collection.
Treat it as a collection problem and work the data collection checks in Microsoft Teams - VIP Monitoring Status. A newly configured tenant will also show this message until the first collection completes, which is expected rather than a fault.
How do we verify the monitoring test results?
- Compare against Microsoft's Call Quality Dashboard at cqd.teams.microsoft.com for the same day. The figures come from the same source, so they should broadly agree.
- Allow for Microsoft's reporting delay. Call quality data is not real time and can take hours to appear. Today's figures are always partial until the day closes — which is the single most common reason the Daily view appears to disagree with something.
- Check call volume alongside the percentages. A reliability percentage calculated over very few calls swings wildly. A 50% setup failure rate on two calls is not the same finding as 50% on two thousand.
Common warning or error results, and potential solutions
| Result | Potential solution |
|---|---|
| Packet loss and jitter both raised | Congestion on a shared path. Check the Hourly view to find when it started and whether it aligns with the working day. |
| Round trip raised, loss and jitter normal | Latency rather than congestion — a routing change, a failed-over circuit, or traffic taking an unexpected path to Microsoft. |
| Setup failures raised, quality metrics normal | Calls are not being established. Look at client versions, firewall and proxy changes rather than bandwidth. |
| Video poor streams raised, audio normal | Often an early bandwidth warning. Teams degrades video first to protect audio. |
| An indicator stays green while users complain | Check the configured thresholds, and check the Rate My Call data. A tenant-wide average can absorb a serious problem affecting one site or team. |
| A single day is dramatically worse with no other evidence | Check call volume for that day. A low-volume day such as a holiday can produce an extreme percentage from a handful of calls. |
| The page reports that no test results have been received | Not a call quality fault. Collection has not run — see the section above, and the data collection checks in Microsoft Teams - VIP Monitoring Status. The Teams views share a collection pipeline and normally fail together. |
Comments
0 comments
Article is closed for comments.