Exchange Connection Problems

Fix Exchange 2016 Hybrid Public Folders Not Appearing in Office 365

Nimra MalikNimra Malik Nov 18, 2026 869 views

Question details

An administrator needs to make on-premises Exchange 2016 public folders accessible to Office 365 users in a hybrid deployment.

Fix Exchange 2016 Hybrid Public Folders Not Appearing in Office 365
Product
Microsoft Exchange Server 2016 and Exchange Online
Device & OS
not provided
Scenario
Modern public folders are hosted on-premises while user mailboxes have been migrated to Exchange Online.
Observed behavior
The on-premises public folders do not appear for Office 365 users after the hybrid public folder configuration and synchronization scripts have been run.
Before you start

Identify an affected Exchange Online mailbox and the names of the on-premises public folder mailboxes. Make sure you have administrative access to Exchange Online PowerShell and the on-premises Exchange Management Shell.

Solution 1Recommended

Verify the remote public folder configuration and synchronized objects

Use this check to confirm that Exchange Online can identify the on-premises public folder mailboxes.

1
Check the remote configuration

Connect to Exchange Online PowerShell and run Get-OrganizationConfig | Format-List *remote*. Verify that the on-premises public folder mailboxes are listed in the remote public folder mailbox configuration.

2
Find the synchronized mail users

In Exchange Online PowerShell, run Get-MailUser -Identity '<public folder mailbox name>' for each expected public folder mailbox. Confirm that the corresponding synchronized objects are present as mail users.

3
Investigate missing objects

If an expected mail user is missing, review the public folder synchronization script results and directory synchronization status in your hybrid environment. Correct any reported synchronization errors, then repeat the Exchange Online checks.

4
Test an affected mailbox

Open Outlook with an affected Exchange Online mailbox and check the Folders view for the on-premises public folders. Test another migrated mailbox to determine whether the issue affects one user or multiple users.

Verify the remote public folder configuration and synchronized objects
Free Microsoft Office alternative

Work with Office documents using WPS Office

WPS Office is a free, lightweight alternative with a familiar interface for working with Microsoft Office files. It can help users transition to a different document suite, but it does not fix Exchange hybrid public folder configuration or provide Outlook public folder access.

Open and edit documents that users may share after retrieving them from public foldersWork with Microsoft Office formats including DOCX, XLSX, and PPTXUse a familiar interface for an easier transition from Microsoft OfficeCreate and edit files with a free, lightweight office suite
microsoft office alternative - wps office

Frequently Asked Questions

Where can I check whether Exchange Online recognizes the on-premises public folder mailboxes?

In Exchange Online PowerShell, run Get-OrganizationConfig | Format-List *remote* and check whether the remote public folder mailbox configuration lists the expected on-premises mailboxes.

How do I verify that a public folder mailbox object synchronized to Office 365?

In Exchange Online PowerShell, run Get-MailUser -Identity '<public folder mailbox name>'. The corresponding synchronized object should appear as a mail user.

What does an Unknown user type in public folder permissions mean?

An Unknown entry can indicate a problematic permission that may affect access. Run Get-PublicFolderClientPermission -Identity '<public folder path>' in the on-premises Exchange Management Shell and review the User Type values.

Why should I check the X500 address of a migrated mailbox?

The Exchange Online mailbox should have an X500 address containing the on-premises account's LegacyExchangeDN. Compare the on-premises LegacyExchangeDN with the online mailbox's EmailAddresses property in PowerShell.

Does an unresolvable on-premises OWA address prove the firewall is blocking public folders?

No. It is a connectivity clue, not proof of the cause. Check DNS resolution, Exchange endpoint reachability, and firewall or publishing rules, then test access again in Outlook.