Mailbox quota isn't validated during Exchange Server 2013 or 2016 migration

View products that this article applies to.

Symptoms

When you move a mailbox to Exchange Server 2013 or Exchange Server 2016 within the same forest from an earlier version of Exchange Server, the mailbox quota is not validated during the migration process.

Mailbox moves are completed successfully even when the mailbox size exceeds the quota limits of the target database. In this situation, users can't send or receive email messages after they're migrated to Exchange 2013 or Exchange 2016.

↑ Back to the top

Cause

This issue occurs because quota validation is skipped within the same organization when you use the New-MoveRequest cmdlet.

↑ Back to the top

Resolution

To fix this issue, install one of the following, as appropriate for your situation:

Cumulative Update 12 for Exchange Server 2013 or a later cumulative update for Exchange Server 2013.
Cumulative Update 1 for Exchange Server 2016 or a later cumulative update for Exchange Server 2016.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

More Information

After you install this update, the New-MoveRequest cmdlet performs a quota validation check and blocks mailbox migration if the size exceeds the quota limits that are specified on the target mailbox database.

When a mailbox is moved from an earlier version of Exchange to Exchange 2013, the reported mailbox size may increase 30–40 percent, as described in the Mailbox section of the release notes for Exchange 2013.

↑ Back to the top