Given that the QuickCal component doesn't fulfil all of the functions performed by the integration, do you have any target dates when we can expect the patches to re-enable this?
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.
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.
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!
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
Can you confirm the Sage CRM version you are using?
Not sure about the version in french CRM, but it's the last one. Sage France tells me they don't have received the patch yet
The last version in France (100c v11) is 2024R2.
Hi Matthew Shaw
Please check the Office 365 Exchange Online permissions listed in the ReadMe - the following steps resolved Mathew Simon's issue:

Good morning everyone
On Monday I raised this issue with tech support in the UK so have the reference CASE-04553887. Currently this has a status of Escalated with a reason of L3 - Project Engineering. Apparently a few people have raised an issue with the Exchange sync after applying Sage CRM 2024 R2.1
There are two questions I would like to ask everyone
The first thing I did on Monday was set the permissions in Microsoft 365 as per the documentation. When making changes to 365 they can take a while to propagate, which is why I did not raise this as being an issue straight away as I thought that it could just be a propagation delay in 365.

In the documentation there is an an entry for email,
Unless I am missing something obvious this does not appear to be a Delegated permissions for Office 365 Exchange Online

I simply get "Invalid Credentials" 
email was missing from my App permissions, since adding this, I still get the same problem.
Hi Matthew, can you send me the patch please ?
Hi AlisonA
The solution is to select Public client/native (mobile & desktop) instead of Web in App Registrations
i.e. when following the instructions in the 2024 R2.1 ReadMe for Getting OAuth 2.0 client ID and secret for Entra ID,
replace
"Under Redirect URI (optional), select Web and enter the following URIs:"
with
*Community Hub is the new name for Sage City