Microsoft Teams Incoming Webhook Deprecation & Keep's Teams Provid

[shuan-han]

HI,

We are reaching out regarding the upcoming deprecation of Microsoft Teams Incoming Webhooks, which are slated to cease functioning after December 2025.

Currently, our Keep workflows rely on the existing Teams Provider, which appears to be configured to use these traditional Incoming Webhook URLs. We understand that Microsoft's recommended alternative is to leverage Teams Workflows powered by Power Automate, which generates a different type of webhook URL and expects Adaptive Card payloads.

Our primary concern is ensuring the continuity of our incident notifications via Teams. Given that Keep's existing Teams Provider seemingly only supports the soon-to-be-deprecated Incoming Webhooks, we'd like to inquire:

Does Keep plan to update the existing Teams Provider to directly support Power Automate Workflow URLs and Adaptive Card payloads?

Are there any alternative solutions or recommended migration paths within Keep itself (e.g., a new Provider type, a generic Webhook Provider that can be configured for Power Automate Workflows, or official guidance on using custom scripts/integrations) to ensure Teams notifications continue seamlessly after the deprecation?
Your guidance on this critical transition would be highly appreciated. We aim to proactively adapt our workflows to avoid any disruption in our incident management processes.

Thank you for your time and assistance.

[talboren]

Hey @shuan-han,

Thank you so much for opening this discussion!

It sounds like we're speaking about 2 different things, and let me know if I'm missing something:

1. Teams is going to deprecate the current incoming webhook method, which means that Keep needs to support their new way of sending messages (i.e., Power Automate, which supports other webhook URL.
2. Keep needs to support the newly Adaptive Card payloads

Re 1: I will have to deeply dive in to it, but from briefly reading through the docs, it seems that we will still be able to support this new method. It will just require some documentation changes to make sure people know how to generate those webhook URLs (contributions are welcome! :D)
Re 2: We already support that! Checkout this: https://docs.keephq.dev/providers/documentation/teams-provider#in-workflows -- there are a few examples for workflows that already use Adaptive Card payload.

Hope that clarify some things, let me know if not.