logo
search
Calendar Problems

Fix On-Premises Users Cannot See Microsoft 365 Free/Busy Information

Rana GarciaRana Garcia Sep 28, 2026 870 views

Question details

On-premises Exchange users are unable to view the free/busy calendar status for Microsoft 365 mailboxes in an Exchange hybrid environment.

How to Fix On-Premises Users Cannot See Microsoft 365 Free/Busy Information
Product
Microsoft Exchange Hybrid / Microsoft 365
Device & OS
not provided
Scenario
Users are trying to schedule meetings or view calendar availability across a hybrid Exchange deployment.
Observed behavior
The free/busy calendar information of Microsoft 365 users appears as unavailable, hashed out, or throws an error to on-premises users.
Before you start

Ensure that you have administrator access to both your on-premises Exchange Server and your Microsoft 365 tenant, and verify that the target users have correctly configured their default calendar sharing permissions.

Solution 1Recommended

Verify Autodiscover and Organization Relationship Configurations

Check that Autodiscover is correctly routing requests and that the organization relationship between the on-premises environment and Exchange Online is valid.

Free/busy lookup failures in a hybrid environment are often caused by misconfigured Autodiscover endpoints or broken organization relationships.

By validating the TargetAutodiscoverEpr and testing connectivity, you can identify where the cross-premises request is failing.

1
Test Autodiscover Configuration

Run the Microsoft Remote Connectivity Analyzer (ExRCA) from the Microsoft website. Select the 'Free/Busy' test to ensure the Autodiscover service is functioning correctly for the routing domain.

2
Check Organization Relationships

Log in to the Exchange admin center. Navigate to the 'Organization' tab and verify that the organization relationships exist between on-premises and Exchange Online, and that 'Free/busy access' is explicitly enabled.

3
Verify Target Autodiscover EPR

Open the Exchange Management Shell and run 'Get-OrganizationRelationship | Format-List TargetAutodiscoverEpr'. Ensure that the URL returned points to the correct Exchange Online Autodiscover endpoint.

Verify Autodiscover and Organization Relationship Configurations
Replication Time: After making changes to organization relationships or running the Hybrid Configuration Wizard, it may take up to a few hours for the new settings to fully replicate across the environment.
Free Microsoft Office alternative

Looking for a Lightweight and Reliable Office Suite? Try WPS Office

While you troubleshoot complex Exchange Server backend configurations, you might also be looking for a reliable, cost-effective office suite for your organization's daily document tasks. WPS Office provides a lightweight, highly compatible alternative to Microsoft Office.

Fully compatible with Microsoft Word, Excel, and PowerPoint file formats.Lightweight architecture ensures fast startup times even on older hardware.All-in-one suite to view, edit, and collaborate on documents seamlessly.Free core features to help reduce your organization's software licensing overhead.
microsoft office alternative - wps office

Frequently Asked Questions

Why does free/busy information only fail in one direction in a hybrid deployment?

This typically occurs if the Autodiscover record, OAuth configuration, or Organization Relationship is misconfigured on one side of the deployment (either on-premises or Exchange Online) but is functioning correctly on the other side. Each direction relies on its own set of validation checks.

Does OAuth configuration affect free/busy lookups in Exchange Hybrid?

Yes. Exchange Server uses OAuth authentication to securely request free/busy information across premises. If the intra-organization OAuth certificate is expired, missing, or improperly configured, free/busy requests will be denied and return an error.

How do I know if my Hybrid Configuration Wizard (HCW) caused the free/busy issue?

If free/busy lookup was working previously and stopped immediately after updating or re-running the HCW, the wizard may have overwritten custom organization relationship settings or failed to correctly publish the current OAuth certificate. Reviewing the HCW logs can help identify the failure point.