# Teams call quality dashboard and analytics

Canonical: https://warmtransfer.net/knowledge/teams-call-analytics

Last verified: 2026-09-24

Microsoft describes Call Quality Dashboard (CQD) as an organization-wide trend view and Teams admin center as a per-user call and meeting troubleshooting view[^60]. Microsoft names four ways to reach call quality data: the CQD portal, CQD in Power BI, the Users page in Teams admin center (not customizable), and the Microsoft Graph call records API[^16].

## How it works

Microsoft's current CQD overview and setup pages give the CQD portal address as https://cqd.teams.cloud.microsoft, also reachable from Teams admin center under Analytics & reports > Call Quality Dashboard[^24]. Using CQD with Skype for Business Server 2019 requires configuring Call Data Connector[^26].

CQD call records remain in CQD for 12 months, and both summary and detailed reports cover the last 12 months of data[^25]. CQD keeps end-user identifiable information (EUII) for only 28 days; after that the EUII fields are cleared and the remaining data is EUII-free[^17]. CQD fields treated as EUII include IP address, user ObjectId, MAC address, phone number, UPN, feedback text, client endpoint name, BSSID, local and remote site, and auto attendant and call queue identity[^18].

Among CQD access roles, Reports Reader and Teams Communications Support Specialist can view CQD reports but cannot see EUII fields, while Teams Communications Support Engineer and Global Reader can see EUII[^19]. Only Global Administrator, Teams Administrator, Teams Communications Administrator and Skype for Business Administrator can upload building data for CQD; support engineer, support specialist, Global Reader and Reports Reader cannot[^10]. CQD does not currently support delegated administration for Microsoft Partners[^22].

CQD summary reports have four tabs: Overall Call Quality, Server-Client, Client-Client, and Voice Quality SLA[^27]. CQD calculates Poor % as Poor streams divided by (Poor plus Good streams) times 100, so Unclassified streams do not affect it[^23]. CQD marks an endpoint Inside only if its subnet appears as InsideCorp in uploaded building information; without building data, every stream is classified Outside[^21]. CQD classifies a stream as WiFi if either of its two endpoints is connected to a WiFi network; server endpoints always count as wired[^28].

In August 2026 Microsoft changed the CQD First/Second UPN and First/Second Object Id logic to reflect users associated with Teams Phone Mobile numbers in PSTN calls[^11]. In July 2026 CQD added First/Second Public IP columns that reflect the Public IP values in the active building file, and building metadata began supporting Public IP values[^14]. In February 2026 CQD changed Meeting Id to match the numeric Meeting Id in Teams meeting invites and added a Thread Id column carrying the value Meeting Id used to hold[^12]. Since April 2026 CQD First/Second Feedback Rating is 0 when a Rate My Call survey was offered but the user did not submit it or submitted it without a rating[^20]. In January 2026 CQD added First/Second Is Call Throttled columns for device CPU throttling and First/Second HW Encoder Blocked and HW Decoder Blocked columns for blocked hardware drivers[^13].

## Stream classification and intelligent media quality classifiers

The default CQD portal reports still classify streams as Good or Poor using legacy stream classification, while Teams call reporting is moving to the intelligent media quality classifiers, so the two systems can report different quality results[^15].

The CQD audio classifier marks a stream Poor when Packet Utilization exceeds 500 packets and any of these holds: average round trip over 500 ms, average packet loss rate over 0.1, or average jitter over 30 ms[^2]. Microsoft states that an audio stream marked Poor by the network-threshold classifier was not necessarily poor quality or perceived as poor by the user, because the Teams media stack can mitigate network degradation beyond those thresholds[^1]. For video streams with Packet Utilization over 500 packets, CQD checks the first available metric in order: local frame loss percentage over 50%, then frame rate average under 7, then post-FEC packet loss rate over 0.15; if none is available the stream is Unclassified[^58].

CQD marks a stream Unclassified when ICE connectivity failed (First or Second Connectivity Ice is FAILED) or when the metrics needed to classify it were not reported: no QoE report was received, the call was short, or packet utilization was low[^57]. The CQD 'QoE Record Available' dimension is True if a QoE report was received from either endpoint, and QoE reports from both endpoints are needed for the most accurate metrics[^48].

Intelligent media quality classifiers use percentile-based thresholding that flags the lowest-performing 2% of endpoints within a given platform, region and media type as having a poor call experience[^38]. These classifiers apply to inbound streams only when the user received at least 60 seconds of media, and to outbound streams only when the user sent at least 60 seconds[^37]. Modality and network classifiers cover all platforms and media modalities; compute device classifiers exclude Teams Web, optimized VDI and CVI; input device classifiers cover audio only on native platforms, excluding WebRTC-based ones[^40]. Microsoft lists August 4, 2026 as the latest intelligent media quality classifier model update and March 8, 2025 as the previous one, and says retraining is not retroactive to streams already classified[^39].

## Building data files

A CQD building data file must be a.tsv or.csv file with no header row, and every row must have exactly 16 columns in a fixed order: NetworkIP, NetworkName, NetworkRange, BuildingName, InsideCorp and ExpressRoute are required, and VPN and PublicIP are optional[^4]. Processing an uploaded building file can take up to 4 hours[^5]. A building data file has a limit of 1,000,000 expanded rows, and setting VPN to 1 fully expands the subnet toward that limit and slows building-data queries[^6].

Each uploaded building or endpoint file has a start date and an optional end date and applies only to calls within that window; multiple files can cover different periods but cannot be combined for the same period[^3]. Building files support supernetting only for masks from 8 to 28 bits; Microsoft supports supernetting but does not recommend it because it reduces reporting detail[^7].

The First/Second VPN dimensions in QoE data depend on VPN vendors registering their adapter as a Remote Access adapter, which not all do; Microsoft recommends marking VPN subnets with the VPN column in the building file instead[^59]. The CQD Missing Subnet Report lists subnets with 10 or more audio streams that are not defined in the building file, excluding common home subnets, and it needs a Second Tenant ID filter to exclude federated subnets[^41].

## Power BI integration

The Microsoft Call Quality connector for Power BI supports only DirectQuery, not Import mode, and every query must include at least 1 measure[^43]. CQD queries through the Power BI connector return at most 10,000 rows, a limit set on the API side, and Microsoft advises drilling down from low-cardinality dimensions instead of trying to raise it[^42]. GCC, GCC-High and DoD customers need an on-premises data gateway to use the Microsoft Call Quality connector with the Power BI service; without one they can use it only in Power BI Desktop[^44].

## Teams admin center troubleshooting

Microsoft's per-user Call Analytics article describes an earlier troubleshooting experience in Teams admin center, now replaced by the Monitor and troubleshoot Teams meetings and calls experience[^9]. In per-user Call Analytics the last 4 digits of caller and recipient phone numbers are obfuscated for every communications support role, and this cannot be changed or disabled[^8].

In the Teams admin center meeting and call troubleshooting experience, aggregated telemetry is available for all users for 30 days after a meeting ends, whatever their license[^50]. Telemetry for a completed meeting or call can take 30 minutes to 2 hours to process after the meeting ends[^54]. This current troubleshooting experience no longer labels meeting and call quality Good or Poor; after telemetry is processed it reports quality and reliability issues found by the intelligent media classifiers, with root-cause areas Network, Compute, Device and Media[^53]. Partner admins using GDAP must hold the Teams Communications Support Specialist or Teams Communications Support Engineer role in the customer tenant to use the Teams admin center meeting and call troubleshooting experience[^52]. Microsoft lists the Teams admin center meeting and call troubleshooting experience as available in Worldwide (Public) and GCC[^51].

## Microsoft Graph APIs and PSTN reports

In Graph a callRecord contains 1 or more sessions, each session contains 1 or more segments (media links between 2 endpoints), and each segment contains 1 or more media streams; a peer-to-peer call has 1 session, and in a group call each session connects a participant to a service endpoint[^36]. A Microsoft Graph callRecord is created after a call or meeting ends and stays available for 30 days; requests for older records return 404 Not Found[^31]. The CallRecords Graph API might not contain all of the fields available in CQD, and field naming can differ between the two[^32].

Getting a callRecord or calling getPstnCalls requires the application permission CallRecords.Read.All; delegated permissions are not supported[^30]. The Graph Get callRecord and getPstnCalls APIs are available in the global service, US Government L4 and US Government L5 (DOD), but not in China operated by 21Vianet[^33].

Graph pstnCallLogRow and directRoutingLogRow cover only the PSTN part of a call, and a log row's ID cannot be used to fetch a callRecord[^35]. getPstnCalls accepts a fromDateTime and toDateTime range of no more than 90 days, based on call start time, and returns an @odata.nextLink when more than 1,000 entries fall in the range[^34]. Calls on Telstra calling plans do not appear in the Teams PSTN usage report or in the Graph getPstnCalls API[^56].

The Teams PSTN usage report usually lags activity by 24 to 48 hours[^46]. PSTN usage detail records are kept for 365 days for Calling Plans and 150 days for Direct Routing by default, with country-specific periods such as 730 days in Italy and Mexico and 450 days in the United Kingdom, based on the user's country[^47]. The Direct Routing tab of the PSTN usage report shows, per call, the SBC FQDN, media bypass, Azure regions for media and signaling, final SIP code, final Microsoft subcode and SIP phrase, and links to a SIP call flow view[^29]. The PSTN and Direct Routing reports obfuscate the last 3 or 4 digits of external phone numbers for organizations in listed European countries such as Germany, France and Switzerland, show full numbers elsewhere, and note that CQD and Call Analytics may use different obfuscation rules[^45].

## See also

See also [Microsoft Teams Phone architecture and licensing](https://warmtransfer.net/knowledge/teams-phone-architecture).
See also [Call quality metrics and MOS estimation](https://warmtransfer.net/knowledge/call-quality-metrics).
See also [SIP trace capture and ladder analysis](https://warmtransfer.net/knowledge/sip-trace-analysis).

## Applicability

Applies to: Microsoft Teams Phone, Microsoft Teams Call Quality Dashboard, Microsoft Teams admin center, Microsoft Call Quality connector for Power BI, Microsoft Teams admin center per-user Call Analytics, Microsoft Teams admin center meeting, Microsoft Graph call records API v1.0, Microsoft Teams admin center PSTN usage report, and Microsoft Teams admin center Real-Time Analytics. Deployments: cloud, hybrid, and multi-tenant. Sources checked 2026-09-24. The legacy Call Analytics experience covered earlier per-user troubleshooting, which has been replaced by the Monitor and troubleshoot Teams meetings and calls experience[^9]. Using CQD with Skype for Business Server applies to Skype for Business Server 2019[^26]. Teams admin center meeting and call troubleshooting is available in Worldwide (Public) and GCC regions[^51]. For Graph call records and PSTN APIs, deployment is available in global service, US Government L4 and US Government L5 (DOD), but excluded in China operated by 21Vianet[^33]. Telstra calling plans in Australia are excluded from Teams PSTN usage reports and Graph getPstnCalls[^56].

## What remains uncertain

Sources disagree on real-time meeting telemetry retention: the legacy Call Analytics article states Real-Time Analytics covers scheduled meetings in progress and for 72 hours after ending[^49], whereas the current Teams admin center troubleshooting documentation states real-time telemetry is kept for 7 days post-meeting for Teams Premium or Teams Rooms Pro licensees and only for meeting duration for other users[^55]. Whether specific fields between CQD and Microsoft Graph call records map 1-to-1 beyond the documented differences in field naming and availability is not covered by the sources below.

## Sources

[^1]: Microsoft states that an audio stream marked Poor by the network-threshold classifier was not necessarily poor quality or perceived as poor by the user, because the Teams media stack can mitigate network degradation beyond those thresholds. Source: [Stream classification in Call Quality Dashboard (CQD)](https://learn.microsoft.com/en-us/MicrosoftTeams/stream-classification-in-call-quality-dashboard), Classifier Definitions > Audio Classifier > Note callout. Checked 2026-09-24.
[^2]: The CQD audio classifier marks a stream Poor when Packet Utilization exceeds 500 packets and any of these holds: average round trip over 500 ms, average packet loss rate over 0.1, or average jitter over 30 ms. Source: [Stream classification in Call Quality Dashboard (CQD)](https://learn.microsoft.com/en-us/MicrosoftTeams/stream-classification-in-call-quality-dashboard), Classifier Definitions > Audio Classifier > table. Checked 2026-09-24.
[^3]: Each uploaded building or endpoint file has a start date and an optional end date and applies only to calls within that window; multiple files can cover different periods but cannot be combined for the same period. Source: [Upload building and endpoint data](https://learn.microsoft.com/en-us/microsoftteams/cqd-upload-tenant-building-data), Upload building and endpoint files > step 3; Updating a building file > Important. Checked 2026-09-24.
[^4]: A CQD building data file must be a .tsv or .csv file with no header row, and every row must have exactly 16 columns in a fixed order: NetworkIP, NetworkName, NetworkRange, BuildingName, InsideCorp and ExpressRoute are required, and VPN and PublicIP are optional. Source: [Upload building and endpoint data](https://learn.microsoft.com/en-us/microsoftteams/cqd-upload-tenant-building-data), Building data file > validation criteria list; Building data file format table. Checked 2026-09-24.
[^5]: Processing an uploaded building file can take up to four hours. Source: [Upload building and endpoint data](https://learn.microsoft.com/en-us/microsoftteams/cqd-upload-tenant-building-data), Upload building and endpoint files > Note. Checked 2026-09-24.
[^6]: A building data file has a limit of 1,000,000 expanded rows, and setting VPN to 1 fully expands the subnet toward that limit and slows building-data queries. Source: [Upload building and endpoint data](https://learn.microsoft.com/en-us/microsoftteams/cqd-upload-tenant-building-data), Building data file > validation criteria; paragraph on the VPN column. Checked 2026-09-24.
[^7]: Building files support supernetting only for masks from 8 to 28 bits; Microsoft supports supernetting but does not recommend it because it reduces reporting detail. Source: [Upload building and endpoint data](https://learn.microsoft.com/en-us/microsoftteams/cqd-upload-tenant-building-data), Building data file > Supernetting. Checked 2026-09-24.
[^8]: In per-user Call Analytics the last four digits of caller and recipient phone numbers are obfuscated for every communications support role, and this cannot be changed or disabled. Source: [Use Call Analytics to troubleshoot poor call quality](https://learn.microsoft.com/en-us/microsoftteams/use-call-analytics-to-troubleshoot-poor-call-quality), What does each Teams Support role do? > paragraph before table and table rows 'Caller phone number' and 'Recipient phone number'. Checked 2026-09-24.
[^9]: Microsoft's per-user Call Analytics article describes an earlier troubleshooting experience in Teams admin center, now replaced by the Monitor and troubleshoot Teams meetings and calls experience. Source: [Use Call Analytics to troubleshoot poor call quality](https://learn.microsoft.com/en-us/microsoftteams/use-call-analytics-to-troubleshoot-poor-call-quality), opening Note. Checked 2026-09-24.
[^10]: Only Global Administrator, Teams Administrator, Teams Communications Administrator and Skype for Business Administrator can upload building data for CQD; support engineer, support specialist, Global Reader and Reports Reader cannot. Source: [Call Quality Dashboard (CQD) setup](https://learn.microsoft.com/en-us/microsoftteams/turning-on-and-using-call-quality-dashboard), Assign admin roles for access to CQD > role table column 'Upload building data'. Checked 2026-09-24.
[^11]: In August 2026 Microsoft changed the CQD First/Second UPN and First/Second Object Id logic to reflect users associated with Teams Phone Mobile numbers in PSTN calls. Source: [What is Call Quality Dashboard (CQD)?](https://learn.microsoft.com/en-us/microsoftteams/cqd-what-is-call-quality-dashboard), What's New > August 2026. Checked 2026-09-24.
[^12]: In February 2026 CQD changed Meeting Id to match the numeric Meeting Id in Teams meeting invites and added a Thread Id column carrying the value Meeting Id used to hold. Source: [What is Call Quality Dashboard (CQD)?](https://learn.microsoft.com/en-us/microsoftteams/cqd-what-is-call-quality-dashboard), What's New > February 2026. Checked 2026-09-24.
[^13]: In January 2026 CQD added First/Second Is Call Throttled columns for device CPU throttling and First/Second HW Encoder Blocked and HW Decoder Blocked columns for blocked hardware drivers. Source: [What is Call Quality Dashboard (CQD)?](https://learn.microsoft.com/en-us/microsoftteams/cqd-what-is-call-quality-dashboard), What's New > January 2026. Checked 2026-09-24.
[^14]: In July 2026 CQD added First/Second Public IP columns that reflect the Public IP values in the active building file, and building metadata began supporting Public IP values. Source: [What is Call Quality Dashboard (CQD)?](https://learn.microsoft.com/en-us/microsoftteams/cqd-what-is-call-quality-dashboard), What's New > July 2026. Checked 2026-09-24.
[^15]: The default CQD portal reports still classify streams as Good or Poor using legacy stream classification, while Teams call reporting is moving to the intelligent media quality classifiers, so the two systems can report different quality results. Source: [Data and reports in Call Quality Dashboard (CQD)](https://learn.microsoft.com/en-us/microsoftteams/cqd-data-and-reports), Summary Reports > Overall Call Quality tab > Note callout. Checked 2026-09-24.
[^16]: Microsoft names four ways to reach call quality data: the CQD portal, CQD in Power BI, the Users page in Teams admin center (not customizable), and the Microsoft Graph call records API. Source: [Data and reports in Call Quality Dashboard (CQD)](https://learn.microsoft.com/en-us/microsoftteams/cqd-data-and-reports), Many ways to access call quality data > table. Checked 2026-09-24.
[^17]: CQD keeps end-user identifiable information (EUII) for only 28 days; after that the EUII fields are cleared and the remaining data is EUII-free. Source: [Data and reports in Call Quality Dashboard (CQD)](https://learn.microsoft.com/en-us/microsoftteams/cqd-data-and-reports), EUII data > paragraph after the location-sharing caution. Checked 2026-09-24.
[^18]: CQD fields treated as EUII include IP address, user ObjectId, MAC address, phone number, UPN, feedback text, client endpoint name, BSSID, local and remote site, and auto attendant and call queue identity. Source: [Data and reports in Call Quality Dashboard (CQD)](https://learn.microsoft.com/en-us/microsoftteams/cqd-data-and-reports), EUII data > bulleted list 'Fields that contain EUII data are'. Checked 2026-09-24.
[^19]: Among CQD access roles, Reports Reader and Teams Communications Support Specialist can view CQD reports but cannot see EUII fields, while Teams Communications Support Engineer and Global Reader can see EUII. Source: [Call Quality Dashboard (CQD) setup](https://learn.microsoft.com/en-us/microsoftteams/turning-on-and-using-call-quality-dashboard), Assign admin roles for access to CQD > role table columns 'View reports' and 'View EUII fields'. Checked 2026-09-24.
[^20]: Since April 2026 CQD First/Second Feedback Rating is 0 when a Rate My Call survey was offered but the user did not submit it or submitted it without a rating. Source: [What is Call Quality Dashboard (CQD)?](https://learn.microsoft.com/en-us/microsoftteams/cqd-what-is-call-quality-dashboard), What's New > April 2026. Checked 2026-09-24.
[^21]: CQD marks an endpoint Inside only if its subnet appears as InsideCorp in uploaded building information; without building data, every stream is classified Outside. Source: [Data and reports in Call Quality Dashboard (CQD)](https://learn.microsoft.com/en-us/microsoftteams/cqd-data-and-reports), Summary Reports > Server-Client tab and Client-Client tabs > Inside versus Outside. Checked 2026-09-24.
[^22]: CQD does not currently support delegated administration for Microsoft Partners. Source: [Call Quality Dashboard (CQD) setup](https://learn.microsoft.com/en-us/microsoftteams/turning-on-and-using-call-quality-dashboard), Limitations > first bullet. Checked 2026-09-24.
[^23]: CQD calculates Poor % as Poor streams divided by (Poor plus Good streams) times 100, so Unclassified streams do not affect it. Source: [Data and reports in Call Quality Dashboard (CQD)](https://learn.microsoft.com/en-us/microsoftteams/cqd-data-and-reports), Summary Reports > Overall Call Quality tab > second paragraph. Checked 2026-09-24.
[^24]: Microsoft's current CQD overview and setup pages give the CQD portal address as https://cqd.teams.cloud.microsoft, also reachable from Teams admin center under Analytics & reports > Call Quality Dashboard. Source: [Call Quality Dashboard (CQD) setup](https://learn.microsoft.com/en-us/microsoftteams/turning-on-and-using-call-quality-dashboard), Call Quality Dashboard (CQD) setup > first paragraph. Checked 2026-09-24.
[^25]: CQD call records remain in CQD for 12 months, and both summary and detailed reports cover the last 12 months of data. Source: [Data and reports in Call Quality Dashboard (CQD)](https://learn.microsoft.com/en-us/microsoftteams/cqd-data-and-reports), opening paragraph; Data available in CQD reports > table row 'Amount of data available'. Checked 2026-09-24.
[^26]: Using CQD with Skype for Business Server 2019 requires configuring Call Data Connector. Source: [Call Quality Dashboard (CQD) setup](https://learn.microsoft.com/en-us/microsoftteams/turning-on-and-using-call-quality-dashboard), Call Quality Dashboard (CQD) setup > Important callout. Checked 2026-09-24.
[^27]: CQD summary reports have four tabs: Overall Call Quality, Server-Client, Client-Client, and Voice Quality SLA. Source: [Data and reports in Call Quality Dashboard (CQD)](https://learn.microsoft.com/en-us/microsoftteams/cqd-data-and-reports), Summary Reports > tab table. Checked 2026-09-24.
[^28]: CQD classifies a stream as WiFi if either of its two endpoints is connected to a WiFi network; server endpoints always count as wired. Source: [Data and reports in Call Quality Dashboard (CQD)](https://learn.microsoft.com/en-us/microsoftteams/cqd-data-and-reports), Summary Reports > Server-Client tab and Client-Client tabs > Wired versus WiFi. Checked 2026-09-24.
[^29]: The Direct Routing tab of the PSTN usage report shows, per call, the SBC FQDN, media bypass, Azure regions for media and signaling, final SIP code, final Microsoft subcode and SIP phrase, and links to a SIP call flow view. Source: [Microsoft Teams PSTN usage report](https://learn.microsoft.com/en-us/microsoftteams/teams-analytics-and-reports/pstn-usage-report), Interpret the report > Direct Routing callouts 4 and 5. Checked 2026-09-24.
[^30]: Getting a callRecord or calling getPstnCalls requires the application permission CallRecords.Read.All; delegated permissions are not supported. Source: [Get callRecord](https://learn.microsoft.com/en-us/graph/api/callrecords-callrecord-get), Permissions table. Checked 2026-09-24.
[^31]: A Microsoft Graph callRecord is created after a call or meeting ends and stays available for 30 days; requests for older records return 404 Not Found. Source: [Get callRecord](https://learn.microsoft.com/en-us/graph/api/callrecords-callrecord-get), Warning callout; Response section. Checked 2026-09-24.
[^32]: The CallRecords Graph API might not contain all of the fields available in CQD, and field naming can differ between the two. Source: [Data and reports in Call Quality Dashboard (CQD)](https://learn.microsoft.com/en-us/microsoftteams/cqd-data-and-reports), Many ways to access call quality data > table row 'Graph API'. Checked 2026-09-24.
[^33]: The Graph Get callRecord and getPstnCalls APIs are available in the global service, US Government L4 and US Government L5 (DOD), but not in China operated by 21Vianet. Source: [Get callRecord](https://learn.microsoft.com/en-us/graph/api/callrecords-callrecord-get), national cloud deployments table. Checked 2026-09-24.
[^34]: getPstnCalls accepts a fromDateTime and toDateTime range of no more than 90 days, based on call start time, and returns an @odata.nextLink when more than 1,000 entries fall in the range. Source: [callRecord: getPstnCalls](https://learn.microsoft.com/en-us/graph/api/callrecords-callrecord-getpstncalls), Function parameters > Important; Response. Checked 2026-09-24.
[^35]: Graph pstnCallLogRow and directRoutingLogRow cover only the PSTN part of a call, and a log row's ID cannot be used to fetch a callRecord. Source: [Working with the call records API in Microsoft Graph](https://learn.microsoft.com/en-us/graph/api/resources/callrecords-api-overview), PSTN and direct routing logs. Checked 2026-09-24.
[^36]: In Graph a callRecord contains one or more sessions, each session contains one or more segments (media links between two endpoints), and each segment contains one or more media streams; a peer-to-peer call has one session, and in a group call each session connects a participant to a service endpoint. Source: [Working with the call records API in Microsoft Graph](https://learn.microsoft.com/en-us/graph/api/resources/callrecords-api-overview), Call record structure. Checked 2026-09-24.
[^37]: Intelligent media quality classifiers apply to inbound streams only when the user received at least 60 seconds of media, and to outbound streams only when the user sent at least 60 seconds. Source: [Intelligent media quality classifiers in CQD](https://learn.microsoft.com/en-us/microsoftteams/cqd-intelligent-media-quality-classifiers), When to use intelligent media quality classifiers. Checked 2026-09-24.
[^38]: Intelligent media quality classifiers use percentile-based thresholding that flags the lowest-performing 2% of endpoints within a given platform, region and media type as having a poor call experience. Source: [Intelligent media quality classifiers in CQD](https://learn.microsoft.com/en-us/microsoftteams/cqd-intelligent-media-quality-classifiers), Interpreting intelligent media quality classifiers > second paragraph. Checked 2026-09-24.
[^39]: Microsoft lists August 4, 2026 as the latest intelligent media quality classifier model update and March 8, 2025 as the previous one, and says retraining is not retroactive to streams already classified. Source: [Intelligent media quality classifiers in CQD](https://learn.microsoft.com/en-us/microsoftteams/cqd-intelligent-media-quality-classifiers), Maintenance of classification models. Checked 2026-09-24.
[^40]: Intelligent media modality and network classifiers cover all platforms and media modalities; compute device classifiers exclude Teams Web, optimized VDI and CVI; input device classifiers cover audio only on native platforms, excluding WebRTC-based ones. Source: [Intelligent media quality classifiers in CQD](https://learn.microsoft.com/en-us/microsoftteams/cqd-intelligent-media-quality-classifiers), Supported platforms and media types. Checked 2026-09-24.
[^41]: The CQD Missing Subnet Report lists subnets with 10 or more audio streams that are not defined in the building file, excluding common home subnets, and it needs a Second Tenant ID filter to exclude federated subnets. Source: [Upload building and endpoint data](https://learn.microsoft.com/en-us/microsoftteams/cqd-upload-tenant-building-data), Locate missing subnets. Checked 2026-09-24.
[^42]: CQD queries through the Power BI connector return at most 10,000 rows, a limit set on the API side, and Microsoft advises drilling down from low-cardinality dimensions instead of trying to raise it. Source: [Install Power BI Connector to use CQD query templates](https://learn.microsoft.com/en-us/microsoftteams/cqd-power-bi-connector), Frequently asked questions > 10,000-row limit question. Checked 2026-09-24.
[^43]: The Microsoft Call Quality connector for Power BI supports only DirectQuery, not Import mode, and every query must include at least one measure. Source: [Install Power BI Connector to use CQD query templates](https://learn.microsoft.com/en-us/microsoftteams/cqd-power-bi-connector), opening Note; Building Queries > step 2 Important. Checked 2026-09-24.
[^44]: GCC, GCC-High and DoD customers need an on-premises data gateway to use the Microsoft Call Quality connector with the Power BI service; without one they can use it only in Power BI Desktop. Source: [Install Power BI Connector to use CQD query templates](https://learn.microsoft.com/en-us/microsoftteams/cqd-power-bi-connector), Installation > paragraph on Government cloud; Limitations > item 7. Checked 2026-09-24.
[^45]: The PSTN and Direct Routing reports obfuscate the last three or four digits of external phone numbers for organizations in listed European countries such as Germany, France and Switzerland, show full numbers elsewhere, and note that CQD and Call Analytics may use different obfuscation rules. Source: [Microsoft Teams PSTN usage report](https://learn.microsoft.com/en-us/microsoftteams/teams-analytics-and-reports/pstn-usage-report), Direct Routing > Phone number obfuscation. Checked 2026-09-24.
[^46]: The Teams PSTN usage report usually lags activity by 24 to 48 hours. Source: [Microsoft Teams PSTN usage report](https://learn.microsoft.com/en-us/microsoftteams/teams-analytics-and-reports/pstn-usage-report), Interpret the report > Calling Plans callout 2; Direct Routing callout 2. Checked 2026-09-24.
[^47]: PSTN usage detail records are kept for 365 days for Calling Plans and 150 days for Direct Routing by default, with country-specific periods such as 730 days in Italy and Mexico and 450 days in the United Kingdom, based on the user's country. Source: [Microsoft Teams PSTN usage report](https://learn.microsoft.com/en-us/microsoftteams/teams-analytics-and-reports/pstn-usage-report), Direct Routing > Data retention table. Checked 2026-09-24.
[^48]: The CQD 'QoE Record Available' dimension is True if a QoE report was received from either endpoint, and QoE reports from both endpoints are needed for the most accurate metrics. Source: [Stream classification in Call Quality Dashboard (CQD)](https://learn.microsoft.com/en-us/MicrosoftTeams/stream-classification-in-call-quality-dashboard), Unclassified Streams > 'QoE reports weren't received' > Tip. Checked 2026-09-24.
[^49]: The legacy Call Analytics article says Real-Time Analytics let admins troubleshoot scheduled meetings in progress and for 72 hours after the meeting ends (disputed). Source: [Use Call Analytics to troubleshoot poor call quality](https://learn.microsoft.com/en-us/microsoftteams/use-call-analytics-to-troubleshoot-poor-call-quality), Introduction to Call Analytics > third paragraph. Checked 2026-09-24.
[^50]: In the Teams admin center meeting and call troubleshooting experience, aggregated telemetry is available for all users for 30 days after a meeting ends, whatever their license. Source: [Monitor and troubleshoot Teams meetings and calls from the Teams admin center](https://learn.microsoft.com/en-us/microsoftteams/monitor-troubleshoot-teams-meetings-calls), Session-level telemetry > Note; Completed meetings > Note and export steps. Checked 2026-09-24.
[^51]: Microsoft lists the Teams admin center meeting and call troubleshooting experience as available in Worldwide (Public) and GCC. Source: [Monitor and troubleshoot Teams meetings and calls from the Teams admin center](https://learn.microsoft.com/en-us/microsoftteams/monitor-troubleshoot-teams-meetings-calls), opening 'Available in' line. Checked 2026-09-24.
[^52]: Partner admins using GDAP must hold the Teams Communications Support Specialist or Teams Communications Support Engineer role in the customer tenant to use the Teams admin center meeting and call troubleshooting experience. Source: [Monitor and troubleshoot Teams meetings and calls from the Teams admin center](https://learn.microsoft.com/en-us/microsoftteams/monitor-troubleshoot-teams-meetings-calls), Prerequisites > third bullet. Checked 2026-09-24.
[^53]: The current Teams admin center troubleshooting experience no longer labels meeting and call quality Good or Poor; after telemetry is processed it reports quality and reliability issues found by the intelligent media classifiers, with root-cause areas Network, Compute, Device and Media. Source: [Monitor and troubleshoot Teams meetings and calls from the Teams admin center](https://learn.microsoft.com/en-us/microsoftteams/monitor-troubleshoot-teams-meetings-calls), Completed meetings > Important 'What's changed'; Investigate a meeting > Issues > Root cause areas. Checked 2026-09-24.
[^54]: In the Teams admin center troubleshooting experience, telemetry for a completed meeting or call can take 30 minutes to 2 hours to process after the meeting ends. Source: [Monitor and troubleshoot Teams meetings and calls from the Teams admin center](https://learn.microsoft.com/en-us/microsoftteams/monitor-troubleshoot-teams-meetings-calls), Find a meeting you want to troubleshoot > Completed meetings > first paragraph. Checked 2026-09-24.
[^55]: The current Teams admin center troubleshooting page says real-time telemetry is kept for seven days after a meeting for users with Teams Premium or Teams Rooms Pro licenses and only for the duration of the meeting for everyone else (disputed). Source: [Monitor and troubleshoot Teams meetings and calls from the Teams admin center](https://learn.microsoft.com/en-us/microsoftteams/monitor-troubleshoot-teams-meetings-calls), Investigate the meeting quality of a specific participant > Session-level telemetry > Note. Checked 2026-09-24.
[^56]: Calls on Telstra calling plans do not appear in the Teams PSTN usage report or in the Graph getPstnCalls API. Source: [Microsoft Teams PSTN usage report](https://learn.microsoft.com/en-us/microsoftteams/teams-analytics-and-reports/pstn-usage-report), opening Note. Checked 2026-09-24.
[^57]: CQD marks a stream Unclassified when ICE connectivity failed (First or Second Connectivity Ice is FAILED) or when the metrics needed to classify it were not reported: no QoE report was received, the call was short, or packet utilization was low. Source: [Stream classification in Call Quality Dashboard (CQD)](https://learn.microsoft.com/en-us/MicrosoftTeams/stream-classification-in-call-quality-dashboard), Unclassified Streams. Checked 2026-09-24.
[^58]: For video streams with Packet Utilization over 500 packets, CQD checks the first available metric in order: local frame loss percentage over 50%, then frame rate average under 7, then post-FEC packet loss rate over 0.15; if none is available the stream is Unclassified. Source: [Stream classification in Call Quality Dashboard (CQD)](https://learn.microsoft.com/en-us/MicrosoftTeams/stream-classification-in-call-quality-dashboard), Classifier Definitions > Video Classifier > table. Checked 2026-09-24.
[^59]: The First/Second VPN dimensions in QoE data depend on VPN vendors registering their adapter as a Remote Access adapter, which not all do; Microsoft recommends marking VPN subnets with the VPN column in the building file instead. Source: [Upload building and endpoint data](https://learn.microsoft.com/en-us/microsoftteams/cqd-upload-tenant-building-data), Building data file > VPN. Checked 2026-09-24.
[^60]: Microsoft describes Call Quality Dashboard as an organization-wide trend view and Teams admin center as a per-user call and meeting troubleshooting view. Source: [Prepare your organization's network for Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/prepare-network), Best practice: Monitor your network by using CQD and Teams admin center. Checked 2026-09-06.