Office 365 Migration free/busy detail


I'm currently in the middle of an Office 365 migration from exchange 2010.
I have started to test my first batch of migrated users, but have found when a Cloud users tries to see the free/busy details of an on-prem user the information is not available the Outlook error is 'The recipient's mailbox server could not be contacted'

I have checked the IIS logs and can't see any POST logs,
I have used the PowerShell to set the TargetSharingEpr to the URL that  bypasses the load balancer (

I have test Autodiscover on
the final error is
Checking for account settings after domain redirection
       We were unable to get account settings after a domain redirection.
      Additional Details
The Microsoft Connectivity Analyzer doesn't support multiple domain redirections. Please check that your redirections aren't looping.
Elapsed Time: 0 ms.

Does anyone have any suggestions?
Ben SAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

It may be due to autodiscovery configuration. Did you configure autodiscovery to point to the o365 tenant? it should point to the onprem Exchange
More details here:

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Amit KumarCommented:
I agree with Michelangelo
Ben SAuthor Commented:

It's currently to o365,
should I update the cname or can I use PowerShell?

Amit KumarCommented:
If it is in hybrid mode and still users are homed on Exchange On-Prem then you must configure Autodiscover URLs to exchange On-prem with best practices. This will be done by changing DNS records pointing in your DNS registrar.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.