Teams Out of Office Not Syncing for On-Prem Exchange Mailboxes in Hybrid Environment

Question

Teams Out of Office Not Syncing for On-Prem Exchange Mailboxes in Hybrid Environment

Davit Ubilava 0

We are running a Hybrid Exchange environment where some users have mailboxes on-premises and others are in Exchange Online.

We’ve noticed that Out of Office (Automatic Replies) do not sync for on-prem Exchange mailboxes in Microsoft Teams, while cloud mailboxes work correctly.

Additionally, when an on-prem user tries to set Out of Office directly from Microsoft Teams, they receive the following error:

"We were not able to schedule out of office. Try again by clicking Save."

The OOO setting is not saved, and no changes are applied.

For users with Exchange Online mailboxes, OOO works as expected and syncs correctly with Teams.

Hybrid connectivity, mail flow, and free/busy are functioning normally. The issue appears specific to Teams attempting to write or read OOO data from on-prem Exchange mailboxes.

Is this a known limitation by design, or is there a supported configuration or workaround to enable Teams OOO integration for on-prem Exchange users?

0 comments

2 answers

Your answer

Answer 1

Kha-N 8,260 Microsoft External Staff Moderator

Hi @DavitUbilava,

Welcome to Microsoft Q&A, and thank you very much for reaching out to us.

Based on your description of the Out of Office (OOF) not syncing issue, may I know whether the OOF status is never syncing at all, or if it does sync but only after a delay.

If the status updates with a delay, from my research, this behavior is expected by design as suggested by Q&A assist. As noted in this Microsoft documentation, when mailboxes are hosted on‑premises, Teams relies on periodic polling rather than real‑time integration. This can result in delays of up to one hour before Teams reflects the updated state.

User's image

Regarding configuring OOF directly from Microsoft Teams, unfortunately based on this Microsoft documentation, this is not supported for on‑premises Exchange mailboxes. This capability is only fully supported when the mailbox is in Exchange Online.

User's image

Therefore, for on‑premises users, I recommend configuring their Out of Office message through Outlook application or Outlook web as a workaround. This ensures that automatic replies work correctly for email flow. However, please note that Teams won’t fully reflect or sync that OOF state, as mentioned previously.

I also understand why having the option for on‑premises users to set their Out of Office directly from Teams would be valuable. I checked and found a Microsoft Feedback entry requesting native Teams integration for Exchange on‑premises environments. I recommend reviewing the feedback, voting for it, and adding your comments. The more voices behind a request, the more likely Microsoft is to prioritize it in the future.

Thank you for your understanding.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Kha-N 8,260 Reputation points Microsoft External Staff Moderator

2026-01-05T00:19:17.8333333+00:00

Hi @DavitUbilava,

I hope you are well.

It’s been a few days, and I just wanted to follow up on your issue.

Have you had a chance to review my suggestion?

Warm thanks.
Kha-N 8,260 Reputation points Microsoft External Staff Moderator

2026-01-21T11:11:40.29+00:00

Hi @DavitUbilava,

I hope you are well.

It's been a while, and I just wanted to check on your issue. Was my provided information helpful?

If you feel this discussion has been helpful, please consider marking this thread as accepted by clicking “Accept the answer.” This helps surface the information provided for others encountering similar issues and contributes to building a stronger, more informed community.

Warm thanks.
Davit Ubilava 0 Reputation points

2026-01-26T14:11:55.39+00:00

Hi @Kha-N ,

Apologies for the delayed response, and thank you very much for your attention and detailed explanation.

To clarify, this was not an issue in our environment before — Out of Office status for on-premises Exchange mailboxes used to sync correctly with Microsoft Teams. The problem started recently, around just before the New Year.

At this point, the behavior is that the OOF status does not sync to Teams at all for on-prem users — not even with a delay. Additionally, attempting to set Out of Office directly from Teams consistently results in an error and the setting is not applied.

Thank you again for your support and follow-up.

Best regards,
Kha-N 8,260 Reputation points Microsoft External Staff Moderator

2026-01-26T14:56:18.9566667+00:00

Hi @DavitUbilava,

Thank you very much for your response and the update.

Please note that our forum is a public platform, and we will modify your question to hide your personal information in the description. Kindly ensure that you hide any personal or organizational information the next time you post an error or other details to protect personal data.

Based on your additional information, please allow me a bit of time to research this further. I’ll get back to you as soon as I have more information that can further help you.

Warm thanks.
Kha-N 8,260 Reputation points Microsoft External Staff Moderator

2026-01-27T14:05:55.5366667+00:00

Hi @DavitUbilava,

Thank you very much for your patience.

I research further on your issue, if Out of Office updates for on‑premises Exchange mailboxes stop working entirely, it can also be related to EWS App Access Policy restrictions.

Microsoft Teams depends on Exchange Web Services (EWS) to read and update Out of Office (OOO) settings for on‑premises mailboxes. If EWS is disabled at the organization level, or if AppAccessPolicy blocks the Teams service principals from accessing EWS, then Teams will not be able to retrieve or write any calendar data for those mailboxes.

You mentioned that Hybrid connectivity is functioned normally, may I verify that you have run the Microsoft Remote Connectivity Analyzer to verify Exchange and Teams integration? If not, I suggest you run it again and let me know if you receive errors related to EWS. For example:

Regarding the behavior when setting Out of Office directly from Microsoft Teams, as noted in my earlier explanation, this is unfortunately by design. Teams does not support writing Out‑of‑Office settings to on‑premises Exchange mailboxes. This capability is only fully supported when the mailbox is hosted in Exchange Online.

For on‑premises users, I recommend configuring their Out of Office message through Outlook application or Outlook web as a workaround. This ensures that automatic replies work correctly for email flow.

I hope this helps. Looking forward to your response.
Kha-N 8,260 Reputation points Microsoft External Staff Moderator

2026-01-28T13:31:11.5066667+00:00

Hi @DavitUbilava,

I just wanted to check on your issue. Have you had a chance to check on my response?

Warm thanks.

Answer 2

In a hybrid Exchange environment, it is known that Out of Office (OOF) replies may not sync correctly between Microsoft Teams and on-premises Exchange mailboxes. This limitation arises because OOF settings for on-premises mailboxes are not fully integrated with Teams in the same way that Exchange Online mailboxes are. As a result, when an on-prem user attempts to set OOF directly from Teams, they may encounter errors like "We were not able to schedule out of office. Try again by clicking Save."

To work around this issue, on-premises users can set their OOF replies directly through Outlook or Outlook on the web instead of using Teams. This ensures that their OOF settings are applied correctly, even if they do not sync with Teams.

Currently, there is no supported configuration that allows Teams to fully integrate OOF settings for on-prem Exchange users, and Microsoft is aware of this limitation. They are working on resolving it, but until then, using Outlook for OOF settings is the recommended approach for on-premises mailboxes.

References:

Share via

Teams Out of Office Not Syncing for On-Prem Exchange Mailboxes in Hybrid Environment

2 answers

Your answer