Timezone setting in MS Teams Notification V2 seems to be ignored

[zippi-ifn]

Description

Steps To Reproduce

1. Use new MS Teams Notification V2

Environment

• Graylog Version: Graylog 6.0.6+4aa664f
• OpenSearch Version: opensearch/stable,now 2.17.0 amd64
• MongoDB Version: mongodb-org-server/jammy,now 6.0.17 amd64
• Browser Version: --

Seems like this was fixed for the old plugin: Graylog2/graylog-plugin-integrations#1318
(and I accidentally opened the issue there)

When notifications are sent to MS Teams with the V2 plugin, the timestamp is always UTC, regardless of which timezone was selected in the drop-down list.

ATM Berlin is at GMT+2

[kingzacko1]

@zippi-ifn I'm able to reproduce the bug, but I think it may be on the Teams side of things... When I send a test notification with my UTC-5 timezone set on the notification I can see all the way in Teams Workflows that my UTC-5 was formatted properly. Here is an example from the Workflow Run History of my most recent test.

However, the card that was posted in my channel has been reformatted:

Check your Workflow history to find the raw message that was received by Teams and see if it is sent with the proper UTC+2 formatting. I think you will, meaning this is indeed a Teams issue.

And it seems to be a known issue, or rather something Microsoft says happens 'by design'. See this question on Microsoft's Q&A website. The one answer has two comments, the second one by Sandor Zeestraten seems to describe this exact scenario with no response as to why.

[zippi-ifn]

Thank you for investigating this.
The behaviour of the MS tool is ... let's say ‘D'OH!

I think the simple solution is to remove the timestamp from the message for now.