Forum Discussion
Imthyas1979
Oct 21, 2022Copper Contributor
Office 365 users not able to see free/busy info for Exchange On-Prem mailbox
We recently migrated to O365 from On-prem except for some mailboxes and smtp mail relay from printers and SAP application. Recently we did a DR drill , where we changed the mail flow to the DR Ex...
Dan_Snape
Oct 24, 2022Iron Contributor
What exactly changed for the DR drill and have you changed it back after the DR drill and still getting the same error?
It sounds like the migration/hybrid endpoints are not able to connect to the on-premises Exchange servers. Use the get-migrationendpoint and test-migrationserveravailability in EXO PowerShell to confirm if the migration endpoint is OK.
You can troubleshoot free/busy here: https://learn.microsoft.com/en-us/exchange/troubleshoot/calendars/troubleshoot-freebusy-issues-in-exchange-hybrid
It sounds like the migration/hybrid endpoints are not able to connect to the on-premises Exchange servers. Use the get-migrationendpoint and test-migrationserveravailability in EXO PowerShell to confirm if the migration endpoint is OK.
You can troubleshoot free/busy here: https://learn.microsoft.com/en-us/exchange/troubleshoot/calendars/troubleshoot-freebusy-issues-in-exchange-hybrid
Imthyas1979
Oct 26, 2022Copper Contributor
Yes, after working with MS for nearly 1 month and no help to find what was causing the blockage, we finally reverted back the Mail Flow to On-Prem Servers and it started working.
When I say maiflow we were doing only few changes with respect to DNS both at the External DNS and Internal
So, not sure what was going on at the Network Level, which was causing the blockage as we had many times asked our Network to open and give access for the Office from the DR side as suggested by Microsoft and they said everything is open.
Anyway we had only few Resource Rooms which were connected to some Third Party Device for booking which had restrictions, so we could not move them to O365. Now ,we will try to move them to O365 and once moved we should not face these kind of issues.
Thanks Dan for suggestions as I was left without any help and as the issue was complicated and getting escalated we had to stop further troubleshooting and bring back the flow to Primary servers.
When I say maiflow we were doing only few changes with respect to DNS both at the External DNS and Internal
So, not sure what was going on at the Network Level, which was causing the blockage as we had many times asked our Network to open and give access for the Office from the DR side as suggested by Microsoft and they said everything is open.
Anyway we had only few Resource Rooms which were connected to some Third Party Device for booking which had restrictions, so we could not move them to O365. Now ,we will try to move them to O365 and once moved we should not face these kind of issues.
Thanks Dan for suggestions as I was left without any help and as the issue was complicated and getting escalated we had to stop further troubleshooting and bring back the flow to Primary servers.