Microsoft has issued a clear warning to IT administrators managing Exchange Online environments: do not use local mailbox move requests inside the same tenant or datacenter. While the PowerShell command used for these moves still exists, Microsoft confirms that this action is unsupported and risky, with real chances of mailbox disruption or data loss.
What Is a Local Mailbox Move in Exchange Online?
A local mailbox move refers to using the New-MoveRequest PowerShell cmdlet to move a mailbox within the same Exchange Online tenant or datacenter.
This command was designed for:
- On-premises Exchange Server 2010 database moves
- Hybrid onboarding or offboarding scenarios
- Cross-tenant mailbox migrations
- Multi-Geo environments with mailboxes in different regions
However, in modern Exchange Online, Microsoft manages mailbox placement automatically. Forcing a manual intra-tenant move goes against how the service is designed to operate.
Why Microsoft Does Not Support Local Mailbox Moves
Microsoft has been explicit that local move requests are not supported, even though the command is still technically available.
1. No Microsoft Support or Troubleshooting
Once a local move is initiated:
- Microsoft Support cannot accelerate, fix, or troubleshoot it
- The move is treated as a low-priority background task
- Completion time is unpredictable and may take days or even weeks
There is no guaranteed duration, unlike Microsoft-managed automated mailbox balancing processes.
2. Risk of Orphaned or “Dial-Toned” Mailboxes
One of the most serious risks involves mailbox shards.
Exchange Online mailboxes can include:
- Primary Mailbox
- Main Archive Mailbox
- Auxiliary or component-based shards
If a local move is accidentally targeted at the wrong shard type (such as ComponentShared or AuxArchive), the system’s completion logic may:
- Fail to update the correct database
- Reset the Primary mailbox database reference
- Result in a dial-toned or orphaned mailbox
In simple terms, this can cause users to lose access to their real mailbox data.
3. Manual Moves Can Make Performance Worse
A common misconception is that moving a mailbox improves performance. Microsoft clearly states that this is not true.
Mailbox performance depends on:
- Service-level optimizations
- Backend load balancing
- Automated health monitoring
A manually moved mailbox can actually land on a more constrained server, making performance worse instead of better.
4. Local Moves Do Not Truly Repair Mailboxes
Another myth is that mailbox moves “fix” corruption.
While a move recreates mailbox items on the destination database, it:
- Does not guarantee corruption repair
- May leave underlying issues unresolved
- Can make root-cause investigation harder later
Mailbox moves are not a repair tool in Exchange Online.
Why the New-MoveRequest Cmdlet Still Exists
Admins often ask why Microsoft hasn’t removed the command if it’s unsafe.
The reason is compatibility:
- The cmdlet is still fully supported for cross-tenant migrations
- It is required for certain hybrid and Multi-Geo scenarios
Because of this, Microsoft keeps the command available but explicitly warns against using it for local moves.
What Administrators Should Do Instead
If you are experiencing mailbox-related issues, Microsoft recommends supported alternatives.
Open a Microsoft Support Case
If a mailbox shows unusual behavior:
- Contact Microsoft Support
- Allow engineering teams to investigate
- In some cases, Microsoft may perform a controlled mailbox move themselves
This process is monitored, validated, and safe.
Trust Exchange Online Automation
Exchange Online continuously:
- Monitors mailbox health
- Rebalances databases automatically
- Handles load distribution without admin intervention
Manual interference is rarely necessary and often counterproductive.
Do’s and Don’ts for Exchange Online Mailbox Management
Do:
- Investigate the root cause of mailbox problems
- Use Microsoft-supported migration and repair methods
- Rely on Exchange Online’s automated systems
Don’t:
- Use New-MoveRequest for local mailbox moves
- Attempt shard-level or auxiliary archive moves manually
- Expect Microsoft Support to fix or speed up unsupported moves
FAQs
Is it safe to use local mailbox moves in Exchange Online?
No. Microsoft does not support local mailbox moves in Exchange Online. These moves can lead to data loss, orphaned mailboxes, and long completion times that Microsoft Support cannot troubleshoot or speed up.
What does Microsoft say about Exchange Online local mailbox moves?
Microsoft warns administrators not to use local mailbox moves because Exchange Online already manages mailbox placement automatically. Manual moves are unsupported and can cause reliability issues.
Why does the New-MoveRequest cmdlet still exist in Exchange Online?
The New-MoveRequest cmdlet exists for legacy and supported scenarios such as cross-tenant migrations and hybrid deployments. It is not supported for moving mailboxes within the same tenant or datacenter.
Can local mailbox moves cause data loss?
Yes. Local mailbox moves can result in orphaned or dial-toned mailboxes, especially if a move targets the wrong mailbox shard or archive component.
Do local mailbox moves improve mailbox performance?
No. Mailbox performance in Exchange Online depends on Microsoft’s backend optimizations. Manual local moves do not improve performance and can place mailboxes on more constrained servers.
Are local mailbox moves supported by Microsoft Support?
No. Microsoft Support cannot troubleshoot, expedite, or recover issues caused by unsupported local mailbox moves in Exchange Online.
What should administrators do instead of local mailbox moves?
Administrators should open a Microsoft Support case to investigate mailbox issues. Microsoft engineering teams may perform controlled actions when necessary.
Does Exchange Online automatically manage mailbox placement?
Yes. Exchange Online continuously monitors mailbox health, load, and performance, and automatically rebalances mailboxes without manual administrator intervention.
Can local mailbox moves fix mailbox corruption?
No. Local mailbox moves do not reliably fix corruption and may leave underlying issues unresolved, making further troubleshooting more difficult.
Is New-MoveRequest safe for any Exchange Online migrations?
Yes, but only for supported scenarios such as cross-tenant mailbox migrations or approved hybrid Exchange workflows.
Local mailbox moves in Exchange Online carry real risks, including data loss and long-term mailbox damage. While the tools may still exist, that does not mean they are safe to use in modern cloud environments.
For Exchange Online administrators, the safest path is clear: avoid unsupported local moves and work within Microsoft’s supported support and automation framework.
