Modern public folder deployment best practices

Good mention, Christian. This was a more recently discovered behavior after this part of the article series was well under way. The behavior Christian mentions is one where a destination PF mailbox has a lock put on it when moving any PF into that particular PF mailbox. This results in users being locked out of making hierarchy connections and content connections to any content that exists in the destination PF mailbox. Why is there a lock to begin with? It is a byproduct of the MRS process being used to move PFs between PF mailboxes. Normally you do not want a user accessing the mailbox in its new home until the move process has verified all content has been successfully copied. In this case however even though we're only moving a folder, the mailbox level lock is still applied. It's being investigated for improvement. For one method to lessen the impact is to prevent that destination mailbox from serving hierarchy connections (it won't help for any content residing in there). Some customers may choose to move large PFs into a net-new PF mailbox (excluded from serving hierarchy) so there is no content in there to become locked during the move.