Forum Discussion
Channel connectors not loading
Hello there,
we are using a connector to get a notification about new Azure DevOps Pull Requests to a Microsoft Teams channel. Since these connectors are deprecating soon, we wrote an PowerAutomate flow to replace the old one.
We now finished the new flow and want to remove the old connector. But unfortunately the list of configured connectors for the channel is not loading - no matter if I try to access it in the installed app or in different browsers on different operating systems. The lists for adding new connectors work, but "Configured" and "My Accounts" does not.
I already cleared the cache of Teams, I also installed new browsers (on MacOS and on Windows systems), but the list is always empty.
Does someone have any tips how to remove the old connector?
- Same issue here, on multiple computers and multiple Teams accounts (different orgs).
It's great for this to break right when we should try switching to Work flows... - Same issue here... Hoping for a resolution soon.
There was a response last week from Microsoft in this other post: https://techcommunity.microsoft.com/t5/teams-developer/issues-with-ms-teams-connectors/m-p/4195335
So far no update though
I'm facing the exact same issue. I need to access the configuration area to see the existing RSS feeds we need transitioned to Work flow. Additionally, it seems that Microsoft has not provided an easy 'migrate' solution so that all existing RSS feeds can be migrated over to Work flow.
It seems we need to set everything up again from scratch, including adding every single RSS feed as a new entry in Work Flow, which is a massive amount of work and time for organizations who have setup hundreds of alerts on various subjects.
FlorianBerger - This didn't work for me but was suggested in a different thread. It might be worth a shot for you in case you have better luck than we did.
Edit Connectors Online:
https://outlook.office.com/connectors/publish
Solution would be greatly appreciated.- Thanks for the link, but it also didn't work for me - the list on this page also stays empty.
Same here.
The error seems to be related to the webapp itself.
Some console errors are:
[Error] Refused to connect to https://login.microsoftonline.com/common/oauth2/authorize?...._0&x-client-ver=7.5.1.0 because it does not appear in the connect-src directive of the Content Security Policy.
[Error] Blocked by Content Security Policy.
[Error] XMLHttpRequest cannot load https://login.microsoftonline.com/common/oauth2/authorize?client_id=...=7.5.1.0 due to access control checks.
[Error] Possibly unhandled rejection: {"data":null,"status":-1,"config":{"method":"GET","transformRequest":[null],"transformResponse":[null],"jsonpCallbackParam":"callback","params":{},"headers":{"Accept":"application/json, text/plain, */*","X-Requested-With":"XMLHttpRequest","If-Modified-Since":"Mon, 26 Jul 1997 05:00:00 GMT","Cache-Control":"no-cache","Pragma":"no-cache"},"url":"Manage/GetOrgPrivacyUrlAsync"},"statusText":""} – undefined
(anonymous function) (vendor.min.js:6:52777)
(anonymous function) (app.min.js:1:13613)
rt (vendor.min.js:6:73400)
$digest (vendor.min.js:6:79130)
$apply (vendor.min.js:6:80920)
at (vendor.min.js:6:56683)
rt (vendor.min.js:6:59132)
tt (vendor.min.js:6:59605)
