SOLVED

Migrated user mailbox was disabled on-premises

%3CLINGO-SUB%20id%3D%22lingo-sub-95442%22%20slang%3D%22en-US%22%3EMigrated%20user%20mailbox%20was%20disabled%20on-premises%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-95442%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20a%20hybrid%20environment%20and%20one%20collegue%20by%20mistake%20performed%20the%20disable%20action%20for%20a%20user%20mailbox%20on%20the%20exchange%20on-premises%20server%2C%20this%20user%20mailbox%20was%20already%20migrated%20to%20exchange%20online.%20We%20still%20see%20the%20mailbox%20in%20exchange%20online%20but%20the%20primary%20smtp%20address%20has%20change%20from%20user%40domain.com%20to%20user%40domain.onmicrosoft.com%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20mailbox%20is%20no%20longer%20visible%20at%20the%20exchange%20server%20on%20premises.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20a%20way%20to%20role%20back%20the%20action%20performed%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eregards.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-95442%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdmin%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHybrid%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-364809%22%20slang%3D%22en-US%22%3ERe%3A%20Migrated%20user%20mailbox%20was%20disabled%20on-premises%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-364809%22%20slang%3D%22en-US%22%3E%3CP%3EMassive%20thanks%20for%20this%20Andy%2C%20saved%20me%20a%20lot%20of%20heartache%20and%20investigation%20over%20internet.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-251157%22%20slang%3D%22en-US%22%3ERe%3A%20Migrated%20user%20mailbox%20was%20disabled%20on-premises%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-251157%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F2798%22%20target%3D%22_blank%22%3E%40Carlos%20Gomez%3C%2FA%3E%26nbsp%3BI%20had%20the%20same%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-95519%22%20slang%3D%22en-US%22%3ERe%3A%20Migrated%20user%20mailbox%20was%20disabled%20on-premises%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-95519%22%20slang%3D%22en-US%22%3EThanks%20Andy%2C%3CBR%20%2F%3E%3CBR%20%2F%3ELooks%20that%20we%20are%20good%20now%20after%20follow%20your%20suggestion.%3CBR%20%2F%3E%3CBR%20%2F%3Eregards.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-95518%22%20slang%3D%22en-US%22%3ERe%3A%20Migrated%20user%20mailbox%20was%20disabled%20on-premises%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-95518%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Andy%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECorrect%2C%20AD%20user%20is%20intact%20and%20mailbox%20data%20looks%20to%20be%20also%20intact%20in%20the%20cloud.%20I'll%20test%20your%20solution%2C%20our%20goal%20is%20to%20not%20loose%20data%20of%20the%20user%20mailbox%20and%20be%20able%20to%20see%20the%20remote-mailbox%20on%20the%20onpremises%20server.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'll%20update%20soon.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-95506%22%20slang%3D%22en-US%22%3ERe%3A%20Migrated%20user%20mailbox%20was%20disabled%20on-premises%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-95506%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20mean%20they%20disabled%20the%20remotemailbox%20on-prem%2C%20right%3F%20But%20the%20AD%20account%20is%20intact%3F%3C%2FP%3E%3CP%3EYou%20can%20always%26nbsp%3Bre-enable%20it%20on-prem%20in%20that%20case.%3C%2FP%3E%3CP%3EEnable-RemoteMailbox%20%3CUSERNAME%3E%20-RemoteRoutingAddress%20username%40%3CTENANT%3E.mail.onmicrosoft.com%3C%2FTENANT%3E%3C%2FUSERNAME%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThen%20set%20the%20SMTP%20addresses%20as%20required%20on%20the%20remote%20mailbox%20as%20required%20and%20wait%20or%20force%20the%20AADConnect%20sync%20to%20365...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-95491%22%20slang%3D%22en-US%22%3ERe%3A%20Migrated%20user%20mailbox%20was%20disabled%20on-premises%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-95491%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Carlos%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20you%20disable%20the%20mailbox%20you%20have%20to%20recover%20the%20user%20associate%20with%20that%20mailbox.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20you%20user%20source%20is%20AD%20you%20need%20to%20have%20Recicle%20Bin%20activated%20before%20that%20deletion%2C%20if%20you%20don't%20have%20the%20recicle%20bin%2C%20you%20have%20to%20create%20a%20new%20user%20and%20then%20reconnect%20the%20mailbox.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20article%20can%20help%20you%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fdn186233(v%3Dexchg.160).aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fdn186233(v%3Dexchg.160).aspx%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Contributor

Hi,

 

We have a hybrid environment and one collegue by mistake performed the disable action for a user mailbox on the exchange on-premises server, this user mailbox was already migrated to exchange online. We still see the mailbox in exchange online but the primary smtp address has change from user@domain.com to user@domain.onmicrosoft.com

 

The mailbox is no longer visible at the exchange server on premises.

 

Is there a way to role back the action performed?

 

regards.

6 Replies
Highlighted

Hi Carlos,

 

If you disable the mailbox you have to recover the user associate with that mailbox.

 

If you user source is AD you need to have Recicle Bin activated before that deletion, if you don't have the recicle bin, you have to create a new user and then reconnect the mailbox.

 

This article can help you https://technet.microsoft.com/en-us/library/dn186233(v=exchg.160).aspx

Highlighted
Best Response confirmed by Carlos Gomez (Contributor)
Solution

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

 

Highlighted

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.

Highlighted
Thanks Andy,

Looks that we are good now after follow your suggestion.

regards.
Highlighted

Thanks @Carlos Gomez I had the same issue.

Highlighted

Massive thanks for this Andy, saved me a lot of heartache and investigation over internet.