Summary
Following further investigation and testing, Sage has confirmed the root cause of the Exchange Online integration error affecting Sage CRM and has validated the official PowerShell workaround for specific supported versions of Sage CRM.
This advisory updates and supersedes earlier guidance by confirming the exact Sage CRM versions for which the workaround is supported.
Who is affected
This issue affects:
-
Customers using Exchange Online with the Sage CRM Exchange Sync Engine
-
Sage CRM systems, where Exchange integration was previously working and then began failing
This issue does not affect:
-
On-premise Microsoft Exchange Server integrations
-
OAuth2-based import of Contacts and Emails
-
Other Sage CRM email functionality
Cause
Our testing has confirmed that the issue is caused by changes introduced by Microsoft to Exchange Online validation behaviour. These changes now reject requests containing a malformed or deprecated URL in XML headers used by the Exchange Sync Engine.
These XML headers were previously accepted and no longer comply with current Exchange Online validation rules. No changes were made to Sage CRM that directly caused this behaviour.
Supported Sage CRM versions for the workaround
The official PowerShell workaround has now been validated and is supported for the following Sage CRM versions:
-
Sage CRM 2023 R2.4 onwards
-
Sage CRM 2024 R2.1 onwards
-
Sage CRM 2025 R1
-
Sage CRM 2025 R2
The workaround should only be applied to these versions.
Available workaround
The official workaround, including the PowerShell script and detailed instructions, is available in the Fixes and Workarounds section of the Sage CRM Community Hub:
Earlier versions
Earlier supported versions of Sage CRM that fall below the versions listed above are not covered by this workaround. Customers running earlier releases should review upgrade options to a supported version where the workaround is applicable.
Next steps
Customers experiencing this issue and running one of the supported versions listed above should review and apply the official workaround.
Further updates will be shared on the Sage CRM Community Hub should additional guidance become available.
