Retirement of Office 365 connectors within Microsoft Teams

[yogeshpsp]

What feature do you want to see added?

Micorosft has announced that office 365 connector will expire on August 2024. Will this affect the office 365 connector jenkins plugin as well.
https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/

Upstream changes

No response

Are you interested in contributing this feature?

No response

[PrismaComputer]

A fix for the problem will be available in time?

[wjones38]

This plugin can continue to be used if you translate the data it sends on power automate into Microsofts "adaptive card" format. See the comment from Damian E here: https://gitlab.com/gitlab-org/gitlab/-/issues/471344 for the template I used that got this working for me.

The biggest issue I ran into is that this plugin looks for a 200 response and Power Automate does not give 200 responses, it gives 202 responses. I opened an issue to address this here: #356

[PrismaComputer]

Folks, don't get me wrong, I know it's for free and open source. But please try to see it from the Admin side, who's just a user from this point of view. It's not the aim of the user to translate anything from this plugin into whatever. Especially if the webservice isn't giving the expected response code anyway. Adjustments have to be made anyway. I think the aim should be to have one checkbox in plugin configuration to trigger the usage of another data format and expecting another response code.

[wjones38]

@PrismaComputer What you proposed would be nice, but the very simple addition of a 202 response code can be easily done in the short time window that Microsoft has given. Long term I wholeheartedly agree but, to be completely honest, right now I just need something that holds my team over until that long term solution is finished.

[damianszczepanik]

This plugin can continue to be used if you translate the data it sends on power automate into Microsofts "adaptive card" format. See the comment from Damian E here: https://gitlab.com/gitlab-org/gitlab/-/issues/471344 for the template I used that got this working for me.

Can be used but you need to user Power Automate and implement the workflow which will consume requests from this plugin. Is that correct?

[wjones38]

@damianszczepanik yes, that is correct. Its not probably the nicest solution ever but it gets the job done.

[damianszczepanik]

@damianszczepanik yes, that is correct. Its not probably the nicest solution ever but it gets the job done.

Agree. Then this plugin will work as pure curl with POST method and the adaptive cards with filled subject/text as the body of this request.

[PrismaComputer]

@damianszczepanik
Agree. Then this plugin will work as pure curl with POST method and the adaptive cards with filled subject/text as the body of this request.

As far as I can see, at the moment no adaptive cards are used. But for PowerAutomate adaptive cards are mandatory. This is at least my information, maybe I'm wrong. And it's not only the card definition itself. In opposite to “the old method” the card's JSON must be wrapped into "attachments": [] beside the “type”: “message”.

If I'm correct, just solving the 202 problem alone won't do the trick.

So, may I kindly ask where to edit the card's template? I did not find anything in Jenkins directory. But maybe I've overseen something.

[jimmygoogle]

This plugin can continue to be used if you translate the data it sends on power automate into Microsofts "adaptive card" format. See the comment from Damian E here: https://gitlab.com/gitlab-org/gitlab/-/issues/471344 for the template I used that got this working for me.

Can be used but you need to user Power Automate and implement the workflow which will consume requests from this plugin. Is that correct?

Unfortunately, you need a premium license to be able to use "When an http request is received", which would allow you to take the current payload Jenkins plugin sends and transform it to an adaptive card to post to a Teams channel. The "When a Teams webhook request is received" trigger does not require a premium license but it expects an adaptive card payload.

[damianszczepanik]

Can you clarify which one is where? This is not clear to me what is the difference or which one will work after office 365 retirement

[jimmygoogle]

Both webhooks will work as they are in the workflow setup (https://make.powerautomate.com/). The "When an http request is received" webhook allows you to supply the payload of the webhook that Microsoft will send. The "When a Teams webhook request is received" webhook expects a payload with a specific structure.

[wjones38]

Both webhooks will work as they are in the workflow setup (https://make.powerautomate.com/). The "When an http request is received" webhook allows you to supply the payload of the webhook that Microsoft will send. The "When a Teams webhook request is received" webhook expects a payload with a specific structure.

@jimmygoogle have you tested using the "When a Teams webhook request is received" and received errors when sending a format that doesn't match? I have been able to send whatever payload I want to that trigger and it has been working. Not sure if maybe I just managed to find a loop hole on accident or what.

[jimmygoogle]

Both webhooks will work as they are in the workflow setup (https://make.powerautomate.com/). The "When an http request is received" webhook allows you to supply the payload of the webhook that Microsoft will send. The "When a Teams webhook request is received" webhook expects a payload with a specific structure.

@jimmygoogle have you tested using the "When a Teams webhook request is received" and received errors when sending a format that doesn't match? I have been able to send whatever payload I want to that trigger and it has been working. Not sure if maybe I just managed to find a loop hole on accident or what.

Yes I have tried that webhook and I get "Action 'Send_each_adaptive_card' failed: 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."

[PrismaComputer]

Yes I have tried that webhook and I get "Action 'Send_each_adaptive_card' failed: 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."

I completely agree.

That is the trigger which Teams will set up automatically if you click the drop-in replacement link (which, unfortunately, does not create a drop-in replacement) in the warning. Additionally, this is the trigger which you can set up manually without PowerAutomate Premium:

This trigger expects:

• An adaptive card format, which is significantly different from the old Teams Card.
• Colours only as "default, dark, light, accent, good, warning, attention". No RGB values are allowed anymore.
• The card wrapped into "attachments": [] beside the “type”: “message”.

Otherwise, as you wrote, the error appears:

"Action 'Send_each_adaptive_card' failed: 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."