Office 365 users can’t see free/busy of on-premises users

The past few days I was working on making an on-prem Exchange Server 2013 SP1 environment hybrid with the Office 365 tenant. You would expect that running the Hybrid Configuration Wizard (HCW) would be it, after setting all the requirements as they should.

Unfortunately after running the HCW, Office 365 mailboxes couldn’t access free/busy information of on-prem mailboxes. The other way round was functional. Enter troubleshooting mode! I will spare you the whole story and summarize it to the basics.

I did get an AutoDiscover error after finishing the HCW the first time, but subsequent runs did not give me the error:

Office 365 was unable to communicate with your on-premises Autodiscover endpoint.  This is typically due to incorrect DNS or firewall configuration.  The Office 365 tenant is currently configured to use the following URL for Autodiscover queries from the Office 365 tenant to the on-premises organization https://autodiscover.contoso.com/ autodiscover/autodiscover.svc/WSSecurity. See the following article for further information: http://go.microsoft.com/fwlink/p/?LinkId=275838

Inspecting the environment also didn’t show up any issues and the Exchange Remote Connectivity Analyzer also did not show any issues. Not with AutoDiscover and not with the Exchange Web Services (EWS). Both crucial in these endeavors. I found some posts that setting WSSecurityAuthentication on the AutoDiscover and EWS virtual directory should be True and that even if the value is already set to True reapplying it would possibly help. Unfortunately not for me.

Running Test-OrganizationRelationship on the “On-Prem to O365” object did show some errors, but after consultation probably weren’t the cause of this issue. However, when running the same test on the “O365 to On-prem” object (using remote PowerShell to the Office 365 tenant), the test failed on AutoDiscover (excerpt):

STEP 3 of 4: Requesting delegation token from the STS…

RunspaceId  : 2a0844db-1337-4b35-993b

Identity    :

Id          : AutodiscoverServiceCallFailed

Status      : Error

Description : The Autodiscover call failed.

IsValid     : True

ObjectState : New

Terminating execution. Autodiscover service call failed.

This error prompted me to perform an IISreset on all on-prem Exchange servers, even tho ExRCA showed everything was fine. After finishing, I ran the OrganizationRelationship test on “O365 to On-prem” again and this time it completed successfully! Checking with my O365 mailbox now showed Free/Busy information of on-prem mailboxes. Victory!

Lesson learned: Have you tried turning it off and on again?

Despite the fact I resolved it myself: thank you to all that tried to help me!

Leave a Reply

Your email address will not be published. Required fields are marked *