#PUBLIC FOLDER SYNC LICENSE#

Email-enabled public folders had their raison d'être in the past but are no longer state-of-the-art in today's world. Email Enabled Public FoldersĪ word about mail-enabled public folders. External availability of an OA endpoint is a prerequisite for legacy public folder migration to Exchange Online.įor better readability, necessary components for the publication of internal Exchange endpoints to the Internet are not included. If you have already removed the external OutlookAnywhere (OA) access to Exchange Server 2010 or have never used it before, you must configure OA access. Setting up the migration endpoint requires a user account (aka migration account) in the local Active Directory that is an Exchange organization administrator. It is created as part of setting up the migration batch using Exchange Online Remote PowerShell. An endpoint of this type cannot be created manually in the Exchange Admin Center. The legacy public folders are migrated via a dedicated public folder migration endpoint. The migration endpoint for Exchange mailboxes cannot be used to migrate legacy public folders. The path for migrating Exchange mailboxes is shown in green, the path for migrating public folders is shown in blue.Įxchange Server 2016 acts as a proxy server for migrating mailboxes and accepts Exchange Online mailbox move requests through the mailbox migration endpoint listening configured for host name. The following diagram shows the access paths for migrating mailboxes and public folders from Exchange Server 2010 to Exchange Online.

#PUBLIC FOLDER SYNC LICENSE#

It should be noted at this point that there is no installable Exchange role 'Hybrid Server.' When you use the Exchange Server license provided by Microsoft in your Office 365 tenant the operating role is 'Hybrid.'.

Exchange Online accesses the locally installed Exchange organization using this Exchange Server 2016 endpoint. Mailbox migration from a local Exchange organization to Exchange Online requires the configuration of a migration endpoint. Since this is technically a migration across organizational boundaries (so-called cross-forest migration) there are unique challenges that are addressed in this blog post. Office 365 supports the direct migration of legacy public folders from a local Exchange organization to modern public folders in Exchange Online. I outlined the challenges involved in migrating public folders within a local Exchange organization in a previous blog post. Public folders up to Exchange Server 2010 are called legacy public folders. In the previous versions of Exchange Server, public folders were replicated using their own replication technology. Exchange Server 2013 implemented a major change for public folder hierarchies and brought us modern public folders.

Public folder sync