Email Migration

Fix Exchange Mailbox Stuck in ProvisioningUpdate During Cutover Migration

John WilsonJohn Wilson Nov 4, 2026 868 views

Question details

An on-premises mailbox migration to Microsoft 365 is stalled in the ProvisioningUpdate state for more than 24 hours without reporting any errors.

Fix Exchange Mailbox Stuck in ProvisioningUpdate During Cutover Migration
Product
Microsoft 365 / Exchange Online
Device & OS
not provided
Scenario
Performing a cutover migration from an on-premises Exchange environment to Microsoft 365.
Observed behavior
The migration batch is active but has synchronized zero items. Restarting the batch does not change the status, and it remains stuck in ProvisioningUpdate without throwing a migration error.
Before you start

Ensure you have the Exchange Online PowerShell module installed and are connected to your Microsoft 365 tenant with Exchange Administrator privileges.

Solution 1Recommended

Stop and Resume the Migration User via PowerShell

Use Exchange Online PowerShell to forcefully stop the stalled migration user, verify configurations, and then resume the process.

Often, a migration can get hung up on a specific mailbox due to temporary backend glitches or minor configuration mismatches. Stopping the individual user's migration rather than the whole batch allows the system to reset the state for that specific mailbox.

1
Connect to Exchange Online

Open PowerShell as an administrator and connect to Exchange Online by running 'Connect-ExchangeOnline'.

2
Stop the migration user

Execute the following command to stop the affected mailbox migration: Stop-MigrationUser -Identity user@contoso.com

3
Verify endpoint configuration

Check the migration endpoint and the on-premises mailbox settings to ensure there are no configuration errors preventing the synchronization.

4
Resume the migration

Once verified, restart or resume the migration for the stopped user to see if it moves past the ProvisioningUpdate phase.

Stop and Resume the Migration User via PowerShell
Important: Avoid removing synchronization objects or manually importing mail into the mailbox until the directory configuration and migration state have been thoroughly reviewed.
Free Microsoft Office alternative

Enhance Your Productivity with WPS Office

While resolving Microsoft 365 administration and migration issues can be complex, creating and editing your daily documents doesn't have to be. WPS Office provides a free, lightweight, and incredibly powerful alternative to Microsoft Office applications.

  1. 1. Download the installer: Visit the official WPS Office website and download the free installation package.
  2. 2. Install WPS Office: Run the installer and follow the quick on-screen instructions to set up the software on your device.
  3. 3. Open and edit your files: Launch WPS Office to immediately open, edit, and save your existing Word, Excel, and PowerPoint documents seamlessly.
Fully compatible with Microsoft Office formats, including .docx, .xlsx, and .pptx.Lightweight installation that consumes minimal system resources.Familiar tabbed interface that requires zero learning curve for Office users.Built-in PDF editing, conversion, and annotation tools.
microsoft office alternative - wps office

Frequently Asked Questions

Why does a cutover migration stay stuck in ProvisioningUpdate?

This status typically indicates that Microsoft 365 is trying to provision the mailbox or apply directory synchronization updates, but is encountering a conflict, transient server delay, or an attribute mismatch that prevents completion.

Will stopping the migration user delete their migrated data?

No. Using the Stop-MigrationUser cmdlet only halts the current active migration process. It does not delete the mailbox or any data that has already been synchronized to the target Microsoft 365 mailbox.

How do I collect migration diagnostics for Microsoft Support?

You can gather detailed logs by running the command 'Get-MigrationUserStatistics -Identity user@domain.com -IncludeReport | Export-Clixml -Path C:\temp\MigrationReport.xml' in Exchange Online PowerShell, and then provide the resulting XML file to the support team.