Call Quality Reporting
The Teams call quality reports currently only looks at average values (packet loss, latency, jitter) when flagging possible problems with media quality and because of this, meetings that have high amounts of maximum packet loss, latency or jitter are being rated as Good which in turn makes it very difficult to track down possible problems without having to drill down into each user's meeting connection. The Teams call quality reports need to take maximum values into account when rating media quality.
Also, it would be extremely beneficial to have a new in-between rating (e.g. "Impacted") to help rate those calls that are neither Good nor Poor. For example, the current threshold for a Poor rating for packet loss rate is 10% and that number is way too high. If a third rating was added, the threshold for packet loss could be 6% or 7% (while still keeping Poor at greater than 10%) and that would allow those who are troubleshooting to more easily identify the users who were impacted.