MS Teams notifications are currently broken with new message format

[wargamez]

Microsoft are urging users to convert to a / generate a new url for webhook by December. This new format which adds a new path to existing webhook urls seems not to be supported by shoutrrr containrrr/shoutrrr#446. Any plans to change this library which seems like it hasn't gotten any commits in over a year? (To be clear, I am not talking about MS workflows, just new webhook urls)

old:
https://<organization>.webhook.office.com/webhookb2/<group>@<tenant>/IncomingWebhook/<altId>/<groupOwner>

new:
https://<organization>.webhook.office.com/webhookb2/<group>@<tenant>/IncomingWebhook/<altId>/<groupOwner>/<newSegment>

/E

[jorgelon]

Yep
Here is the link

https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/

[YildizBurhan]

@wargamez I am guessing you havent found a workaround to make the new url format work with shoutrrr?

[dv0gt]

Any news here?? There is one week left only!

[evrardjp]

I don't have an environment for testing.
Did you try, by any chance, what's written in containrrr/shoutrrr#446 (comment) ?

[github-actions]

This issue was automatically considered stale due to lack of activity. Please update it and/or join our slack channels to promote it, before it automatically closes (in 7 days).

[heathharrelson]

A colleague and I just spent an annoying amount of time figuring this out, so I wanted to document our solution here. After updating your Teams webhook connector URL to the new format, you can configure kured to notify the channel using shoutrrr's generic webhook with the json template.

Copy the updated Teams connector URL and set kured's --notify-url (configuration.notifyUrl in the Helm chart) to:

generic://<organization>.webhook.office.com/webhookb2/...?template=json&messagekey=text

Note that https:// has been replaced by generic:// and query parameters have been added to the URL. This will get things working until shoutrrr supports workflows or you find some other solution.

[wargamez]

Thanks @heathharrelson, that did the trick!

[jorgelon]

If you are using external-secrets operator and extraEnvVars in the helm charts, this makes the conversion.

apiVersion: external-secrets.io/v1beta1
kind: ExternalSecret
metadata:
  name: kured-settings
spec:
 ...
  target:
    template:
      data:
        KURED_NOTIFY_URL: '{{ list .msteamsWebhookUrl "template=json&messagekey=text" | join "?" | replace "https://" "generic://" }}'

[evrardjp]

If I understood correctly, we have a workaround for teams. That's at least for now.

However, it means we have raised the question of overall maintenance level of the notification module we are using.
We are in a state where shoutrrr seems less maintained than it used to.

We'll need to determine what our next steps are.
From what I see, we can either help shoutrrr or use our own notification webhook (and start to maintain what shoutrrr was doing).

This needs to be a community decision, and someone needs to step up, contact the shoutrrr team to understand what are their plans and contribute to shoutrrr or kured to provide the required features/quality we expect all.

Did I get that right?