Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Retirement of Office 365 connectors in Teams #53

Open
dlnash18 opened this issue Jul 8, 2024 · 3 comments
Open

Retirement of Office 365 connectors in Teams #53

dlnash18 opened this issue Jul 8, 2024 · 3 comments

Comments

@dlnash18
Copy link

dlnash18 commented Jul 8, 2024

Microsoft announced on 2024-07-03 that it is retiring Office 365 connectors in Teams. The replacement is to use a Workflow. I imagine this add-on will need to be updated in response to this.

@securitytime
Copy link

I couldn't manage to create a functioning workflow for this add-on. Highly appreciated if there is an update.

@jeking-illinois
Copy link

Literally got here the week that the Teams "Incoming Webhook" connector went offline!

The "problem" with using a Flow is that the alert action is sent with "MessageCard" (depreciated) formatting vs what Flow is expecting which is "AdaptiveCard" formatting. I know that the "body" of the MessageCard could be mapped to fields in the AdaptiveCard, but I haven't had success doing it just yet. The better solution would essentially be a new version that supports AdaptiveCard natively, which is a big ask.

@faleon
Copy link

faleon commented Jul 23, 2024

I'd like to also add my post to request an update to the JSON. Our company relies on this for Splunk to spend notifications to Teams.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants