<div>
1) No specific license requirements, apart from needing a mailbox<br />
2) Depends on how you migrate them, and whether the permission entries will be preserved/mapped to the ExO mailbox users<br />
3) Depends on your needs, integrations, etc. PFs have been dead for years now, no new investments are being made there, so you might use this opportunity to move to a more modern platform. Microsoft prefers that you move them to Office 365 Groups, though those lack some basic features compared to Shared mailboxes... but again it boils down to what you need.
</div>


Service Manager

<div>
Hi Vasil,<br><br>Ok so now would be a good opportunity to move to shared mailboxes if I am reading you correctly. With that in mind then as long as a user has an O365 licence that includes Exchange they can use the shared mailbox, is that correct? What about on prem users accesing a shared mailbox online?<br><br>Cheers,<br>Paul
</div>


System Administrator

Paul Walsh

<div>
<div class="content wysiwyg-content fr-view">
Hi All,<br><br>We may be moving from Exchange 2010 on prem &nbsp;to Exchange online. We have a number of public folders, mostly are mail enabled and used for generic correspondence from outside customers. With that in mind I have a couple of questions:<br>1. Are there any specific licence requirements for using public folders. All of our users that we will be movng to O365 will have a business basic licence, will this cover it? (I know that shared mailboxes dont need a licence, but anyone who accesses them does, is this the same for public folders? I have read they require a P2 licence, is this just for the user accessing them, or per public folder?<br>2. When we migrate the public folder, will users who havent been moved online still be able to view/ interact with the public folders? Does this also work in reverse, ie. O365 users can still view/use public folders still on prem?<br>3. In general is it better/easier to migrate the public folder like for like (stay public folders in the cloud), or convert them to shared mailboxes?<br><br>Thanks for your help,<br>Paul<br><br>
</div>
</div>



Hi All,
We may be moving from Exchange 2010 on prem  to Exchange online. We have a number of public folders, mostly are mail enabled and used for generic correspondence from outside customers. With that in mind I have a couple of questions:
1. Are there any specific licence requirements for using public folders. All of our users that we will be movng to O365 will have a business basic licence, will this cover it? (I know that shared mailboxes dont need a licence, but anyone who accesses them does, is this the same for public folders? I have read they require a P2 licence, is this just for the user accessing them, or per public folder?
2. When we migrate the public folder, will users who havent been moved online still be able to view/ interact with the public folders? Does this also work in reverse, ie. O365 users can still view/use public folders still on prem?
3. In general is it better/easier to migrate the public folder like for like (stay public folders in the cloud), or convert them to shared mailboxes?
Thanks for your help,
Paul

Exchange Onlie PUblic Folders

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Office 365 is a group of software plus services subscriptions that provides productivity software and related services to its subscribers. Office 365 allows the use of Microsoft Office apps on Windows and OS X, provides storage space on Microsoft's cloud storage service OneDrive, and grants 60 Skype minutes per month. Office 365 includes e-mail and social networking services through hosted versions of Exchange Server, Skype for Business Server, SharePoint and Office Online, integration with Yammer, as well as access to the Office software. All of Office 365's components can be managed and configured through an online portal; users can be added manually, imported from a CSV file, or Office 365 can be set up for single sign-on with a local Active Directory using Active Directory Federation Services.