This is not a situation that I have experience of, but to me is sounds like something that shouldn't happen. That is, it's a bug. So you could open a support case with Microsoft, but since the situation has been resolved, I don't think there is much they can analyse. What they can do is to give you a package that collects data that they can analyse if the issue re-occurs.
Then again, it seems like this was an unfortunate chain of events, so you may not run into these again.