Understanding Call quality report

Modified on Thu, 10 Mar 2022 at 04:12 AM

Call Quality report shows detailed information about Teams calls and meetings per each session in your Office 365 tenant. It is updated almost in real time and uses the Graph API to import the data.


On the top you can find the chart showing the calls and meetings quality grouped by department/country/company over the last 30 days by default. If any user session has any poor audio, video or sharing quality, then the whole call is marked as poor.

You can switch between the tabs department/country/company and change the date range from the last 30 days to the last 7 days. Also, it is possible to filter the results shown on the chart by excluding the specific call quality. To do it you should just click on the quality name present in the legend to be excluded from the chart. 


The detailed table provided you together with the common data provides you with some specific data on:


Call quality

can be marked as Poor / Good / Unknown. Overall call quality based on Stream (audio, video, VBSS) counts.
OrganizerTagsTags attributed through CoreView portal to the user who is call organizer 

Attendees type

Internal Only vs With External

Call audio quality

can be marked as Poor / Good / Unknown. Please refer to Microsoft Audio classifier for more details.

Call endpoints

Audio devices and up-to-date clients, such as audio, video, video Based Screen Sharing, screen Sharing.

Call type

Call vs Meeting

Call VBSS quality

can be marked as Poor / Good / Unknown. Please refer to Microsoft VBSS classifier for more details.

Call video quality

can be marked as Poor / Good / Unknown. Please refer to Microsoft Video classifier for more details.


Moreover, by clicking on call recorder ID it is possible to open the call card showing the details of specific call. 


Note: if we have a user with multiple session for the same meeting we count this user as a single one.




Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us how can we improve this article!

Select atleast one of the reasons

Feedback sent

We apprciate your effort and will try to fix the article