Exchange Connection Problems

How to Fix Missing Exchange Hybrid Public Folder Contacts

Phi Hung VoPhi Hung Vo Nov 2, 2026 869 views

Question details

Users are unable to see certain public folder contacts after migrating mailboxes to Exchange Online.

How to Fix Missing Exchange Hybrid Public Folder Contacts
Product
Exchange Online
Device & OS
not provided
Scenario
Operating in an Exchange Hybrid environment post-mailbox migration to the cloud.
Observed behavior
Contacts associated with missing public folders do not appear in Exchange Online because their Organizational Unit (OU) is not synced with Microsoft 365.
Before you start

Ensure you have active administrator credentials for your on-premises Active Directory and access to your Azure AD Connect server to modify synchronization rules.

Solution 1Recommended

Include the Organizational Unit in Directory Synchronization

Update your directory sync configuration to include the specific OU where the missing public folder contacts are stored.

In a hybrid deployment, mail-enabled public folder contacts must be synchronized to the cloud for migrated users to view them properly. If the OU containing these contacts is filtered out of your Azure AD Connect sync, Exchange Online will not recognize them.

1
Identify the target OU

Locate the exact Organizational Unit in your on-premises Active Directory where the contacts for the missing public folders are currently stored.

2
Open Azure AD Connect

Log in to the server hosting Azure AD Connect and launch the synchronization settings wizard.

3
Update domain and OU filtering

Navigate to the domain and OU filtering section and check the box next to the Organizational Unit that contains the public folder contacts.

4
Run a synchronization cycle

Save the new configuration and either wait for the next scheduled sync interval or force an immediate directory synchronization using PowerShell.

5
Verify in Exchange Online

Once the sync is complete, log in to the Exchange Admin Center or use Outlook to verify that the missing contacts and public folders now appear for the migrated users.

Include the Organizational Unit in Directory Synchronization
Synchronization Complete: Depending on the size of your directory, changes might take up to 30 minutes to reflect across all Microsoft 365 services after the sync cycle finishes.
Free Microsoft Office alternative

Ensure Smooth Team Productivity with WPS Office

While resolving backend Exchange Server syncing issues, guarantee your users have a reliable desktop productivity suite. WPS Office is a high-performing, cost-effective alternative to Microsoft Office that offers full format compatibility and familiar user interfaces.

  1. 1. Download the installer: Visit the official WPS Office website and download the free installer package for your operating system.
  2. 2. Run the setup: Execute the downloaded file and follow the simple on-screen prompts to complete the installation.
  3. 3. Start creating: Open WPS Office and instantly access Writer, Spreadsheets, Presentation, and PDF tools from a single workspace.
Seamlessly open, edit, and save Microsoft Word, Excel, and PowerPoint file formats.Extremely lightweight installation, minimizing system resource usage on enterprise endpoints.Familiar ribbon-style interface that requires zero additional training for your workforce.Built-in robust PDF editing, merging, and conversion tools out of the box.
microsoft office alternative - wps office

Frequently Asked Questions

Why are public folders hidden after an Exchange Online migration?

When a user's mailbox is moved to Exchange Online, it relies on synchronized directory objects to map permissions and locations. If the on-premises contacts linked to mail-enabled public folders aren't synced via Azure AD Connect, the cloud environment cannot display those folders to the user.

How can I manually force an Azure AD sync?

You can force a sync by opening an elevated PowerShell prompt on your Azure AD Connect server and running the command: Start-ADSyncSyncCycle -PolicyType Delta.

Does this issue happen with fully cloud-based Microsoft 365 environments?

No, this specific synchronization issue only occurs in Exchange Hybrid setups where public folders remain on-premises while user mailboxes are migrated to Exchange Online.