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
Thanks for the interest!
We use PFs as email collaboration tool. Mails sent to the PFs contain information relevant to more than one department, and recipients are used to handle read/unread status on an individual basis. So the PFs are in some sense distribution groups with built-in archive functionality. Our issue with Shared Mailbox is the individual read/unread status. Besides technical considerations, some workflows are proven for 15+ years, so our colleagues are familiar and comfortable with the setup.
Additionally we automatically process emails/attachments in the PF with EWS. (import in DB, calculations,…)
We are aware of Microsoft 365 Groups, but missed flexibility with subfolders and rules. We are also aware that additional functionality has been added to Groups, but we did not have time to evaluate these improvements.
Anyway, we’ve heard the signals and will reevaluate our PF workflows