When your public folder content migration to Exchange Online is complete or you create public folders for the very first time, you do not have to worry about managing many aspects of public folders. ...
Updated Jan 11, 2021
Version 2.0
Blog Post
8 MIN READ
How Exchange Online automatically cares for your public folder mailboxes (via AutoSplit)
Hazem_Embaby Thank you for your answer.
Yes, we definitly can agree that it is a huge environment. How can I check the hierarchy sync for a mailbox that is excluded from serving hierarchy? For the Hierarchyserving mailboxes, they are all on hierarchy ready $true.
I can see a lot of hierarchy sync errors in the diagnostics for Mailbox1:
Failed to resolve mail public
folder. Folder : 0000000073A217EBDDCA3A4D877A199F008AD1040100258EE17F54982A49913C835704EB1F67000048DD47
FB0000,,b56264df-bf5b-4b25-ab43-24e13afeca49,6246c9fe-79e6-4621-bcc2-e21d4805e60e
Maybe this is causing hierarchy sync issues? Before migrating the public folders, we have been in a public folder hybrid deployment with the "Sync-MailPublicFolders.ps1" script. Can it be that the objects created by the script beforehand are causing a kind of duplicate now?
Even you mention that the split will also work slowly if the sync didn't complete, I still see that the mailbox is just growing for about 200MB a day. We will soon run into new problems with that mailbox and SEV A is unfortunately just acting by increasing the qouta which is not fixing the problem itself but just the symptoms.