Azure Application Insight Work items authorization error

2
votes

My purpose is to create bug in Azure DevOps directly from Azure Application Insight, I am doing to attach the work item (bug) feature available in Azure Application Insight but on clicking Authorize button it give me following error

Authorization token provided through OAuth does not have access to read/write work items for requested uri/project collection/project

for reference please find the below image. enter image description here

Updates: I didnt understand what you meant by private browser, and I have full admin access over Azure Portal.

basically I have the https://dev.azure.com/HealthTechnologies/ReportItNow link in which

https://dev.azure.com is the devop url

HealthTechnologies is the organization

ReportItNow is the Project

so in Azure insight workitem section, URL I am putting https://dev.azure.com/HealthTechnologies/ and in project I am putting ReportItNow, I dont know what i am doing wrong.

Still waiting for this glitch to solve.

Oky let me make it more simple, if I want to automatically create bug in Azure DevOps when ever any new exception came in to the Azure Application Insight How I can get this into real practical.

1
azureazure-devopsazure-application-insightsworkitem
Try doing that in a private browser window to avoid effects from other accounts. And if that still persists, check if this helps. You may need to use old format for this. - LoLance
What's the result if you enter URL https://HealthTechnologies.visualstudio.com, it's old format of https://dev.azure.com. It looks one issue with Azure Application Insight but I can't reproduce it in my side, see if this makes some help. And the private window I mean edge's New InPrivate Window and Chrome's new incognito window. It's private mode of browser. - LoLance
I have tried HealthTechnologies.visualstudio.com in URL field and in chrome incognito mode but same result :( - Saad Awan
@LanceLi-MSFT I have tired your suggestion but same result, please guild where is the mistake? - Saad Awan
Any1 know from where I am doing mistake or is this the glitch from azure - Saad Awan

1 Answers

0
votes

I solve this when I took a detailed look at the error message url. It's saying that the missing authorization is for https://uri/Project Collection/Project. Based on that, I changed my url from https://dev.azure.com/organization to https://dev.azure.com/ and it worked,