# O365 connectors within Teams will be deprecated and notifications from this service will stop

**URL:** <https://discuss.elastic.co/t/o365-connectors-within-teams-will-be-deprecated-and-notifications-from-this-service-will-stop/363240>\
**Category:** Kibana\
**Created:** [July 16, 2024, 6:25pm UTC](https://discuss.elastic.co/t/o365-connectors-within-teams-will-be-deprecated-and-notifications-from-this-service-will-stop/363240 "2024-07-16T18:25:43Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Patr123](https://avatars.discourse-cdn.com/v4/letter/p/ac91a4/32.png) [@Patr123](https://discuss.elastic.co/u/Patr123)\
**Post date:** [July 16, 2024, 6:25pm UTC](https://discuss.elastic.co/t/o365-connectors-within-teams-will-be-deprecated-and-notifications-from-this-service-will-stop/363240/1 "2024-07-16T18:25:43Z")

</div>

**Action Required:** O365 connectors within Teams will be deprecated and notifications from this service will stop. [Learn more](https://aka.ms/O365ConnectorDeprecation) about the timing and how the Workflows app provides a more flexible and secure experience. If you want to continue receiving these types of messages, you can use a workflow to post messages from a webhook request. [Set up workflow](https://teams.microsoft.com/l/task/c3a1996d-db0f-4857-a6ea-7aabf0266b00?url=https://make.powerautomate.com/teams/store/flowCreation?templateId=d271a6f01c2545a28348d8f2cddf4c8f)

So now do we need to use webhook instead of the microsoft teams connectors for kibana rules?  
Was anyone able to use it successfully?

Right now I am using the microsoft teams connector and it works like a charm. The new workflow doesn't seem to work at all.

---

<div class="post-metadata">

**Author:** ![Sean\_Story](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sean_story/32/69987_2.png) [@Sean\_Story](https://discuss.elastic.co/u/Sean_Story)\
**Post date:** [July 16, 2024, 6:51pm UTC](https://discuss.elastic.co/t/o365-connectors-within-teams-will-be-deprecated-and-notifications-from-this-service-will-stop/363240/2 "2024-07-16T18:51:41Z")

</div>

Removed #connectors

---

<div class="post-metadata">

**Author:** ![Marchelune](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marchelune/32/112334_2.png) [@Marchelune](https://discuss.elastic.co/u/Marchelune)\
**Post date:** [August 13, 2024, 8:43am UTC](https://discuss.elastic.co/t/o365-connectors-within-teams-will-be-deprecated-and-notifications-from-this-service-will-stop/363240/3 "2024-08-13T08:43:32Z")

</div>

Hi!  
I believe Microsoft has finally agreed to delay the deprecation at least until **December 31, 2024** , and even December 2025 if the Teams connector url is updated in a way we don't know yet.

That said, we will still not be able to create new Teams Connector already from 15th of August 2024 (I actually can't find the Teams Connector already).  
The trick to use Kibana's webhook is to set the `content-type` header to `application/json` , otherwise Kibana uses `application/x-www-form-urlencoded` by default.

If you're interested I had compiled a guide with a Kibana sample here: [Microsoft Teams Webhook retirement: an unofficial emergency guide](https://javascript.plainenglish.io/microsoft-teams-webhook-retirement-an-unofficial-emergency-guide-76d242ce944f).

Hopefully the Elastic Kibana team will offer a new connector based on the AdaptiveCards so that we don't have to write that json payload manually 😬.