Forum Discussion
Migrated user mailbox was disabled on-premises
- Aug 12, 2017
You mean they disabled the remotemailbox on-prem, right? But the AD account is intact?
You can always re-enable it on-prem in that case.
Enable-RemoteMailbox <username> -RemoteRoutingAddress username@<tenant>.mail.onmicrosoft.com
Then set the SMTP addresses as required on the remote mailbox as required and wait or force the AADConnect sync to 365...
You mean they disabled the remotemailbox on-prem, right? But the AD account is intact?
You can always re-enable it on-prem in that case.
Enable-RemoteMailbox <username> -RemoteRoutingAddress username@<tenant>.mail.onmicrosoft.com
Then set the SMTP addresses as required on the remote mailbox as required and wait or force the AADConnect sync to 365...
- CraigTodd23Mar 12, 2019Copper Contributor
Massive thanks for this Andy, saved me a lot of heartache and investigation over internet.
- Carlos GomezAug 12, 2017Brass ContributorThanks Andy,
Looks that we are good now after follow your suggestion.
regards. - Carlos GomezAug 12, 2017Brass Contributor
Hi Andy,
Correct, AD user is intact and mailbox data looks to be also intact in the cloud. I'll test your solution, our goal is to not loose data of the user mailbox and be able to see the remote-mailbox on the onpremises server.
I'll update soon.
Regards.