Exchange calendar not syncing in macOS Monterey 12.3

Hi, I'm on version 12.5 and I just started seeing this same issue now.

Same problem here, the workaround provided works but we need a fix from Apple. Maybe someone with a Microsoft Enterprise support could open a ticket to put pressure on Apple from the Microsoft side?

How do you do that?

Started failing to sync again. I'm now on Monterey v 12.5.1. I may need to resort to running Outlook on my Mac for calendar. Come on Apple!!!

This is now broken again on 12.5.1 for me as well. Very frustrating! It was working on prior versions

Has anyone updated to MacOS 12.6 any seen if that fixes the issue?

sorry for the dumb question .. how/where do you use those command lines ?

How on earth do I do this? This is a foreign language to me! thanks for your help!

Yes, I still have the problem on 12.6. Very frustrating

I'm having the same problem...annoying that the fixes only work for a short time...strange that this only started a few weeks ago on my MacBook (M1), although I always perform the updates...

Still not fixed on 12.6.1 (Monterey), and I've seen reports of it on Ventura this week..

Same here... 12.6 and agenda sync from MacBook to Exchange Server still quits after a while. Other iOS devices seem to keep syncing (iPhone) strangely enough. I have changed the refresh interval in calendar settings from 'Push' to 'Every minute'. Curious to see if that works for now... A normal restart of my MacBook seems to do the trick as well (although temporarily I guess). Apple needs to fix this! All our employees work with a Macbook and an office 365 account for mail and calendar.

The problem persists in 12.6.

This works here as well:

launchctl stop com.apple.CalendarAgent
launchctl start com.apple.CalendarAgent

I have the idea to automate these commands and have them run once per hour. In my search I came across launchd, but I am not an expert and have not been able to implement it successfully. Does anyone know how to do this and could post a step by step guide?

Confirming that I still have this issue in 12.6 :(