This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(147.20000000000002, 62%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EL%3C/text%3E%3C/svg%3E)
Hello. We have migrated most of our users from exchange 2016 to exchange online using the online migration tool and will be running as a hybrid.
We have a handful of users where their online mailbox has provisioned but the account has errored and so we now have two mailboxes. One on premise (received external emails and cloud receives all internal emails). We know the error was created as added the exchange license in the wrong order.
I now wish to delete the online account to start the migration again and sync the emails, users know they will lose all exchange online emails and have exported their online calendar.
I am off-boarding the users to return to MailUser status which will then allow me to remove the exchange license and start the migration again.
I've run into an issue with my first attempted user and wonder if anyone can offer some assistance?
Error: RecipientNotFoundPermanentException: Cannot find a recipient that has mailbox GUID 'XXXXX'
When I check powershell I get the online GUID results fine.
When I run on DC exchange man shell:
Get-remotemailbox useremail | format-list ExchangeGUID
It returns:
The operation couldn't be performed because object 'user' couldn't be found on 'DOMAIN'.
I then look up msExchGUID in AD - its not the same. So try and set it but as the user can't be found its impossible.
I then read I needed to enable remote mailbox - Enable-RemoteMailbox USERNAME -RemoteRoutingAddress USER@snhgov.mail.onmicrosoft.com - I tried this with the result:
This task does not support recipients of this type
I'm now stuck on what to do, is anyone able to offer some assistance. I hope I don't run into new issues on each user I try to regress back to Mailuser.
Thanks for reading.
Do you mean that you have two mailboxes for each users? One on Exchange online (Create by enable license), another on Exchange on-premises? Which mailbox do you want to keep data?
Hello. Thanks for reaching out. Yes, that's correct. I wish to keep the on-premise mailbox and wipe the cloud mailbox so I can start the migration process again, in the hope all the on premise mail will be sync'd over to the cloud.
I have tried Set-User Jon@Company portal .com -PermanentlyClearPreviousMailboxInfo which would be great if it worked, I receive a message saying it completed but no settings were changed. The user remains as a UserMailbox, when I want to change him to MailUser.
Ok, then I would suggest you check whether mailbox show in Exchange on-premises admin center. "Office 365" or "mailbox"
You can also check from EMS, Check to see if the mailbox can be checked by the Get-Mailbox or Get-RemoteMailbox command.
It could used to check the status for Exchange on-premises mailbox.
Any update about this thread now? Where is this mailbox really hosted?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(300.8, 41%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMF%3C/text%3E%3C/svg%3E)
Check for an ArchiveGUID on the EXO mailbox, and then add that to the RemoteMailbox on the Exchange Server.
Set-RemoteMailbox <alias> -ArchiveGUID <value>
You have to disable the on-prem mailbox first using on-prem Powershell
disable-mailbox <user>
Then enable the remote mailbox
https://blog.expta.com/2016/05/creating-remote-mailbox-in-exchange.html
No need to offboard the ExO mailbox, just disable the duplicate on-prem mailbox, then enable as a remote mailbox and let it sync to Azure.
Thanks for your quick response, David.
The emails from on-prem haven't been syncd, so users have lost their history - which is not satisfactory. This is why I want to start the syncing process again by kicking off the migration process.
I think your suggested process above wouldn't sync the on prem mailbox items - is my understanding correct? What's your thoughts, what would you do?
Ok, if you want to completely trash the ExO mailbox and keep the on-prem one to be moved later, follow this:
Keep in mind, this will perm del their ExO mailbox and its not recoverable so export out to a pst anything in Exo you want to keep
Set-User Jon@contoso.com -PermanentlyClearPreviousMailboxInfo
I tried this and it didn't work. I managed to get a phone call with MS as this is an open ticket, they advised this method doens't work anymore.
They wanted me to delete the MSOL user (move to non sync OU, remove MSOL, move back to syncing OU) which I did to a test user but it removes all M365 account details, membership, OneDrive, OneNote ect. So trying to avoid this and find an alternative. I figured as I want the end result to get the user back to Mailuser offboarding would work. Or if there is a quick and easy like you've suggested - even better.
You got some bad advice from support I think. It still works - havent heard or seen anything to the contrary.
What exactly didnt work?
Just tried this, its run. I did a DirSync but still says MailUser so not available for me to select in the migration process to sync emails.
