# Office 365 Integration Issue

**URL:** <https://discuss.elastic.co/t/office-365-integration-issue/378103>\
**Category:** Elastic Agent\
**Tags:** integrations\
**Created:** [May 13, 2025, 9:52pm UTC](https://discuss.elastic.co/t/office-365-integration-issue/378103 "2025-05-13T21:52:50Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![erikg](https://avatars.discourse-cdn.com/v4/letter/e/91b2a8/32.png) [@erikg](https://discuss.elastic.co/u/erikg)\
**Post date:** [May 13, 2025, 9:52pm UTC](https://discuss.elastic.co/t/office-365-integration-issue/378103/1 "2025-05-13T21:52:50Z")

</div>

Hello,

Anyone experiencing similar issues with the Office 365 integration?

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/e/7/e790252709e8c985d698b6608b5baf7c019fe859.jpeg)

It was working fine for months and then it error out today

---

<div class="post-metadata">

**Author:** ![efd6](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/efd6/32/94818_2.png) [@efd6](https://discuss.elastic.co/u/efd6)\
**Post date:** [May 14, 2025, 10:16pm UTC](https://discuss.elastic.co/t/office-365-integration-issue/378103/2 "2025-05-14T22:16:50Z")

</div>

Can you say what version of the stack you are using and also (this is important) what version of the agent you have installed? If the agent is below v8.18.0 this will not work. It should not install if your stack is below this version, but sometimes it is possible for agents to be not upgraded when a stack is.

---

<div class="post-metadata">

**Author:** ![erikg](https://avatars.discourse-cdn.com/v4/letter/e/91b2a8/32.png) [@erikg](https://discuss.elastic.co/u/erikg)\
**Post date:** [May 14, 2025, 11:01pm UTC](https://discuss.elastic.co/t/office-365-integration-issue/378103/3 "2025-05-14T23:01:00Z")

</div>

Hey @efd6 I was coming back to conclude this was solved.  
The elastic agent with this integration was upgraded from v8.16.3 to v8.18.0. This solved the issue.  
We are on Elasticsearch/Kibana/Fleet v8.18.0

We don't upgrade our elastic agent when we upgrade the stack.Bad practice, maybe? We have abundant of elastic agents deployed (clients/servers), agent upgrades are not easily done and frequent due to change management procedures.

---

<div class="post-metadata">

**Author:** ![efd6](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/efd6/32/94818_2.png) [@efd6](https://discuss.elastic.co/u/efd6)\
**Post date:** [May 14, 2025, 11:04pm UTC](https://discuss.elastic.co/t/office-365-integration-issue/378103/4 "2025-05-14T23:04:09Z")

</div>

We make use of the `kibana.version` value in the integration manifest to gate versions because it's expected that agents will match the stack version. So if you upgrade the stack without upgrading agents, you can expect this kind of breakage.

---

<div class="post-metadata">

**Author:** ![erikg](https://avatars.discourse-cdn.com/v4/letter/e/91b2a8/32.png) [@erikg](https://discuss.elastic.co/u/erikg)\
**Post date:** [May 15, 2025, 1:40pm UTC](https://discuss.elastic.co/t/office-365-integration-issue/378103/5 "2025-05-15T13:40:27Z")

</div>

I know it sounds like a given, but I feel like this is not explained clearly and can potentially cause many headaches for other users. I saw a slack thread asking about agent compatibility and stack version similar [here](https://elasticstack.slack.com/archives/CNEDGGJQ3/p1747220740622899)

---

<div class="post-metadata">

**Author:** ![kcreddy](https://avatars.discourse-cdn.com/v4/letter/k/6f9a4e/32.png) [@kcreddy](https://discuss.elastic.co/u/kcreddy)\
**Post date:** [May 15, 2025, 2:49pm UTC](https://discuss.elastic.co/t/office-365-integration-issue/378103/6 "2025-05-15T14:49:35Z")

</div>

There is an open public issue tracking this [here](https://github.com/elastic/package-spec/issues/165), so that elastic agent version requirement can be independent of `kibana.version`.