As many of you might know, we move mailboxes between different databases in the cloud to balance the load. This is done daily through local move requests automatically triggered by our Mailbox Load B...
Updated Mar 11, 2020
Version 1.0
Blog Post
Mirela, thank you for the answer but the issue is not that we are hunting for a better server, is that various mailbox corruption issues are fixed in the move processes. I don't think we much care in which data center a user resides, and if we had a way to run a mailbox health check and correction process outside the mailbox move process we would not need this particular cmdlet. Multiple types support engineers have suggested this exact process, usually after days of debugging while the user is broken and can not get work done. In one such occasion we had a suicide hotline mailbox stuck for about a week while waiting on an answer, via premium support, and a mailbox move fixed the issue. I hope you understand that this is not the sort of thing we can wait on.