Login required when trying to manage connectors in a teams channel

Pavel Ronin 121 Reputation points
2021-11-23T15:54:24.027+00:00

I'm trying to get the connector URL for a channel in a team I'm owning.
But when trying to go to the channel->connectors->manage->configured I get
"Something went wrong.
Login required"

This is when I'm trying getting there through the web interface.
From the desktop app it just loads forever.

Has anybody else encountered it?
Does anybody know how to bypass it?

Microsoft Teams | Development
Microsoft Teams | Microsoft Teams for business | Other
{count} votes

6 answers

Sort by: Most helpful
  1. Vasil Michev 119.6K Reputation points MVP Volunteer Moderator
    2021-11-23T18:04:12.81+00:00

    There seems to be some ongoing issue with configuring connectors, as others have reported similar issues. Best open a support case and report this.

    4 people found this answer helpful.

  2. Ashish Dadhich 56 Reputation points
    2021-12-03T19:28:29.31+00:00

    Same issue :(

    1 person found this answer helpful.
    0 comments No comments

  3. Bruno Sabbadin 71 Reputation points
    2021-12-03T20:07:55.933+00:00

    You can do anything but to open a Support case: they did fix it in a couple of days.

    1 person found this answer helpful.

  4. cavng 6 Reputation points
    2021-12-03T20:16:00.447+00:00

    I've been having the same issue since the beginning of November. Here is what I've tried:

    • Adding a webhook via Teams for Web.
    • Adding a webhook via the Apps panel.
    • Logging in with various privilaged/unprivilaged user accounts.
    • Logging in with a user without MFA enabled.

    None of these worked. Microsoft, please fix.

    Edit: I've been in talks with Microsoft support. They claimed that a badly developed/broken connector was causing the issue.

    While they could not tell me which one was at fault, they speculated it might be Zabbix Webhook, as it was my last-added connection. Unfortunately, removing Zabbix Webhook (and eventually all other apps) from the team via Manage Team > Apps and waiting 24-hours for the change to propagate did not resolve the issue, but this may work for your organization.

    I was eventually able to "resolve" the issue by deleting the impacted team in its entirety. While this was a low-impact decision in my particular organization, I imagine that most organizations will want to avoid deleting an entire team.

    1 person found this answer helpful.

  5. Natascha van Neerven 11 Reputation points
    2021-12-08T15:18:17.9+00:00

    it seems like my issue is fixed. I have 3 connectors(Sharepoint News) running in 3 different Teams. Ik have no idea why the errors suddenly disappeared

    1 person found this answer helpful.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.