Forum Discussion
Disabling Calendar Repair Assistant on mailboxes in Exchange Onprem 2019
Hi,
We are in Exchange Hybrid setup were some mailboxes are in cloud and onprem. Recently, there were some issues with Calendar events were recipients weren't notified of any updates for the events, sometimes the updated event would have been cancelled by recipient and the recipient didn't even know that they received update and it was automatically cancelled by them....
This was a normal situation for EAs for their executive calendar events
When raised a ticket with Microsoft on this issue, Microsoft collected CDL logs and found that CRA was kicking in each time when there was an update and was reverting the updated meeting request to the previous cancellation and as we know this is not a bug, this is just how the CRA works...So, Microsoft is like CRA is a legacy feature with limited applicability and functionality in the current exchange environment and hence has asked to disable-CRA in On-prem exchange as this will not affect normal calendar usage for users.
I had disabled for 5 users and they have reverted that they are not seeing any issues post disabling CRA. so before gunning down on all mailboxes I wanted to take a second opinion on whether is it safe to disable CRA for alll mailboxes in Exchange Onprem
1 Reply
Yes, it is generally safe to disable the CRA on Exchange on-premises mailboxes in a hybrid setup, and Microsoft's guidance in your case is sound.
Here's a breakdown to give you confidence before rolling it out org-wide.
The CRA is a background process that periodically scans mailboxes and attempts to fix inconsistencies between meeting organizers and attendees, for example, correcting mismatches in meeting status, location, or time. It runs on a schedule and does so silently, without user action.
The problem is that in a hybrid exchange environment, this "repair" logic can work against you. When meeting update legitimately flows from Exchange online to on-premises (or visa versa), the CRA can misinterpret the state delta as an inconsistency and revert the meeting to a prior state, in your case, reinstating a cancellation that has already been superseded by an update.
This is a known behavioral quirk, not a bug.
It's an older article on the techcommunity explaining CRA
Exchange 2010 Calendar Repair Assistant | Microsoft Community Hub
