Export Teams Call Quality Dashboard to SQL server

Bronze Contributor


Does anybody knows how to export the CQD data to SQL server? I would like to take some statistics and keep them longer time than what Office 365 is offering by default.

9 Replies
@Petri X-Could you please elaborate your requirement and share the repro steps, so that we can try it from our end.


Basically, Teams keeps the current CDRs only 30 days available. If you want to create any kind of statistics which are older than that, e.g. see PSTN calls, Queue reports, from last months, you should have access to that data longer then 30 days (e.g. for 365 days).


So the idea behind this was, to export available data from O365 and import that into e.g. SQL database. And then having e.g. Power BI templates for users.


This also solves even the bigger issue, to be able to read those CDRs from O365 you need to have quite much access to it which we cannot give for regular users. Having separated SQL DB we could segmenting what end users are able to see from their own calls. And that they can do using their own credentials.


On the Power BI we are able to use "Microsoft Call Quality" as a source, so I though using similar method. I could perhaps setup a process for doing the same in automatically, and importing the data into SQL. But before that I thought to ask from here, if anybody else has already been working with this.

@Petri X -Did you get chance to check?


Yes I did, but I was not sure how that should help? CQD user interface still requires extra credentials for viewers, and CQD does not have past year details.

If I success to do using e.g. PS script which collects the same data what Power BI does, then I could import that into SQL. Then I would be a bit closer to goal :)


like your idea, hope you can find about a way
I leave the word here to let you know more people want this
even I don't know how to build this local database

Sorry to say @Sayali-MSFT, but that is still not help to reach the goal where I could do the same by scripting this.


But I believe the answer is, nobody has done this earlier :)


As far as I have seen, I should authenticate myself, and then send the query in JSON format. But obviously this requires more investigation :) 

This is actually one finding:

CQD PowerShell 2.0.1 

The problem is, that is pretty old already, so not sure if this is active scenario anymore, or is the CQD actually not developed anymore. But this is till pretty interesting.