Today I’m going to show you on how to solve office 365 mailbox does not exist issue.
I had a painful day where a user was associated with a remote user mailbox in on-premises, but no mailbox was provisioned in Microsoft 365 but Exchange Online license was assigned. The strategies in this post will help you solve the issue.
Let’s jump right in.
In this case, the Exchange GUID needs to be updated in on-premises because it’s a hybrid environment with Azure AD Connect to sync objects.
To update the attribute, follow the below steps.
- Launch “Exchange On-Premises PowerShell“
- Update the Exchange GUID to null for the affected mailbox.
For example, Set-RemoteMailbox test2222 -ExchangeGuid 00000000-0000-0000-0000-000000000000
For more information about the Remote Mailbox, visit the Microsoft website.
- Make sure the ExchangeGUID reflects correctly in on-premises. If it is incorrectly set for some reason, follow the steps mentioned in this article.
- Wait for the changes to reflect in cloud. The object in Microsoft 365 should reflect the changes applied 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 again re-add the license and see how it goes.
Woohoo!!. The object now shows as a user mailbox in cloud. 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.