Bring back the Twitter Connector.
The removal of the twitter connector is a horrible decision. To do this with Power Automate is just a horrible user experience.
The power automate template is barely working for this and the user experience of it is horrbile. please bring back this connector.
as descibed by Tony i this blogg post
I echo the sentiments here. We just started using Teams in our company which is very much active on social media. It would be great if we can have tweets arrive directly in Teams without having to change interfaces. The Power Automate solution is difficult to setup.
Power Automate doesn't work properly... please, bring back the original connector which worked perfectly fine.
One way this would be helpful for us is to get Tweets from @MSFT365Status sent to our IT channels, so we are aware of outages and major events.
I don't feel comfortable giving Power Automate access to my Twitter account and it is inconvenient to create yet another Twitter account dedicated to using with Power Automate just so we can be notified of outages.
In my experience, I have found the Power Automate "replacement" for the Twitter connector to be buggy, unreliable, and difficult to set up properly. Tweets are sometimes delayed for hours without explanation. A Twitter connector similar to Slack's Twitter connector would be the ideal solution.
Bring it back!!
Hans Dickel commented
It is indeed a poor experience. It comes from "me" and not "Twitter", so it looks weird (I didn't do the tweet!). It is difficult to set up and get working right. It requires using an "external" tool, so not just "built-in". Now we are not using either, so our enterprise news isn't coming into Teams to notify us of updates, which is the purpose of Teams (proactive communications and collaboration).