Stuck Mailbox Migrations & Move Requests

The question it answers: Which migration batches and move requests failed, stalled or are waiting to be completed or removed?

During tenant-to-tenant moves, hybrid off-boarding or archive imports, batches and move requests fail or stall quietly - and completed ones are left behind. This report lists what failed, what stalled and what is waiting for someone to press Complete.

At a glance

Where in the app	Exchange Online › Mail Security & Hygiene › Stuck Migrations & Moves
Workload	Exchange Online
Kind	Findings list · dashboard tile
Data	Read from Microsoft 365 when someone first opens it, then kept for the report cache lifetime (Settings > Data & cache, 1 hour unless changed). It reads through PowerShell (Exchange Online or SharePoint Online), so the first load takes longer than a Graph report.
Licence	No extra licence needed.
Report id (API and MCP)	exchange.hygiene.migrations

Columns

Column	Key	Type
Severity	Severity	Status
Type	Category	Text
Batch / mailbox	Subject	Link
Check	Setting	Text
Value	Value	Text
Finding	Finding	Text
Progress	Detail	Text
Last update	When	Date
Failed	Number	Number

A findings list hides columns that no row fills. Severity is Critical, Serious, Warning, OK or Info; rows rated Critical, Serious or Warning need attention (Working with findings).

What it needs

Licence: No extra licence needed.

Application permissions on the IntensiveReports app registration (all permissions):

Permission	API	What it allows	Note
Exchange.ManageAsApp	Office 365 Exchange Online	Manage Exchange As Application	+ Move Mailboxes / View-Only Recipients

Data sources it reads

• Get-MigrationBatch
• Get-MoveRequest
• Get-MoveRequestStatistics

Through the API and MCP

GET /ir-api/v1/reports/exchange.hygiene.migrations?size=100

An AI assistant reads it with the MCP tool get_report and the id exchange.hygiene.migrations. The client needs the Read grant for Exchange Online. See Using the API.