Notifcation Controller: Support Microsoft Power Automate Workflow as a Provider

[CelPyn]

Microsoft is deprecating support of Office 365 connectors.

We will gradually roll out this change in waves:

• Wave 1 – effective August 15th, 2024: All new Connector creation will be blocked within all clouds
• Wave 2 – effective October 1st, 2024: All connectors within all clouds will stop working

It's hard to find documentation on this, but it seems like the Connector Card API contract, (which the current msteams provider implementation uses), is not supported by the available "incoming webhook" action in Power Automate. Instead, it requires the Adaptive Card API contract, which in turn is not supported by the Connector webhook.

With this discussion, I propose the creation of a new Provider Kind which supports the Adaptive Card.

[zeeZ]

Big point from the comments (according to the counter there are 125, but the other pages don't load) that a lot of people might be running into, before it gets missed:

Sending a message in private channels isn't supported.

[CelPyn]

Hi, I tested this out in my org's Teams tenant and managed to get this working.

It's a bit of a dirty workaround, but if you set the Post As value to User it will post a message under your name, which uses your permissions and will allow the Workflow to send messages to private channels that you're part of on your behalf.

I'm assuming that you can also use Flow Bot once you add the Workflows app to your Teams channel, but I'm currently not able to get that to work. The app gets installed twice and the Workflows configured via this way are not showing up. Running the workflow with this value results in a "Can't install the Power Automate app automatically" error.

This is probably out of scope for the implementation of this hypothetical Provider, but I do agree that this would need to be clearly documented, at least until Microsoft fixes things on their end.

[jornh]

Related issue: fluxcd/notification-controller#878