Update 1/20/2022: We have edited this post for clarity based on customer feedback.
Over the last few years, we have invested heavily in Microsoft Graph to enable developers to access the rich data ...
Updated Jan 20, 2022
Version 5.0
Blog Post
When our agency moved to Office 365 in 2014, there were no PFs... yet. Everything that was in a PF on-prem was converted to a shared mailbox, some with granular rights inside. Literally the day I finished the conversion, it was announced PFs were coming back. We left the content as shared mailboxes.
Since that time, we had a shared mailbox that we used for reported SPAM and other problematic e-mail. Unfortunately, it seemed to cause issues with Outlook performance when everyone tried to drop items into the mailbox, up to completely freezing the client. It was determined that a PF didn't seem to have the same experience so we created a PF to replace the mailbox (one folder instead of a whole mailbox object). That was back in 2016 if memory serves me correctly.
To this day, it is the only PF the agency has created and uses.