This user's on-premise mailbox hasn't been migrated to Exchange online ERROR

%3CLINGO-SUB%20id%3D%22lingo-sub-1103936%22%20slang%3D%22en-US%22%3EThis%20user's%20on-premise%20mailbox%20hasn't%20been%20migrated%20to%20Exchange%20online%20ERROR%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1103936%22%20slang%3D%22en-US%22%3E%3CP%3EOn%20a%20client%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20a%20newly%20hybrid%20setup%20for%20office%20365%2C%20users%20were%20already%20migrated%20and%20synced%20but%201%20user%20was%20getting%26nbsp%3B%20the%20error%3A%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20user's%20on-premise%20mailbox%20hasn't%20been%20migrated%20to%20Exchange%20online.%20The%20exchange%20online%20mailbox%20will%20be%20available%20after%20the%20migration%20is%20completed%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Elicense%20is%20applied%2C%20is%20there%20anyway%20to%20bypass%20this%20just%20to%20have%20a%20mailflow%20running%20even%20on%20the%20cloud%20and%20a%20mailbox%20provisioned%20for%20this%20user%20so%20we%20can%20import%20the%20pst%20file%20from%20the%20on-prem%20via%20outlook%20app%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1103936%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1104435%22%20slang%3D%22en-US%22%3ERe%3A%20This%20user's%20on-premise%20mailbox%20hasn't%20been%20migrated%20to%20Exchange%20online%20ERROR%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1104435%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F515751%22%20target%3D%22_blank%22%3E%40haru_erick%3C%2FA%3E%26nbsp%3Bno%2C%20if%20you%20try%20and%20work%20around%20that%20the%20AD%20attributes%20will%20be%20messed%20up%20for%20that%20user%2C%20you%20may%20not%20be%20able%20to%20manage%20the%20mailbox%2C%20or%20they%20could%20even%20end%20up%20with%202%20mailboxes.%3C%2FP%3E%3CP%3EYou%20need%20to%20find%20out%20why%20it%20has%20not%20been%20migrated%20and%20then%20migrate%20it%20properly.%20You%20don't%20need%20to%20use%20PST%20files%20if%20you%20do%20a%20hybrid%20migration.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1105477%22%20slang%3D%22en-US%22%3ERe%3A%20This%20user's%20on-premise%20mailbox%20hasn't%20been%20migrated%20to%20Exchange%20online%20ERROR%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1105477%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F431307%22%20target%3D%22_blank%22%3E%40CloudHal%3C%2FA%3E%26nbsp%3B%20Thanks%20for%20the%20response%2C%20will%20let%20client%20know%2C%20thx%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

On a client:

 

We have a newly hybrid setup for office 365, users were already migrated and synced but 1 user was getting  the error: 

 

This user's on-premise mailbox hasn't been migrated to Exchange online. The exchange online mailbox will be available after the migration is completed

 

license is applied, is there anyway to bypass this just to have a mailflow running even on the cloud and a mailbox provisioned for this user so we can import the pst file from the on-prem via outlook app?

 

 

2 Replies
Highlighted

@haru_erick no, if you try and work around that the AD attributes will be messed up for that user, you may not be able to manage the mailbox, or they could even end up with 2 mailboxes.

You need to find out why it has not been migrated and then migrate it properly. You don't need to use PST files if you do a hybrid migration.

Highlighted

@CloudHal  Thanks for the response, will let client know, thx