Today I’m going to show you on how to solve office 365 mailbox does not exist issue.
I had a painful day where in a user associated with a remote user mailbox in on-premises but no mailbox is provisioned in Microsoft 365 but exchange online license is assigned. The strategies in this post help you to solve the issue.
Let’s jump right in.
In this case, the Exchange GUID needs to be updated in on-premises because of a hybrid environment and using the AAD connect to sync objects.
To update the attribute, follow the below steps.
- Go to “Exchange on-premises PowerShell“
- Update the Exchange GUID to null on the affected mailbox
For example, set-remotemailbox test2222 -ExchangeGuid 00000000-0000-0000-0000-000000000000
For more information about Remote Mailbox, Visit the Microsoft website.
- Make sure the ExchangeGUID reflects correctly in on-premises. If not for some reason, follow the steps mentioned in this article.
- Wait for the changes to reflect to cloud. The object in Microsoft 365 should reflect the changes made in on-premises.
- As you can see, the changes synced to Microsoft 365. The next step is to remove the Exchange online license and wait for 15 minutes and then re-add the license and check the status.
Woohoo!!. The object in cloud shows as a user mailbox. The office 365 mailbox does not exist issue is fixed.
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:
Did I Miss Anything? Or maybe you have a question about something that I covered.
Either way, I’d like to hear from you. So go ahead and leave a comment below.