The administration of a hybrid deployment that connects on-premises Exchange Server with Exchange Online, enabling seamless integration and centralized control.
Hi Enzo,
Based on the symptoms you described, this looks more like a hybrid calendar-sharing/configuration issue than an Outlook client issue.
Since the reverse scenario (Exchange Online → Exchange On-Premises) works, and multiple Exchange Online users are getting the same error when accepting a calendar shared from On-Premises, I would focus on the hybrid configuration and the way the sharing invitation is being generated.
A few things I would check:
Verify the Organization Relationship in both directions. Free/busy working correctly does not necessarily mean that calendar sharing is fully supported. The Organization Relationship settings mainly control availability information, while calendar folder sharing involves additional Exchange functionality.
Check the sharing policy on the On-Premises Exchange server. Run:
Get-SharingPolicy | fl Name,Enabled,Domains
Also check which sharing policy is assigned to the affected mailbox:
Get-Mailbox ******@domain.com | fl SharingPolicy
Check the actual calendar folder permissions from the On-Premises side.
Get-MailboxFolderPermission ******@domain.com:\Calendar
Since this is a secondary calendar, make sure you are checking the exact folder path/name rather than only the default Calendar.
Check whether the invitation contains the correct Exchange sharing information. I would also inspect the original sharing invitation/message headers. In a hybrid environment, an incorrect or missing Exchange sharing endpoint/URL can result in Outlook showing the exact error you are seeing when clicking Accept.
Verify the hybrid configuration. If the environment was configured or upgraded some time ago, I would run the latest Hybrid Configuration Wizard again and verify the OAuth/hybrid configuration. In particular, check that the OAuth relationship and Exchange servers participating in hybrid are healthy.
You can also test whether the problem is specifically related to the sharing invitation by manually adding the shared calendar in Outlook using Add Calendar → From Address Book after the permissions have been assigned. If that works while accepting the invitation fails, it would strongly point toward an issue with the sharing invitation rather than the calendar permissions themselves.
One other important point: FreeBusyAccessEnabled = True only confirms that cross-premises availability is configured. It does not by itself confirm that cross-premises folder sharing/acceptance of sharing invitations is working correctly.
Given that the issue is reproducible for multiple Exchange Online users and only occurs in the On-Premises → Exchange Online direction, I would concentrate on the hybrid OAuth/sharing configuration and the sharing invitation generated by the On-Premises Exchange server rather than troubleshooting individual Outlook profiles.
If possible, I would also run Test-OAuthConnectivity from both sides and check the Exchange event logs/message tracking around the time the invitation is accepted. That should help identify whether the request is failing during authentication, autodiscover, or access to the shared folder.