Menu Close

[Quick Fix] How To Solve Mailbox Exists On-premise And Office 365

The strategies in this post help you how to solve mailbox exists on-premise and office 365.

Here is the sample user who has a mailbox in on-premise.

How to solve mailbox exists on-premise and office 365

The same user also has a mailbox in cloud.

office 365 mailbox

There are a couple of options to get rid of the issue. They are listed below.

Option 1: Remove Exchange Online License

  • Remove the Exchange online license.
  • The object will appear as mail user after the Exchange Online license is removed.
microsoft office 365
  • Now, the mailbox available in on-premise will be migrated to Exchange online and assign the necessary license.
  • Once the mailbox appears ok, perform the mailbox restore request to merge items from the soft-deleted mailbox to the active mailbox.
outlook office 365

Option 2: Delete the Azure Active Directory account

  • As you are aware, exchange online mailbox is associated to an Azure Active Directory account.
  • When the Azure Active Directory account is removed, the mailbox in cloud moved to soft-deleted and not appear as active.
mailbox exists on-premise and office 365
  • After sync, the on-premise account will sync to Azure Active Directory again as a mail user.
solve mailbox exists on premise and office 365
  • The mailbox needs to be migrated to Exchange Online and assign the appropriate license.
  • Once it is done, perform the mailbox restore request to merge data from the soft-deleted mailbox to the active mailbox.

For more information on mailbox exists on-premise and office 365, check Microsoft website.

Want to improve your Exchange Online experience for better productivity? Check out the tips and tricks mentioned here.

Now I’d like to hear from you:

Which options from today’s post are you going to try first? or maybe you have a question about something that I covered.

Either way, let me know by leaving a comment below right now.

Related Posts

Leave a Reply

Your email address will not be published. Required fields are marked *