-
Suggestion
-
Resolution: Fixed
The Automation Platform team is working to implement a new Microsoft Teams action, as an alternative to the current action that relies on the soon-to-be deprecated connectors. We'll provide an update shortly with more info on timelines for this new action.
***
Microsoft has announced they are deprecating O365 connectors (more details here).
Automation provides a Send Message to Microsoft Teams Action that relies on one of the O365 connectors.
Please provide an alternative to avoid disrupting existing rules and allow sending messages to a channel in Microsoft Teams once the existing connectors are retired.
[AUTO-1374] Provide support for Microsoft Workflows in automation rules
Hi all,
We’ve just shipped an update to the ‘Send Microsoft Teams message’ action in Automation. The action now uses Workflows in Microsoft Teams to send messages from your automation rules.
To update your rules, follow these steps:
- Go to your channel in Teams and select …› Workflows > Post to a channel when a webhook request is received
- Paste the webhook URL into the ‘Send Microsoft Teams message’ action
- Select Update.
We recommend you do this by December 31, 2024, to avoid any interruption to your automation rules.
Hi all,
We're noticed that some rules have been saved using the new url but with the old version of the MS teams action. We have added a check to pick this up and log it as an error in the audit log. The new changes have now fully been rolled out and this issue should no longer occur. However, if you are experiencing issues still, please check whether your rule has been updated.
The error message in the audit log will appears as follows:
Thank you for your patience in this.
All comments
Sorry adamru, but please read exactly what is stated in that announcement. Jira Server is no longer supported by Atlassian. Jira Data Center is still fully supported beside of Jira Cloud. If you have other information, please join these with us. Otherwise please do not create rumors! If so that should be the job of Atlassian itself 
aefc4c4c1923 ... hasn't all support ended for DC?
https://www.atlassian.com/migration/assess/journey-to-cloud
Support for Server products ended on Feb. 15, 2024
Server products and apps no longer receive technical support, security updates, and bug fixes for vulnerabilities.
fe7ce902b27f - It have not been "Fully" rolled out
- You forgot your Datacenter customers(again!).
https://jira.atlassian.com/browse/JIRAAUTOSERVER-1045 - Still "Gathering Interest"....OMG! - Teams on DC is broken = Incident!
Even the lovely 1st level supporters on keep just pasting wasteless updates of "since apologies" and "sorry for the inconvenience".
We reported this incident as a customer on July 16th - And still almost 2 months later, not a single valuable update on progress towards resolution.......All while Cloud customers are serviced.
Hi all,
We're noticed that some rules have been saved using the new url but with the old version of the MS teams action. We have added a check to pick this up and log it as an error in the audit log. The new changes have now fully been rolled out and this issue should no longer occur. However, if you are experiencing issues still, please check whether your rule has been updated.
The error message in the audit log will appears as follows:
Thank you for your patience in this.
62534117e636 / ezhapa / 89403358cf11 - the integration between Jira automations and MS Teams via Workflows is still broken. Who is responsible for re-opening this ticket and continuing to work the problem?
fae241a7c16d - it's not the community's responsibility to find a solution for that error. The Atlassian team – ezhapa and 89403358cf11 , et al. – is supposed to provide to the community an integration that doesn't throw that error. They claimed to have published an update but it's obviously still broken. This ticket obviously still needs to be worked. There are 154 people watching this issue and hoping Atlassian can solve its problems.
Has anyone found a solution for
"ExpressionEvaluationFailed. 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."
fe7ce902b27f - I can confirm this works for me now. Thank you for your attention to this issue.