Fix External Email Delivery to Exchange Online Public Folders
Question details
Determine how to restore external email delivery to mail-enabled public folders after mailboxes move to Exchange Online.

- Product
- Microsoft Exchange Online and Exchange Server public folders
- Device & OS
- not provided
- Scenario
- Users migrated from on-premises Exchange to Exchange Online in a non-hybrid environment, while public folder delivery needs to continue.
- Observed behavior
- External messages to mail-enabled public folders are rejected, and senders receive non-delivery reports.
Identify where the public folders are hosted and obtain a complete non-delivery report, including its error code. Have the folder's email address and public folder path available, along with an administrator account authorized to manage Exchange public folders.
Migrate public folders to Exchange Online and allow external senders
Use this approach when all mailboxes are in Exchange Online and the public folders are still hosted on-premises.
Exchange Online mailboxes may not be able to access on-premises public folders directly in a non-hybrid environment. Migrating the folders can place them alongside the mailboxes, but external delivery also depends on the mail-enabled folder's sender restrictions and permissions.
In the Exchange admin center, identify the public folders and their mail addresses. Review Microsoft's public folder migration documentation for your Exchange Server version, prerequisites, and migration batch procedure.
Follow Microsoft's documented batch migration procedure to move the public folders to Exchange Online. Complete the migration and verify that the required folders and mail-enabled addresses are present.
Connect to Exchange Online PowerShell and run Get-MailPublicFolder -Identity 'folder@example.com' | Format-List RequireSenderAuthenticationEnabled. If external senders should be allowed and the value is True, run Set-MailPublicFolder -Identity 'folder@example.com' -RequireSenderAuthenticationEnabled $false.
Run Get-PublicFolderClientPermission -Identity '\FolderPath' and check the Anonymous entry for CreateItems. If an Anonymous entry exists without that permission, use Set-PublicFolderClientPermission -Identity '\FolderPath' -User Anonymous -AccessRights CreateItems; if no entry exists, use Add-PublicFolderClientPermission with the same parameters.
Send a message from an external email account to the folder's address. Check the folder for the message and review any new non-delivery report if the test fails.

Investigate non-delivery reports for folders that remain on-premises
Use this approach if the public folders have not been migrated or external delivery still fails after migration.
Work with Office files using WPS Office
WPS Office is a free, lightweight Office alternative with a familiar interface and support for common Microsoft Office formats, making it easier to move existing documents into your workflow. It does not manage Exchange public folders or fix mail delivery.

Frequently Asked Questions
Can an Exchange Online mail-enabled public folder receive external email?
Yes. The folder must be mail-enabled, its delivery restrictions must allow unauthenticated senders, and the Anonymous user must have the appropriate permission to create items in the folder.
How do I check whether a public folder requires authenticated senders?
In Exchange Online PowerShell, run Get-MailPublicFolder -Identity 'folder@example.com' | Format-List RequireSenderAuthenticationEnabled. A value of True means the mail-enabled folder requires sender authentication.
Do I need to migrate on-premises public folders after moving mailboxes to Exchange Online?
If all mailboxes are in Exchange Online, migrating the public folders is a recommended approach. In a non-hybrid environment, users may not be able to access on-premises public folders directly. Review Microsoft's migration prerequisites and batch procedure for your Exchange Server version.
What should I check if external messages still bounce?
Obtain the complete non-delivery report and review its error code and reporting server. Then check the folder address, sender restrictions, Anonymous permissions, and mail flow configuration in Exchange.




