Fix Exchange Online Mail-Enabled Public Folders Removed During Hybrid Sync
Question details
Users need to understand why mail-enabled public folders are removed or converted in Exchange Online during a hybrid synchronization and how to monitor or prevent it.

- Product
- Microsoft Exchange Server
- Device & OS
- not provided
- Scenario
- Running a hybrid public-folder synchronization script between on-premises Exchange environments and Exchange Online.
- Observed behavior
- The hybrid synchronization script removes or converts mail-enabled public-folder recipient objects in Exchange Online, often stripping their SMTP addresses when matching on-premises objects are missing.
Ensure you have administrative privileges for both your on-premises Exchange server and Exchange Online, and do not manually run removal cmdlets without Microsoft Support guidance.
Compare Get-MailPublicFolder Outputs Before and After Sync
Export your public folder statuses before executing the sync script so you can identify exactly which objects are modified, converted, or removed.
The synchronization script checks for duplicate mail-enabled public folders. When objects exist only in Exchange Online without a corresponding on-premises match, the script may convert them to ordinary folders and strip their SMTP addresses.
Open the Exchange Management Shell on your administrative workstation connected to your Exchange environment.
Execute the Get-MailPublicFolder cmdlet and export the results to a CSV file to capture the current state of your folders before running any sync scripts.
Execute the hybrid public-folder synchronization script as instructed in your standard migration documentation.
Run Get-MailPublicFolder again after the sync finishes, export the new results, and compare them against your original CSV file to pinpoint which mail-enabled folders were converted or removed.
Review Synchronization Logs for Removal Cmdlets
Audit the generated sync logs to confirm which removal functions were triggered automatically by the script.
Easily Analyze Your Exchange Export Logs with WPS Office
While resolving complex Exchange Server synchronization issues requires specialized administrative tools, reviewing the resulting CSV logs and exported data doesn't require an expensive software subscription. WPS Office is a lightweight, free alternative to Microsoft Office that easily handles large CSV files and spreadsheet data, making it perfect for IT administrators analyzing migration logs.
- 1. Download the Suite: Visit the WPS official website and download the free WPS Office installer.
- 2. Install WPS Office: Run the installer and follow the simple on-screen instructions to set up the software on your workstation.
- 3. Open Your Logs: Right-click your exported Exchange CSV logs, select 'Open with', and choose WPS Spreadsheet to instantly begin reviewing your sync data.

Frequently Asked Questions
Why does the hybrid sync script remove my Exchange Online public folders?
The script attempts to match your Exchange Online environment with your on-premises environment. If a mail-enabled public folder exists in Exchange Online but has no matching on-premises counterpart, the script may convert it to an ordinary folder by stripping its SMTP address during the synchronization.
Can I manually run the Remove-SyncMailPublicFolder cmdlet to clean up duplicate folders?
No. According to Microsoft's official documentation, the Remove-SyncMailPublicFolder cmdlet is designed to remove mail-enabled public-folder recipient objects from Exchange Online and should only be used when explicitly directed by Microsoft Support or specific technical documentation.
How do I know exactly which public folders were affected during synchronization?
You can find this information by reviewing the synchronization summary log generated by the script. The log explicitly details which objects were created, updated, converted, or removed during the process.
Are the contents of the public folders deleted when they are converted?
Typically, the script does not delete the actual public folder contents. Instead, it converts Exchange Online mail-enabled public folders to ordinary public folders by removing their associated SMTP addresses. Migrated users should still retain access to the folders themselves.




