question

ShaunBarrett-9148 avatar image
0 Votes"
ShaunBarrett-9148 asked KyleXu-MSFT commented

Exchange Hybrid Mailbox Migration - Free / Busy

I have a bit of a strange situation. I am currently in the middle of migrating users to Office365 from an Exchange 2019 Environment.

  1. If I move a mailbox using the O365 Migration Batch Wizard, on-prem users can not see their Free / Busy information.

  2. If I move a mailbox using PowerShell (New-MoveRequest), on-prem users cannot see their Free / Busy information.

I have proven the issue only exists when I use PowerShell as I have moved one of my accounts back to on-prem and then used the migration wizard and now the Free / Busy is working as expected when an on-prem user tries to view it.

I have checked all the settings of an account that works and an account that doesn't and I can't see any obvious differences and I can't seem to find anyone who has had a similar experience. Has anyone else seen this or can point me in the right direction of how I can resolve this without moving all the accounts back to on-prem and then using the batch migration wizard (There are a lot of accounts already moved).

office-exchange-hybrid-itpro
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

KyleXu-MSFT avatar image
0 Votes"
KyleXu-MSFT answered KyleXu-MSFT commented

@ShaunBarrett-9148

The free/busy function depend on Autodiscover, Exchange on-premises Autodiscover use "-TargetAddress" to redirect request to Exchange online mailbox. So, I would suggest you have a check about this value from local AD, whether this value be rewritten by move request.

Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

If this value is incorrect, try to change it from domain.onmicrosoft.com to domain.mail.onmicrosoft.com, then force AAD Connect synchronization and check again:

 Start-ADSyncSyncCycle -PolicyType Delta

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

You are a life saviour.

Changed it and it worked instantly without even needing to do a Delta Sync. Did it anyway for completeness.

Many thanks for your help.

0 Votes 0 ·

Glad to see it works.

0 Votes 0 ·
ShaunBarrett-9148 avatar image
0 Votes"
ShaunBarrett-9148 answered

I think I may have found the issue, but not sure how I can correct it on already moved mailboxes.

The -TargetDeliveryDomain was set in the script to domain.onmicrosoft.com

I changed it to domain.mail.onmicrosoft.com and tested an account and that worked. Not sure why this would make a difference as the account still moves successfully with the domain.onmicrosoft.com without error.

Is there any way to fix accounts that have already been migrated?

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.