mediavur.blogg.se

This is the Public Folder mailbox that is hosted on-premise. This is how the Public Folder mailbox user looks like from the Exchange Online perspective: PS C:\Users\p.terlisten> Get-MailUser Mailbox1

If you are using an OU filter for the AzureAD sync, make sure that the OU with the Public Folder mailbox user object is included into the sync.īut there is also a second requirement: You also need to sync the Microsoft Exchange System Objects container! This is pretty important and it is not mentioned in the docs ( Public folders in Microsoft 365, Office 365, and Exchange Online).Ĭheck if the user is synced by using the Exchange Online PowerShell.

This is not complicated, because all you need to make sure is, that the user object is synced. In order to get the access to the Public Folders working, the Public Folder mailbox object needs to be synced to AzureAD.

To our surprise the on-premise Public Folders were not visible from the migrated Exchange Online mailboxes. Something was missingĪfter setting up the Exchange Hybrid, the customer and I where able to migrate the first mailboxes to Exchange Online. The customer uses Office 365 E5 plans and he wants to move to Exchange Online, aside other O365 services like SharePoint Online, Teams etc. AzureAD Sync is running and its syncing on-premise identities to AzureAD. The customer is running a single Exchange 2016 server in a Windows Server 2012 R2 forest. I had to deal with this during a Office 365 transition project at one of my customers. And while companies are moving their stuff into the cloud, Public Folders still need to be accessed by cloud-located mailboxes.Īllowing the access from Exchange Online mailboxes to on-premise hosted Public Folders is well documented by Microsoft, but there are also some fuzz.