Forum Discussion
Can't Configure Azure DevOps Connector in Teams (HTTP ERROR 500)
We are trying to configure the "Azure DevOps" connector in a Teams channel. It has already been added to the channel, so I go to the channel, click the three dots, and click "Connectors."
Then, I click the "Configure" button next to "Azure DevOps":
That then opens a window that says, "To add this connector, sign in to your Azure DevOps account", so I click the "Log in" button.
That then browses the login window to a screen that looks like this:
I click "Continue", and it takes me to a screen to login to my MS account, and I click on my MS account that is currently "Connected to Windows":
After clicking the account, it redirects a few times and ends up showing "https://outlook.office.com" in the window header and nothing but a blank, white screen below:
I've tried this process over and over again, and even had another coworker follow the same process, and none of us can get anything to appear in the window.
I went to the browser version of Teams and did the same process. There was one difference once I got to the blank, white screen bug, which was that the popup window showed a 500 error:
"This page isn’t working
outlook.office.com is currently unable to handle this request.
HTTP ERROR 500"
Anyone have any idea what's going on?
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 🙂
40 Replies
JohnMM I had this problem and I merely clicked "add a new Azure DevOps account" under where you select your account, authenticated again...and it worked for me. I think it just refreshes the token and kicks out a new one.
scottroot2 , this may be fixed now but we've strictly using `bots` that I mentioned in this thread.
Also, I'd like to take this moment to plug my related https://developercommunity.visualstudio.com/idea/1293356/azure-pipelines-ms-teams-bot.html. Please add a vote if you're using bots to manage your release pipeline in MS Teams!
I have the same issue - it was working until yesterday when I had to replace expired token. Then I wasn't able to configure the connector anymore.
Can anyone here point out the case id in order to make a reference when I raise a new support ticket?
VanioVanio I have the same issue. Yesterday it was not possible anymore to change a connector due to an invalid token. How did you replace it?
It's also not possible to add a new connector. I get the sign in screen, fill in all information but nothing happens.
- I'm having this exact issue but can use the Azure Pipelines BOT which at this point is a better approach to what I need.
See
https://docs.microsoft.com/en-us/azure/devops/pipelines/integrations/microsoft-teams?view=azure-devops
still having this issue .. unable to login.. i get all the way past the login but teams never gets past the login screen.
i also started to have issue, it was working last week until today when i try to configure the connector
JohnMM , the issue seems fixed by Microsoft team, now I can use Azure DevOps connectors.
Seems to have same problem... is there any known steps for resolution?
i am getting blank screen while trying TReam,s to Azure DevOps Connector
- Bro is it working normal for you if it's work please suggest me how you have done.
Anyone having still issues?
Failed to acquire an access token.{"Error":"invalid_request","ErrorDescription":"Client secret is expired."}
Babic122 et al,
I am in contact with MS support and they are looking into it. Will let you know how it develops.
For the time being I am using the Azure Repos and Azure Pipelines add-ons as a workaround.
I'm experiencing this at my organization, as well. I asked my manager to give it a try because he has administrative privileges across the tenant (whereas there are some gaps in my privileges), but he had the same result.
JohnMM Just noting that I am also experiencing this issue. Would love updates if anyone finds anything.
- The issue seems fixed by Microsoft team, now I can use Azure DevOps connectors
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.
I'm having the same issue as well. I'm getting a blank page upon logging in.
Mary Jane Cruz As many of you who can should get a message into Microsoft to let them know this is going on. I'm afraid that if Octavio_Vallejo is the only one who has submitted a support request on this, they won't think it's that big of a problem. Octavio can correct me, but I believe the way to submit a request is through: https://admin.microsoft.com/
JohnMM I have an open case on the exact same issue and will let you know if I get a fix of some sort. My Microsoft technician has got as far as it's to do with outlook and where it's hosted (on-prem seems to not play nicely). However, we have outlook online so it's being escalated as of now. I also used to get an error regarding the access token but since I removed the previous configuration I now can't configure it at all!
Here's to hoping... someone can help get this sorted!
lfhighaimer any traction on the support case?
Thankssheesh8080 Unfortunately, not much traction apart from collecting logs and still in escalation. I'll chase up again and inform the technician of this thread. Will post back with any updates as soon as I have any.
- lfhighaimer, great to know we're not the only ones experiencing this and that MS is aware! Thanks for the details. We use Office 365 here.
