Email Migration

Fix Exchange Hybrid Migration Error: Recipient Is Not a Mailbox

Ayan MasoodAyan Masood Nov 20, 2026 868 views

Question details

Determine why an Exchange hybrid remote move reports that a recipient is not a mailbox and correct the recipient configuration.

Fix the Exchange Hybrid Error: Recipient Is Not a Mailbox
Product
Microsoft Exchange hybrid deployment
Device & OS
not provided
Scenario
An administrator is migrating a synchronized user with a remote move.
Observed behavior
The migration fails because the recipient is represented as a mail user rather than the mailbox required for the move. Stale mailbox attributes may be involved.
Before you start

Confirm the migration direction and whether the user should have an on-premises mailbox, a cloud mailbox, or a remote mailbox representation. Use an account with the appropriate Exchange and directory administration permissions to inspect the recipient.

Solution 1Recommended

Check the recipient type and mailbox location

Use this first to establish whether the required source mailbox exists and whether the recipient configuration matches the migration direction.

A mail user can be valid in a hybrid deployment, but a remote move requires an appropriate source mailbox. Do not remove mailbox attributes solely because a recipient is listed as a mail user.

1
Inspect the on-premises recipient

In the on-premises Exchange Management Shell, run Get-Recipient -Identity user@example.com | Format-List Name,RecipientType,RecipientTypeDetails, replacing the address with the affected user's identity.

2
Check mailbox representations

In the same shell, run Get-Mailbox -Identity user@example.com and Get-RemoteMailbox -Identity user@example.com. Check the results against the intended migration direction; a command returning no object can indicate that the corresponding representation is absent.

3
Check the cloud mailbox

Connect to Exchange Online PowerShell and run Get-Mailbox -Identity user@example.com. If the cloud mailbox was deleted, check its recovery status before creating a replacement or changing recipient attributes.

4
Review synchronization

In the Microsoft Entra admin center, open the affected user and check its synchronization status. Compare the cloud recipient with the on-premises result to identify a mismatch.

Check the recipient type and mailbox location
A source mailbox is required: If the intended source mailbox no longer exists, correcting attributes alone will not make a remote move possible. Determine whether the mailbox can be restored or whether a different provisioning or migration approach is required.
Free Microsoft Office alternative

Use WPS Office for Migration Planning Documents

WPS Office is a free, lightweight alternative for preparing migration checklists and reports. Its familiar interface and Microsoft Office format compatibility make it easy to work with existing documents, though it does not manage Exchange mailboxes or fix migration errors.

Create and update Exchange migration checklists and reportsOpen and edit Microsoft Word, Excel, and PowerPoint formats, including DOCX, XLSX, and PPTXUse a familiar interface for a smoother move from Microsoft OfficeWork with a free, lightweight office suite
microsoft office alternative - wps office

Frequently Asked Questions

Why does a remote move say the recipient is not a mailbox?

The recipient may not have the source mailbox required for the move, or its on-premises and cloud representations may not match. Check Get-Recipient, Get-Mailbox, and Get-RemoteMailbox against the migration direction.

Is a mail user always incorrect in an Exchange hybrid deployment?

No. A mail user can be a valid recipient type in some hybrid configurations. Confirm the intended mailbox location and migration direction before changing it.

Should I clear msExchMailboxGuid to fix this error?

Not automatically. The GUID can be required by an existing mailbox or remote mailbox. Verify that the attribute is stale and use a Microsoft-supported correction procedure before changing it.

What if the cloud mailbox was deleted?

Check the deleted mailbox's recovery status in Exchange Online before creating a replacement or changing attributes. If the required source mailbox no longer exists, a remote move cannot proceed until the mailbox situation is resolved.

How do I confirm that directory changes reached the cloud?

After the next Microsoft Entra Connect synchronization cycle, check the user's synchronization status in the Microsoft Entra admin center and compare the Exchange Online recipient with the on-premises Get-Recipient result.