Especially as the announcement says "Sage is actively working on QuickCal 1.2"..... we would like the focus to be on the Exchange Integration patch more. 

Agreed. The "tone" of the announcement suggests that it will be a longer wait than expected.

We've just taken a decision this morning to go for it and build our own Graph API-based Exchange Online calendar sync for Sage CRM. We're going to include the Teams 'isOnlineMeeting" toggle within the communication and allow the storage of meeting transcription data. We've already done quite a bit of the core code for a custom field service management extension.  Not quite sure what the delay is... but my team are hoping to get a beta out as soon as the end of this week for one of our partners.

Hi Matthew. The focus of the Sage CRM Development team is entirely on delivering the Exchange Integration patches. QuickCal was implemented and tested by Jeff and the L3 Support team

Just had my first sync customer report issues today.  Getting "ExchangeImpersonation SOAP header is not supported in the delegate flow., action: CONNECTION_TO_MAILBOX" in the current_exchangesynch.log file.

Looks like Microsoft held to their word, they turned off Application Impersonation.  Here is their announcement from last Nov 2024:  https://techcommunity.microsoft.com/blog/exchange/critical-update-applicationimpersonation-rbac-role-deprecation-in-exchange-onlin/4295762

Really need an update on when that patch is going to be available, so I can share that with my customer.  Any updates on the release date of the patch/fix?

Microsoft made the announcement over 12 months ago. Plenty of time in my opinion (even for a small dev team) to deliver any patch.

Agreed Sean.  Keep us posted on the sync utility you are building.  We may need it.  Thanks.

Dring Dring

It's time to deliver the patch guys. 

All our customers' integrations are down

Sage CRM & Exchange Online Integration: Patch Release Update

We understand the importance of the Sage CRM integration with Microsoft Exchange Online and sincerely regret the ongoing delay in releasing the necessary patches. Despite our dedicated efforts, we have not yet completed the work required for their release.

Our team is making continuous progress in adapting Sage CRM’s integration from Exchange Web Services (EWS) to Microsoft Graph API, ensuring a secure and future-proof solution. However, due to the complexity of this transition, we are not in a position to provide a firm release date at this time.

We recognize the disruption this is causing and want to assure you that delivering these updates remains our highest priority. We will provide further updates as soon as we have a clearer timeline.

Thank you for your patience and understanding.

Please see:  communityhub.sage.com/.../sage-crm-and-microsoft-exchange-online-integration---patch-release-date

How are we looking for a release of the patch today? We've had a growing count of customers complaining about the loss of Exchange Int. 

Sage 2024 R2.1 will be released today.

Still working on confirmation of 

• Sage CRM 2022 R1 & R2 – Patch 2022 R2.6
• Sage CRM 2023 R1 & R2 – Patch 2023 R2.4

The Sage announcement says the patch for SageCRM v2024 R2 was released, but I can find it on the SageCRM Download portal page.  Where will we be seeing that?  I would like to get it installed at one of my customer sites this weekend.

Hi Don

It may still be waiting for support teams to add the patches to the partner portal.

Copy that, thanks.

Have downloaded it and tried it in my demo system and have issues configuring it - currently logged with support. Will report back once all is successful. 

North American Support team, can you give us an idea of when the patch and config instructions will be available to us?

I'm also having issues getting the Exchange sync working in our Sage CRM 2024 R2.1 test environment. Has anyone else seen this error message?

DEBUG [http-nio-10001-exec-3]: [17-Mar-2025 16:47:58.469] Before calling testConnection EWS method for a user null
DEBUG [http-nio-10001-exec-3]: [17-Mar-2025 16:47:58.470] graph token : null
DEBUG [http-nio-10001-exec-3]: [17-Mar-2025 16:47:58.559] Checking : [email protected]

ERROR [http-nio-10001-exec-10]: 17-Mar-2025 16:47:58.851 ewsUrl: outlook.office365.com/.../Exchange.asmx, operation: checkExchangeConnection, error: Invalid credentials, java.lang.NullPointerException, action: ESTABLISHING_CONNECTION_EWS_ENDPOINT

To me this looks like the email address is not being picked up correctly for the user configured to perform the synchronisation. Or it could be that I have missed something during the configuration, but I have followed all the steps in the ReadMe.

Hi can someone post a link to download this patch please. From France here and customers are ... "impatient" ;) Thanx alot

I got mine from the usual file download area at my.sage.co.uk 

As to my issue, I raised it with support and they were able to replicate it and it's been passed to the developers to sort out

Basically I followed the ReadMe and set up the Azure App, entered in the Client ID in CRM (interestingly it didn't ask for the Secret), saved the screen and as usual it prompted for the Microsoft user to approve the link, CRM then did some checks like it used to when saving Exchange Integration settings and it fails on the Sync Engine step. 

When taken back to the configuration screen the OAuth URL (which is a read only field) is then blanked out and refuses to save. 

Hi Matthew

Our team is already looking at this and why you are having issues.  We hadn't experienced this issue our testing so it may be something to do with your environment.  BUT we are all over this now!

Hi Stanislas_p , did you get a version of the patch for the french version of Sage CRM ?

Rien pour l'instant

im seeing this in the log file:

URL : scrm/.../checkExchangeConnection
MSG : The connection with the server was terminated abnormally

Hi Matthew, can you send the patch by wetransfer or something like this please ? We are always the last in europe for these kind of things