Replacing Retired Office 365 Connectors with Teams Workflows
Microsoft retired Office 365 Connectors in May 2026. You might not have noticed that some Teams channels no longer receive updates from different network sources via adaptive cards. The solution is to replace the old connectors with new Power Automate workflows. In this article, we discuss updating two PowerShell scripts to post information about Microsoft 365 roadmap items and service health to Teams channels. It’s only four months since the connectors stopped working… https://office365itpros.com/2026/09/18/teams-workflows-updates/Identify which channels incoming webhook connector is configured
As per MS communication incoming webhook connector url is changing, We are in process of communicating to our end user for same, hence as an admin we what to identify for which channels this incoming webhook is configured. we are able to get information from teams powershell for which team it is configured but not channel. Is there a way (powershell/ms graph/any Api) to find out for which channel this webhook connector is configured ?The Abuse of Teams Inbound Webhook Connectors and Channel Email Addresses
An article by security researchers Black Hills pointed to some vulnerabilities with incoming webhook connectors and email connections for Teams channels. Fortunately, it seems like Microsoft is making changes to Teams to improve security. Even so, it’s always wise for tenants to keep an eye on how information flows into Teams. https://office365itpros.com/2024/03/18/incoming-webhook-connector-abuse/
Is the connector inline configuration broken?
I'm making a new connector for Teams, and I found out that when I add a connector to a channel and hit the configure button, now I don't have the inline configuration page but instead I have a link "Visit site to install" that goes to the configuration page. I created another one a couple of months ago, and it was working as it normally does, showing the configuration page embedded within Teams UI. Thinking maybe there was something new, I tried to create connectors with the latest version and examples provided on Microsoft's web pages, and the result was the same link "Visit site to install". I also noticed that the "Connector Developer Dashboard" was broken last month since it wasn't saving the field "Valid domains", but now it works and now I have this other issue with not showing the configuration in the right place, making it difficult to get the webhook of the channel. I appreciate any guidance on this. Thanks!
CORS PREFLIGHT WHEN USE WEBHOOK FOR MICROSOFT TEAMS
Hi, i've created an angular app that send some Adaptive cards to a TEAMS channel created with connector plugin but when i try to post a a json i got following CORS ERROR. Is there a way to fix it? In documentation there is only an example using cUrl and Powershell but not using a frontend app .
SharePoint News Connector (MS Teams)
There is no way to configure the connector is this correct? (-> see Picture below, i cant do nothing) I can only activate the connector for one channel and it should automatically connect to the corresponding SPO with NewsWebPart. So I can't even configure multiple connectors in a team that pull information from different SPOnlines News WepParts?
Issue to configure connector, (503) Server Unavailable
I can't configure connectors , when try open the configure window, the server response with the next message : ErrorDetails=Microsoft.Griffin.Connectors.Store.ConnectorExtension.ExceptionErrorDetails:CorrectiveAction=NoAction:InnerErrorMessage=The remote server returned an error: (503) Server Unavailable. @rgcejudo have the same issue?
