Forum Discussion
Can't Configure Azure DevOps Connector in Teams (HTTP ERROR 500)
- Sep 14, 2020
JohnMMsheesh8080 Just got a call from MS to say they will be rolling out an update on the 17/18th of Sept! No indication of what the cause might be but hopefully we'll be able to get our ADO/Teams integration powers back this week 🙂
From 29 October 2020 again, I can't access DevOps Connector, when i tried that time get an error message `Failed to acquire an access token.{"Error":"invalid_request","ErrorDescription":"Client secret is expired."}`, After that i logged out and tried to login again, then I can't login. still today.
- navil2225Nov 14, 2020Brass ContributorJust piping in to say me too. i would really like this fixed.
Failed to acquire an access token.{"Error":"invalid_request","ErrorDescription":"Client secret is expired."} - VanioVanioNov 02, 2020Copper Contributor
The support ticket is "Resolved" but the issue is still present...hopeless...
I will keep using the workaround of Repos + Pipelines to replace the DevOps connector. So far these are working just fine.
- filetrail_dgrossmanNov 13, 2020Copper Contributor
I'm still getting the access token error. Anyone see any movement? Is this a not-so-subtle push for us to stop using the Azure DevOps Connector and move to the Boards and Pipeline bots, or something?