Forum Discussion
Migrate on-premise mailboxes to existant online users
You can remove the Exchange license and wait for the mailbox to be deprovisioned. And follow the steps here: https://techcommunity.microsoft.com/t5/exchange-team-blog/permanently-clear-previous-mailbox-info/ba-p/607619
You can remove the Exchange license and wait for the mailbox to be deprovisioned. And follow the steps here: https://techcommunity.microsoft.com/t5/exchange-team-blog/permanently-clear-previous-mailbox-info/ba-p/607619
I have an advance, I could validate the connector and send emails to on-premise mailboxes.
I was checking accepted domains configuration and I saw that the public domain was configured as Authoritative in Exchange Online console, I changed it to Internal redirection, and after that I could send emails to the on-premise mailboxes.
Because of that I'm wondering why HCW configured the accepted domain of Exchange Online as Authoritative.
Thanks Vasil, I was doing a test lab for these situation, having mailboxes before the migration because of the use of the Teams Exploratory free subscription the a lot of customer choose to use.
I followed the article you gave me and the command worked really fine, I could do the mailbox migration without any issue.
But know, I'm having another problem that I do not know if is because the fact that there were mailboxes created in both sides, on-premise and cloud. I cannot send emails to on-premise mailboxes from this migrated mailbox, I'm receiving the error 550 5.1.10 RESOLVER.ADR.RecipientNotFound.
First, I realized that connectors were not created by HCW using minimal hybrid configuration, but when I rerun it choosing the full hybrid option, the connectors were created. And I beleived that that was the reason, but no, i'm still receiving the same 550 error trying to send an email to an on-premise mailbox, and the same error when I want to validate the connector.
