Recently ran into an issue where an organization could not view public folders within Outlook once users where moved to Office 365 (Exchange Online).
The organization was running Exchange 2013 on-premises. They had already converted public folders to public folder mailboxes. We had setup ADFS with Office 365 and had completed an Exchange 2013 Hybrid implementation. We had migrated a few test accounts to Office 365 and everything appeared to be working perfectly – until we realized public folders were not showing in Outlook.
Once public folders are migrated to public folder mailboxes, they are modern public folders and are now compatible with Office 365. So therefore we don’t need a proxy mailbox as specified within the Technet article. That said, we needed to do two things. First, we have to make Office 365 aware of the public folder mailboxes that we have with the on-premise Exchange 2013. We need to synchronize the on-premise public folder mailbox objects to Office 365/Exchange Online. These mailbox objects will then exist as mail enabled user objects in Office 365. This synchronization should occur through the ADFS process.
Second, we need to tell Exchange Online to use the on-premise public folders. To do so follow these steps:
- Connect to Exchange Online by using remote powershell.
- Run the following command: set-organizationconfig –PublicFoldersEnabled Remote –RemotePublicFolderMailboxes PFMailbox1,PFMailbox2,…
One caveat: The public folders will still not be available in Outlook Web App (OWA) until the public folders are migrated to Exchange Online.
Jacob Eker, PEI
When you say “…already converted public folders to public folder mailboxes” do you mean mail-enabled public folders?
Unfortunately, our engineers are extremely busy at the moment and are not able to respond to posts. Feel free to contact PEI directly if you are interested in assistance.