Answered

Cannot connect to Azure DevOps through flow

(1) Share

Report

Posted on by Macauley_scull

Hello, I'm having trouble connecting to Azure DevOps, I'm using the template to notify me when a new work item is created though it comes up with authenticating errors when I try to connect: "Failed with error: 'OAuth2 authorization flow failed for service 'Visual Studio Online'. OAuth 2 sign in failed to exchange code for access token. Client ID and secret sent in form body.. Response status code=InternalServerError. Response body: {"$id":"1","innerException":null,"message":"TF400898: An Internal Error Occurred. Activity Id: 06d3ac0c-0fc1-4919-959b-fb80022a1811.","typeName":"Microsoft.VisualStudio.Services.Common.VssServiceException, Microsoft.VisualStudio.Services.Common","typeKey":"VssServiceException","errorCode":0,"eventId":3000} Client ID and secret sent in Basic authorization header.. Response status code=InternalServerError. Response body: {"$id":"1","innerException":null,"message":"TF400898: An Internal Error Occurred. Activity Id: d6b5ed98-bb8c-4878-a26d-4f6b3c21f4a3.","typeName":"Microsoft.VisualStudio.Services.Common.VssServiceException, Microsoft.VisualStudio.Services.Common","typeKey":"VssServiceException","errorCode":0,"eventId":3000} '. Please sign in again." An authenticating window pops up, I filled out the first part where I agree to flow connecting and then the window closed and produced this error, It will not let me sign in at all.

Categories:

Using connectors

I have the same question (0)

All responses (2)

Answers (1)

daveaglick 3 on at

Like (0)

Report
Copy link

Link copied!

I'm having the exact same problem (same error code and everything). I have a scheduled flow that uses a DevOps connector and it's been working fine for months. Some time last night it stopped connecting to DevOps and now I can't seem to get Flow to talk to DevOps at all. My existing DevOps connectors won't "fix" (in fact the "Fix connection" link opens and popup and then promptly closes it...without fixing anything). I also can't edit them to change the associated account. Nor can I create new DevOps connectors to replace the one that's broken. Looks like the OAuth handshake between Flow and DevOps is hosed.

Was this reply helpful? Yes No
Verified answer

v-bacao-msft Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!
Hi @Macauley_scull / @daveaglick ,

Please try doing the following things and see if they can improve the current situation:

Clear the browser's cache and delete Azure DevOps connection.

Recreate Azure DevOps connection and configure a similar Flow for testing.

Or open a new InPrivate/incognito window and configure a similar Flow.

Best Regards,

Was this reply helpful? Yes No