{"id":167265,"date":"2024-05-17T03:35:20","date_gmt":"2024-05-17T03:35:20","guid":{"rendered":"https:\/\/www.stellarinfo.com\/blog\/?p=167265"},"modified":"2025-11-27T06:01:00","modified_gmt":"2025-11-27T06:01:00","slug":"fix-no-active-public-folder-mailboxes-were-found-error-in-exchange","status":"publish","type":"post","link":"https:\/\/www.stellarinfo.com\/blog\/fix-no-active-public-folder-mailboxes-were-found-error-in-exchange\/","title":{"rendered":"How to Fix \u201cNo Active Public Folder Mailboxes were Found\u201d Error in Exchange?"},"content":{"rendered":"

After creating the migration batch to migrate public folders from on-premises Exchange Server to Exchange Online (Microsoft 365), you run the Complete-MigrationBatch<\/strong> command to complete the migration. However, you notice that the migration batch has failed. When you run the Get-MigrationBatch<\/strong> command, it shows the migration status as Failed<\/strong>.<\/p>

Get-MigrationBatch<\/code><\/pre>
\"Get-MigrationBatch\"<\/figure>
So, to get more information on the status message of the migration batch, you run the Get-MigrationBatch<\/strong> command with the FL<\/strong> option.<\/p>
Get-MigrationBatch <batch name> | FL status.message<\/code><\/pre>
This command shows the status as failed with a message similar to the below.<\/p>
Status: FailedMessage: No active public folder mailboxes were found. This happens when no public folder mailboxes are provisioned, or they are provisioned in 'HoldforMigration' mode.<\/code><\/pre>
The error message indicates that the public folder is on hold for migration. This means that there might be an option of the public folder in question or the public folders, which is hindering the migration.<\/p>
Solutions to Resolve the “No Active Public Folder Mailboxes were Found” Error<\/strong><\/h2>
Here are some possible solutions to fix the “No active public folder mailboxes were found” error in Exchange.<\/p>
1. Check if Hold is Setup<\/strong><\/h3>
You can check if the hold is setup. For this, run the Get-OrganizationConfig<\/strong> command in the Exchange Management Shell (EMS) as given below.<\/p>
Get-OrganizationConfig | Select-Object PublicFoldersLockedForMigration, PublicFolderMigrationComplete<\/code><\/pre>
\"Get-OrganizationConfig<\/figure>
If the result is true, then it means there is a previous failed migration of public folder. So, you need to set the above option to false. For this, use the Set-OrganizationConfig<\/strong> command as given below:<\/p>
Set-OrganizationConfig -PublicFoldersLockedForMigration:$false -PublicFolderMigrationComplete:$false<\/code><\/pre>
\"Set-OrganizationConfig<\/figure>
After the command is complete, you can re-run the migration batch and then use the Complete-MigrationBatch <\/strong>command to see if the issue is resolved.<\/p>
2. Move the AD Account<\/strong><\/h3>
If you have a setup with multiple Active Directory domains and you’re migrating public folder mailboxes, then both the public folder and the user must reside in the same Active Directory Forest. You may encounter the error if the public folder mailbox and the associated user account with the public folder mailbox are not in the same Active Directory. For example, the public folder mailbox is in the primary Active Directory Forest and the associated user account is in one of the child domains.<\/p>
To resolve the issue, you can move the Active Directory account associated with the public folder mailbox to the same Active Directory domain. To do so, you can use the Active Directory Migration Tool (ADMT). Here’s how:<\/p>