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

[markush81]

Magenta: I hope this is a misunderstanding. This should not be up to “me” (as you wrote “you”. Who is “you”?).

You = the one creating the Jenkins Job.

[markush81]

Red: This can be somewhat resolved by the Admin, for example, by using a Workflow owner named “Jenkins”.

Yep, if your company policy allows to have an owner which is not a human. But you're right my answer wasn't correct.

[PrismaComputer]

@markush81, regarding magenta: Of course, this is configured through Jenkins' job name. My picture was produced with a CURL command, not with a fixed plugin. However, I expect this to be handled by the plugin in the future.

To prevent further confusion, has your pull request (thanks for that) been merged and released? Is there something to test and see? I apologize for the seemingly obvious question; this information could undoubtedly be found here on GitHub.

[markush81]

@PrismaComputer no, it is not merged/released.

If you're "fearless" you could use my local built version from here https://github.com/markush81/office-365-connector-plugin/releases/tag/alpha and install the hpi manually. Or built the PR or from the fork the branch o365-adaptivecards yourself.

[sebracs]

Orange: How can we remove this completely unnecessary comment?

@PrismaComputer You can remove the Template reference by exporting and important the Workflow. Via Power Automate export to zip and import (only via Website https://make.powerautomate.com/ -> My flows -> select -> Export -> Package (.zip)) works for sure. Maybe copying inside Power Automate also works, but I have not tried it. Of course you can also get this by creating a new Flow from scratch (without starting from a template)

[KIuliia]

Last week I got this working with Power Automate using its "when a Teams webhook request is received" >>> "Post card in a chat or a channel". I used the adaptive card i think @jimmygoogle posted above here and editted it to suit what I needed. This also involved changing the old teams webhook with Power Automates new webhook for nearly every job I have setup in Jenkins.

What I noticed was that I was receiving 3 identical notifications in the Teams channel for every job being completed. I seen this morning that the plugin was updated here so I installed it. That has resolved the 3 notificiations issues and I am only receiving 1 as expected now.

I have the same issue - notification is sent 3 times. can you please explain what you mean by updated the plugin? we have installed it last week and we have this issue.

[myronu]

I have the same issue - notification is sent 3 times. can you please explain what you mean by updated the plugin? we have installed it last week and we have this issue.

Just update to the latest version of the plugin. That is the one thing they did fix.

[damianszczepanik]

Did you use office-365-connector-plugin to post message from Jenkins using old card format or you have created new payload with adaptive card?

[FrankReisenhofer]

Just one remark from my side:

The new approach with using PowerAutomate has a critical security concern:

The new endpoint is "public", which means anyone that knows the endpoint can trigger workflow in user context without user authentication.