Microsoft Teams workflows

[Denvek]

📑 I have found these related issues/pull requests

I could not find any other issues specifically relating to Microsoft Teams Workflows.

🏷️ Feature Request Type

Change to existing notification-provider

🔖 Feature description

Microsoft are deprecating O365 connectors https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/ and asking everyone to move to workflows instead. Setting up a workflow in my Teams and then switching the webhook URL in Uptime Kuma to the new workflow one does not work - Kuma says a test was sent successfully but Teams says the workflow failed.

✔️ Solution

An update to the Microsoft Teams notification functionality to allow users to switch to using workflow webhooks.

❓ Alternatives

No response

📝 Additional Context

New O365 connectors using the existing method will not be able to be created after August 15th 2024. Existing connectors will stop working after October 1st 2024

[A-Matt]

Just about to open a ticket regarding the same thing 🤣

The full (pre-generated) flow which Microsoft suggests you create for the migration process:

The Error from Power Automate is:

[A-Matt]

This may already be fixed via this #4538 (Not in v1.23, planned for v2)

[Denvek]

I've updated the original post to explicitly include the dates from the Microsoft announcement. It looks to me like #4538 does fix this, but this needs to be released preferably before August 15th, and before October 1st at the latest.

[Stuart-harper]

Do we Know if there is any way to get the old way working if there isnt been an update to this?

[Reftek85]

I have the same issues,
as Microsoft is deprecating direct teams connector and force us to use PowerAutomate.
the automation reports this error
L'action « Send_each_adaptive_card » a échoué: The execution of template action 'Send_each_adaptive_card' failed: the result of the evaluation of 'foreach' expression '@triggerOutputs()?['body']?['attachments']' is of type 'Null'. The result must be a valid array.

would be nice to have the #4538 fix without having to wait till V2.0 release who know when.

[cvsickle]

For anyone here looking for a temporary solution for sending Uptime notifications to a Teams channel, you can setup an email notification. Each Teams channel can have an email address created for it, by right clicking the channel and selecting "Get email address."

As long as the setting "Anyone can send emails to this address" is selected, you can create an SMTP Email notification in Uptime Kuma to post to that channel.

This solution isn't ideal, as the notifications come formatted like an email, but it is a workable solution if we get to the point where we can no longer create Incoming Webhook connectors before the update to Uptime Kuma has been released.

[Tabisch]

Posted this to #4934 but just wanna mention it here too.
I made a PR and a work around to get it working again.
#4934 (comment)

[CommanderStorm]

Issue should be resolved in https://github.com/louislam/uptime-kuma/releases/tag/2.0.0-beta.0