# Elastic Microsoft Teams Connector

**URL:** <https://discuss.elastic.co/t/elastic-microsoft-teams-connector/387504>\
**Category:** Elastic Search\
**Tags:** elastic-workplace-search\
**Created:** [July 3, 2026, 12:17pm UTC](https://discuss.elastic.co/t/elastic-microsoft-teams-connector/387504 "2026-07-03T12:17:18Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![MR\_INTENSE\_GAMING](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mr_intense_gaming/32/147793_2.png) [@MR\_INTENSE\_GAMING](https://discuss.elastic.co/u/MR_INTENSE_GAMING)\
**Post date:** [July 3, 2026, 12:17pm UTC](https://discuss.elastic.co/t/elastic-microsoft-teams-connector/387504/1 "2026-07-03T12:17:18Z")

</div>

Could you explain why the current implementation fetches user-specific chats using the ROPC mechanism? As ROPC is considered an insecure approach and is especially problematic for federated accounts.

---

<div class="post-metadata">

**Author:** ![Artem\_Shelkovnikov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/artem_shelkovnikov/32/134322_2.png) [@Artem\_Shelkovnikov](https://discuss.elastic.co/u/Artem_Shelkovnikov)\
**Post date:** [July 3, 2026, 1:27pm UTC](https://discuss.elastic.co/t/elastic-microsoft-teams-connector/387504/2 "2026-07-03T13:27:25Z")

</div>

Hi @MR_INTENSE_GAMING,

Indeed it's a problem. We're looking if we can prioritise fixing this, but no ETAs are available yet.

---

<div class="post-metadata">

**Author:** ![MR\_INTENSE\_GAMING](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mr_intense_gaming/32/147793_2.png) [@MR\_INTENSE\_GAMING](https://discuss.elastic.co/u/MR_INTENSE_GAMING)\
**Post date:** [July 3, 2026, 1:49pm UTC](https://discuss.elastic.co/t/elastic-microsoft-teams-connector/387504/3 "2026-07-03T13:49:33Z")

</div>

So there is no specific reason for this implementation , I thought there might be limitation on the APIs or other dependencies.