Email Migration

Fix Cannot Create an Exchange Public Folder Migration Endpoint

Tauseeq Magsi Sep 28, 2026 868 views

Question details

User encounters an error stating a recipient with a specified mailbox GUID cannot be found when attempting to create an Exchange Public Folder migration endpoint.

Fix Cannot Create an Exchange Public Folder Migration Endpoint

Product: Microsoft Exchange
Device & OS: not provided
Scenario: Creating an Exchange Public Folder migration endpoint to transfer data from on-premises to Exchange Online.
Observed behavior: The system fails to create the migration endpoint and returns a mailbox GUID not found error, typically due to incomplete Active Directory replication or an incorrect Exchange GUID.

Before you start

Ensure you have administrative privileges in your Exchange Admin Center and that your on-premises servers have a stable connection to Exchange Online before modifying migration batches.

Solution 1Recommended

Wait for Active Directory Replication and Verify Mailbox GUID

Allow Active Directory changes to propagate and ensure the target public folder mailbox has the correct ExchangeGUID configured.

Incomplete Active Directory replication is the most common cause of this error. When changes are made, they need time to sync across all domain controllers before Exchange can locate the specified GUID.

Allow Time for Replication

Wait for your Active Directory replication cycle to finish completely. This can take anywhere from 15 minutes to a few hours depending on your network topology.

Open Exchange Management Shell

Launch the Exchange Management Shell on your on-premises Exchange server as an administrator.

Verify the ExchangeGUID

Run the command 'Get-Mailbox -PublicFolder <YourMailboxName> | Format-List ExchangeGUID' to verify that the target public-folder mailbox has the correct GUID assigned.

Wait for Active Directory Replication and Verify Mailbox GUID

Replication Time: You can manually force Active Directory replication using the 'repadmin /syncall' command if you do not want to wait for the automatic sync cycle.

Solution 2

Recreate the Migration Batch with SourcePFPrimaryMailboxGuid

If waiting for replication does not resolve the issue, recreate the migration batch and explicitly specify the primary mailbox GUID.

Free Microsoft Office alternative

Boost Your Productivity with WPS Office

While managing complex server migrations and Exchange configurations, keep your daily documentation running smoothly. WPS Office provides a free, lightweight, and powerful alternative to Microsoft Office, ensuring seamless workflow transitions without the heavy subscription costs.

Fully compatible with Microsoft Office file formats (.docx, .xlsx, .pptx).Lightweight installation ensures fast startup and smooth operation on any device.Familiar, intuitive user interface requires zero learning curve for Office users.Built-in PDF editing tools for comprehensive and efficient document management.

microsoft office alternative - wps office

Frequently Asked Questions

How long does Active Directory replication typically take to resolve the GUID error?

Active Directory replication can take anywhere from 15 minutes to several hours, depending on the size of your network, the number of domain controllers, and your specific replication topology settings.

How do I find the ExchangeGUID for a public folder mailbox?

You can retrieve the ExchangeGUID by running the command 'Get-Mailbox -PublicFolder <MailboxName> | Format-List ExchangeGUID' in the Exchange Management Shell on your on-premises server.

Why is the SourcePFPrimaryMailboxGuid parameter necessary for the migration batch?

This parameter explicitly tells Exchange Online which on-premises public folder mailbox to connect to during the migration, bypassing potential autodiscover or replication delays that typically trigger the 'GUID not found' error.

Migration & Recovery