You may have already heard that Microsoft is deprecating the O365 connectors in teams (which are currently used to send notifications to MS Teams) and replace it by Workflows (see: Retirement of Office 365 connectors within Microsoft Teams).
So, has anyone of you already successfully setup such Workflow? Any information/docu to share?
is there such a possibility to receive an email in a channel and display it as message?
EDIT: quickly checked: there is an app in Teams to monitor an O365 inbox. We are not using O365 as email provider (yet)…so it won’t work in my case
I’m not an O365 expert, but doesn’t that mean that you would need an additional mailbox which requires an additional license? (sorry for that dumb question )
Looks like the notification plugin needs to be rewritten to send the information as “AdaptiveCard” instead of “MessageCard”.
I now created a simple workflow in Teams by selecting the template “Post to a channel when a webhook request is received” and then tried to send the following data with curl to this webhook and succeeded!
One thing to mention: looks like the HTTP status of the call is here no longer 200 but 202, which causes CheckMk to think that the notification has failed.
EDIT: issue with status already fixed, so nice that function process_by_status_code has this parameter “success_code”
It’s Microsoft, so can one be sure about anything? You may be right about AdaptiveCard, if I remember I stumbled about a message that it might be deprecated too (but don’t find that information anymore).
Maybe it will also work when we embed the current MessageCard in the above construct as attachment. Will try this out later today.
it’s both that we need. first there needs to be the workflow defined (template “Post to a channel when a webhook request is received”) and then we can send the AdaptiveCard to this new “workflow webhook” in the format as described above (AdaptiveCard as part of the “attachments”)
Yes, i think that’s the way to go.
Your examples are very useful, big thank you for that.
Will adjust the notification script next week so we should be prepared.
It’s not nice that users have to take action on there side but i think there will be no way around that.
a quick write up on steps on WorkFlow side would help here, there is a limitation of workflows not posting to private Channels and such. Will new setup require a valid O365 user (service account) ?
in the next page you can give the workflow a nice name and then click next and finally on the last page select the team and the channel to which the messages should be posted: