SOLVED

Migrate on-premise mailboxes to existant online users

%3CLINGO-SUB%20id%3D%22lingo-sub-1638901%22%20slang%3D%22en-US%22%3EMigrate%20on-premise%20mailboxes%20to%20existant%20online%20users%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1638901%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3EWe%20have%20to%20migrate%20on-premise%20Exchange%202010%20mailboxes%20to%20Exchange%20Online%2C%20but%20the%20problem%20is%20that%20the%20customer%20already%20has%20created%20cloud%20users%20with%20mailboxes%20using%20the%20free%20teams%20explanatory%20license.%20Now%2C%20they%20are%20going%20to%20upgrade%20the%20license%20buying%20M365%20business%20standard%20plan.%3C%2FP%3E%3CP%3EIs%20possible%20to%20merge%20the%20on-premise%20mailboxes%20with%20the%20already%20created%20Exchange%20Online%20mailboxes%3F%3C%2FP%3E%3CP%3EExchange%20online%20mailboxes%20are%20almost%20empty%2C%20they%20only%20have%20the%20meetings%20they%20have%20arranged%20using%20Microsoft%20Teams%2C%20so%20those%20mailboxes%20are%20not%20important%20for%20the%20customer%2C%20but%20they%20want%20to%20keep%20onedrive%20and%20Teams%20data.%20Is%20possible%20to%20remove%20online%20mailboxes%20without%20deleting%20cloud%20users%20before%20the%20mailboxes%20migration%3F%20or%20What%20is%20the%20right%20way%20to%20do%20it%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1638901%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2010%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ehybrid%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1639366%22%20slang%3D%22en-US%22%3ERe%3A%20Migrate%20on-premise%20mailboxes%20to%20existant%20online%20users%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1639366%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20can%20remove%20the%20Exchange%20license%20and%20wait%20for%20the%20mailbox%20to%20be%20deprovisioned.%20And%20follow%20the%20steps%20here%3A%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fexchange-team-blog%2Fpermanently-clear-previous-mailbox-info%2Fba-p%2F607619%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fexchange-team-blog%2Fpermanently-clear-previous-mailbox-info%2Fba-p%2F607619%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1640112%22%20slang%3D%22en-US%22%3ERe%3A%20Migrate%20on-premise%20mailboxes%20to%20existant%20online%20users%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1640112%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F745174%22%20target%3D%22_blank%22%3E%40cruizmct%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3EYou%20would%20have%20to%20do%20some%20matching%20between%20on-prem%20and%20cloud.%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F2641663%2Fuse-smtp-matching-to-match-on-premises-user-accounts-to-office-365%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F2641663%2Fuse-smtp-matching-to-match-on-premises-user-accounts-to-office-365%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1644592%22%20slang%3D%22en-US%22%3ERe%3A%20Migrate%20on-premise%20mailboxes%20to%20existant%20online%20users%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1644592%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F745174%22%20target%3D%22_blank%22%3E%40cruizmct%3C%2FA%3E%26nbsp%3BI'm%20happy%20to%20see%20somebody%20else%20is%20facing%20what%20I've%20been%20facing%20repeatedly%20with%20customers%20since%20COVID-19%20(when%20everybody%20jumped%20on%20Teams%20quickly).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHere's%20an%20Exchange%20Team%20blog%20post%20about%20the%20topic%20of%20having%20a%20mailbox%20in%20both%20on-premises%20and%20in%20EXO%20at%20the%20same%20time%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fexchange-team-blog%2Fmy-user-has-a-mailbox-both-on-premises-and-in-exchange-online%2Fba-p%2F846809%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fexchange-team-blog%2Fmy-user-has-a-mailbox-both-on-premises-and-in-exchange-online%2Fba-p%2F846809%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20recommended%20solution%20from%20Microsoft%20(or%20even%20better%2C%20the%20Exchange%20team)%20is%20to%20blow%20away%20the%20on-premises%20mailbox%20and%20then%20re-enable%20the%20user%20as%20a%20Remote%20Mailbox%2C%20then%20perform%20New-MailboxRestoreRequest%20from%20EXO%20PowerShell%2C%20restoring%20the%20soft-deleted%20on-premises%20mailbox%20directly%20into%20the%20live%20EXO%20mailbox.%26nbsp%3B%20The%20main%20caveat%20is%20users%20will%20need%20to%20create%20new%20Outlook%20profiles%20because%20they%20won't%20maintain%20their%20original%20on-premises%20mailbox's%20ExchangeGuid%20through%20this%20process.%26nbsp%3B%20But%20the%20big%20benefit%20is%20that%20they%20won't%20lose%20any%20of%20their%20Teams%2C%20SharePoint%20Online%2C%20OneDrive%2C%20etc.%20metadata.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20you%20go%20this%20route%2C%20you'll%20find%20that%20the%20New-MailboxRestoreRequest's%20end%20in%20%22FailedOther%22.%26nbsp%3B%20Fortunately%20I've%20been%20through%20this%20many%20times%20now%20and%20have%20confirmed%20with%20the%20Exchange%20team%20and%20MS%20Support%20that%20the%20failure%20status%20is%20OK%2C%20as%20long%20as%20the%20Copy%20Progress%20shows%20the%20correct%20number%20of%20items%20having%20been%20copied.%26nbsp%3B%20I%20just%20(last%20Friday%20and%20over%20the%20weekend)%20had%20my%20Pull%20Request%20merged%20into%20the%20MS%20Docs%20page%20for%20this%20procedure%2C%20which%20explains%20this%20in%20more%20detail%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Ftroubleshoot%2Fmove-mailboxes%2Fmailbox-exists-exo-onpremises%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Ftroubleshoot%2Fmove-mailboxes%2Fmailbox-exists-exo-onpremises%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Hello,

We have to migrate on-premise Exchange 2010 mailboxes to Exchange Online, but the problem is that the customer already has created cloud users with mailboxes using the free teams explanatory license. Now, they are going to upgrade the license buying M365 business standard plan.

Is possible to merge the on-premise mailboxes with the already created Exchange Online mailboxes?

Exchange online mailboxes are almost empty, they only have the meetings they have arranged using Microsoft Teams, so those mailboxes are not important for the customer, but they want to keep onedrive and Teams data. Is possible to remove online mailboxes without deleting cloud users before the mailboxes migration? or What is the right way to do it?

5 Replies
Highlighted
Best Response confirmed by cruizmct (New Contributor)
Solution

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...

Highlighted
Highlighted

@cruizmct I'm happy to see somebody else is facing what I've been facing repeatedly with customers since COVID-19 (when everybody jumped on Teams quickly).

 

Here's an Exchange Team blog post about the topic of having a mailbox in both on-premises and in EXO at the same time:

https://techcommunity.microsoft.com/t5/exchange-team-blog/my-user-has-a-mailbox-both-on-premises-and...

 

The recommended solution from Microsoft (or even better, the Exchange team) is to blow away the on-premises mailbox and then re-enable the user as a Remote Mailbox, then perform New-MailboxRestoreRequest from EXO PowerShell, restoring the soft-deleted on-premises mailbox directly into the live EXO mailbox.  The main caveat is users will need to create new Outlook profiles because they won't maintain their original on-premises mailbox's ExchangeGuid through this process.  But the big benefit is that they won't lose any of their Teams, SharePoint Online, OneDrive, etc. metadata.

 

If you go this route, you'll find that the New-MailboxRestoreRequest's end in "FailedOther".  Fortunately I've been through this many times now and have confirmed with the Exchange team and MS Support that the failure status is OK, as long as the Copy Progress shows the correct number of items having been copied.  I just (last Friday and over the weekend) had my Pull Request merged into the MS Docs page for this procedure, which explains this in more detail:

https://docs.microsoft.com/en-us/exchange/troubleshoot/move-mailboxes/mailbox-exists-exo-onpremises

Highlighted

@Vasil Michev 

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.

Highlighted

@Vasil Michev 

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.