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
Just in the last month I have had to use this command over 20 times and who knows how many times my exchange team has used it total. We had somewhere between 20 - 50 conference rooms stop working. Meetings would only show up on the organizer's calendar and not attendees calendars. After uploading countless logs over many days, Microsoft told us to move the calendars. This worked great. I also had 2 users that out of the blue could not access their email. Both outlook and owa would not let them in. I moved the mailbox and they work fine. If this command is removed, we will be opening a few sev A tickets each week.
Now for my personal view on a few things. As someone from Microsoft said above, "new software versions deploy in Exchange Online continuously, we do our best to be bug-free, but there is the occasional problem that needs to be addressed." This is very obvious to the company I work for. We have had probably 3 company wide issues in the last 2 weeks related to new software being deployed in Exchange Online. STOP! How about a quarterly update or some type of a schedule? Also from above, I keep reading that Microsoft says open tickets so we will know there are problems. Does anyone else see this as Microsoft asking it's tenants to de-bug their code?