Here is an example of proper configuration in Exchange Online: Here is an example of proper configuration in an on-premises environment: Ensure that your public folder mailbox objects are synchronized to Exchange Online and that they have auto-discoverable primary SMTP addresses. These instructions assume that Azure Active Directory Connect synchronization services (Azure AD Connect sync) is configured to synchronize public folder mailbox objects to Exchange Online. What do you need to know before you begin? If you have Exchange Online, Microsoft 365, or Office 365 users who aren't currently represented on-premises by MailUser objects, refer to the Microsoft Knowledge Base article KB3106618 to create matching on-premises entities. This MailUser object must also be local to the target Exchange Server public folder hierarchy. To enable on-premises Exchange Server users to access public folders in Exchange Online, Microsoft 365, or Office 365, see Configure Exchange Online public folders for a hybrid deployment.Īn Exchange Online, Microsoft 365, or Office 365 user must be represented by a MailUser object in the Exchange on-premises environment in order to access Exchange Server public folders.
#Microsoft exchange public folder access how to
This article describes how to enable your Exchange Online, Microsoft 365, or Office 365 users to access public folders in Exchange 2013, Exchange 2016 and Exchange 2019 (for the rest of this article, referred to as Exchange Server). You need to resolve it before you can create new public folders in Exchange Online.Īnd while doing that don’t forget that, the best tool out there to migrate your Public Folders is the BitTitan MigrationWiz tool, so while you’re in our help center go ahead and read our migration guides and ask for a quote from our sales team.If you have Exchange 2010 public folders, see Configure legacy on-premises public folders for a hybrid deployment. Follow this excellent BitTitan article to understand why and resolve that issue. Let me know if you need help with that.īefore closing this blog post lets just discuss one last thing: creating the Office 365 Public Folder mailbox.Ī Public folder mailbox created under a Hybrid scenario, where public folder access is set to remote, will be set by default to a HoldForMigration state. The command above is what you need to run, and you can adapt if to multiple users. set-mailbox -DefaultPublicFolderMailbox 365PFMBX The answer is simple, you run a set-mailbox cmdlet, to one or multiple users, and you define the -defaultpublicfoldermailbox parameter, to a 365 Public Folder mailbox, that you of course need to have created before hand. What this does is very simple: at the mailbox level, for each mailbox, it will set the parameter “EffectivePublicFolderMailbox” to the mailbox “OnPremPFMBX”, which is a synced mailbox object from on premises, as you can see below: Now lets look at how a Hybrid Public Folder Organization Config looks like:Īs you can see above, the Public Folders in 365 are configured as remote (step 5 in the guide mentioned above), and an on premises public folder mailbox is defined as their mailbox (created in step 2 of the guide).
Some key things you should have in mind, when you’re moving your Exchange Organization from On Premises to Office 365, and Public Folders are in scope:
0 kommentar(er)
