CQD API - MS Teams question

%3CLINGO-SUB%20id%3D%22lingo-sub-339525%22%20slang%3D%22en-US%22%3ECQD%20API%20-%20MS%20Teams%20question%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-339525%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20we%20use%20Powershell%20to%20access%20CQD%20Data%20for%20MS%20Teams%2C%20a%20pop%20up%20window%20is%20shown%20for%20credentials.%3CBR%20%2F%3EWhile%20working%20with%20CQD%20Powershell%2C%20we%20see%20that%20all%20calls%20are%20HTTP%20REST%20APi%20calls%20(everything%20works).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20programming%20in%20JAVA%20and%20we%20use%20the%20following%20method%20to%20authenticate%3A%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fdevelop%2Fv2-oauth-ropc%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fdevelop%2Fv2-oauth-ropc%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20get%20a%20valid%20JWT%20token%20but%20unfortunately%20we%20are%20unable%20to%20access%20the%20data%20(status%20401).%3CBR%20%2F%3EThe%20only%20difference%20between%20the%20two%20tokens%20one%20through%20PowerShell%20and%20our%20implementation%20is%20in%20the%20scope.%20Access%20token%20retrieved%20via%20PowerShell%20has%20scope%3A%20user_impersonation%20whereas%20the%20token%20received%20via%20grant_type%20password%20(see%20link%20above)%20has%20scope%3A%20CQD_DATA_API%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20any%20documentation%20available%20which%20can%20point%20us%20to%20the%20right%20direction%26nbsp%3B%20%3F%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3CP%3Estefan%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-339525%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-339566%22%20slang%3D%22en-US%22%3ERe%3A%20CQD%20API%20-%20MS%20Teams%20question%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-339566%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Stefan%2C%20please%20feel%20free%20to%20submit%20your%20issue%20to%20our%20developer%20alias%20here%3A%26nbsp%3Bmicrosoftteamsdev%40microsoft.com%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1192904%22%20slang%3D%22en-US%22%3ERe%3A%20CQD%20API%20-%20MS%20Teams%20question%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1192904%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F44882%22%20target%3D%22_blank%22%3E%40Stefan%20Fried%3C%2FA%3EHi%2C%20Did%20you%20by%20any%20chance%20solve%20this%3F%20We%20are%20having%20the%20same%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1193337%22%20slang%3D%22en-US%22%3ERe%3A%20CQD%20API%20-%20MS%20Teams%20question%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1193337%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F322639%22%20target%3D%22_blank%22%3E%40Schillman88%3C%2FA%3E%20nope%20%3A(%3C%2Fimg%3E%3CBR%20%2F%3EBut%20a%20lot%20has%20been%20changed%20in%20CQD%20within%20the%20last%202-3%20months.%3CBR%20%2F%3E...powerbi%20connector%2C%20etc...%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fturning-on-and-using-call-quality-dashboard%23BKMKFeaturesOfTheCQD%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fturning-on-and-using-call-quality-dashboard%23BKMKFeaturesOfTheCQD%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EI've%20heard%20that%20MS%20is%20working%20on%20a%20MS%20graph%20api%20to%20provide%20access%20to%20CQD%20data%20in%20the%20future.%3CBR%20%2F%3E%3CBR%20%2F%3EHth%3CBR%20%2F%3EStedan%3C%2FLINGO-BODY%3E
Super Contributor

When we use Powershell to access CQD Data for MS Teams, a pop up window is shown for credentials.
While working with CQD Powershell, we see that all calls are HTTP REST APi calls (everything works).

 

We are programming in JAVA and we use the following method to authenticate:
https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-oauth-ropc

 

We get a valid JWT token but unfortunately we are unable to access the data (status 401).
The only difference between the two tokens one through PowerShell and our implementation is in the scope. Access token retrieved via PowerShell has scope: user_impersonation whereas the token received via grant_type password (see link above) has scope: CQD_DATA_API

 

Is there any documentation available which can point us to the right direction  ?

Thanks

stefan

3 Replies

Hi Stefan, please feel free to submit your issue to our developer alias here: microsoftteamsdev@microsoft.com

@Stefan FriedHi, Did you by any chance solve this? We are having the same issue.

@Schillman nope :(
But a lot has been changed in CQD within the last 2-3 months.
...powerbi connector, etc...
https://docs.microsoft.com/en-us/microsoftteams/turning-on-and-using-call-quality-dashboard#BKMKFeat...

I've heard that MS is working on a MS graph api to provide access to CQD data in the future.

Hth
Stedan