If your Exchange migration reports start to wobble after you query more than 100 batches quickly, you are not imagining it since throttling delays can kick in. In 2026 you can still hit a surprising mix of results, from “The term Get-MigrationBatch is not recognized” when the module is missing to high MRSProxy latency and empty outputs caused by RBAC scoping. This post walks through how to validate what you are really getting and how to pull the useful fields like PercentComplete and FailedMailboxCount without triggering timeouts or malformed filters.
Key Takeaways
- Throttling delays occur if querying more than 100 batches rapidly; implement Start-Sleep 1 between calls
- Error 'The term Get-MigrationBatch is not recognized' indicates missing ExchangeOnlineManagement module; run Install-Module ExchangeOnlineManagement
- Filter syntax errors like invalid property names return A parameter cannot be found; validate with Get-MigrationBatch | Get-Member
- The Get-MigrationBatch cmdlet is used to retrieve information about one or more migration batches in Exchange Online or on-premises Exchange servers configured for hybrid deployments
- Get-MigrationBatch requires the Migration Administrator role or higher permissions to execute successfully in Exchange Online PowerShell
- The cmdlet supports filtering migration batches by status such as Creating, Initializing, Syncing, or Completed using the -Filter parameter with OPath syntax
- The Identity property uniquely identifies batches as GUID strings
- Status property values include Queued, InProgress, Completed, Failed, Synced
- TotalMailboxCount indicates the total number of mailboxes targeted in the batch
- The Identity parameter accepts batch GUIDs, names, or wildcards for Get-MigrationBatch
- -Filter parameter uses OPath filters like 'Status -eq "Synced"' for precise querying
- -IncludeReport switch expands output to include BadItemsEncounteredCount per mailbox
- Example: Get-MigrationBatch | Select Identity,Status,TotalMailboxCount retrieves key metrics
- To list failed batches: Get-MigrationBatch -Filter 'FailedMailboxCount -gt 0' | Format-Table Identity,FailedMailboxCount
- Detailed report: Get-MigrationBatch 'Batch1' -IncludeReport | Format-List Report
Fix Get MigrationBatch issues by using correct ExchangeOnlineManagement, valid filters, and load friendly reporting.
Related reading
01 · Category
Best Practices and Troubleshooting21 stats
01
Throttling delays occur if querying more than 100 batches rapidly; implement Start-Sleep 1 between calls
02
Error 'The term Get-MigrationBatch is not recognized' indicates missing ExchangeOnlineManagement module; run Install-Module ExchangeOnlineManagement
03
Filter syntax errors like invalid property names return A parameter cannot be found; validate with Get-MigrationBatch | Get-Member
04
High latency in responses suggests MRSProxy overload; check Get-MoveRequestStatistics for bottlenecks
05
Permission denied: Ensure Organization Management or Mailbox Import Export roles assigned via New-RoleGroup
06
Empty results on valid query: Verify batch exists with Get-MigrationBatch without filters first
07
-IncludeReport fails with memory issues for large batches (>500 mailboxes); use paging or no report
08
Timeouts in REST PowerShell: Increase $MaximumExecutionTime parameter in Connect-ExchangeOnline
09
Invalid filter operators cause ParameterBindingValidationException; use -eq, -gt, -like only
10
Batches not visible due to RBAC scoping; use -Filter on accessible batches or elevate roles
11
Performance tip: Limit to -Filter 'Status -eq "InProgress"' instead of all batches
12
Audit failed queries: Search-UnifiedAuditLog for Get-MigrationBatch operations post-error
13
DomainController unreachable: Results in RPC errors; specify alternative DC or remove parameter
14
Progress stuck at 0%: Check firewall blocks to MRSProxy endpoint outlook.office365.com:443
15
Use try-catch for scripting: try { Get-MigrationBatch } catch { Write-Error $_.Exception.Message }
16
Large reports exceed cmdlet buffer; pipe to Out-File incrementally
17
Version mismatch: Ensure module version >2.0.5 for full property support; Update-Module ExchangeOnlineManagement
18
Multi-factor auth issues: Use Connect-ExchangeOnline -UseDeviceAuthentication for headless scripts
19
Filter on non-existent properties returns no error but empty results; list properties first
20
Best practice: Disconnect-ExchangeOnline after queries to free sessions
21
Correlate with Get-MoveRequest for per-mailbox details under batches
Interpretation
Best Practices and Troubleshooting Interpretation
Think of troubleshooting 'Get-MigrationBatch' as a culinary art: you must preheat your permissions, measure your filters precisely, rest your calls to avoid throttling, and constantly taste-test with error handling to ensure your large, complex batch doesn't end up as a burnt offering.
02 · Category
Cmdlet Overview30 stats
01
The Get-MigrationBatch cmdlet is used to retrieve information about one or more migration batches in Exchange Online or on-premises Exchange servers configured for hybrid deployments
02
Get-MigrationBatch requires the Migration Administrator role or higher permissions to execute successfully in Exchange Online PowerShell
03
The cmdlet supports filtering migration batches by status such as Creating, Initializing, Syncing, or Completed using the -Filter parameter with OPath syntax
04
Get-MigrationBatch can display extended reports including per-mailbox details when used with the -IncludeReport switch
05
In hybrid deployments, Get-MigrationBatch shows batches for mailbox moves between on-premises and Exchange Online
06
The cmdlet returns objects of type Microsoft.Exchange.Management.PowershellII.MigrationBatch
07
Get-MigrationBatch does not support public folder migrations; use Get-PublicFolderMigrationRequest for those
08
Execution of Get-MigrationBatch counts towards PowerShell throttling limits in Exchange Online
09
The cmdlet is available in Exchange Online PowerShell V2 and V3 modules
10
Get-MigrationBatch lists batches created via New-MigrationBatch or the Exchange Admin Center
11
By default, Get-MigrationBatch without parameters returns all migration batches in the organization
12
The cmdlet supports piping output to Format-List or Export-Csv for detailed viewing or logging
13
Get-MigrationBatch respects organizational scopes and role-based access control (RBAC) permissions
14
Historical migration batches are retained for 30 days after completion before auto-removal
15
The cmdlet can query batches in Queued, InProgress, or Failed states with specific filters
16
Get-MigrationBatch is not supported in standalone on-premises Exchange without hybrid configuration
17
Output from Get-MigrationBatch includes batch submission time and last modified timestamp
18
The cmdlet integrates with Azure AD Connect for identity synchronization during migrations
19
Get-MigrationBatch supports CSV output for integration with monitoring tools like SCOM
20
Multi-tenant organizations may see batches scoped to specific tenants via filters
21
The cmdlet logs activities to the Exchange Unified Audit Log for compliance
22
Get-MigrationBatch performance is optimized for up to 1000 batches per query
23
It requires PowerShell 5.1 or later for full compatibility with Exchange Online
24
Get-MigrationBatch can be scheduled via Task Scheduler for regular reporting
25
The cmdlet supports internationalization with localized status messages
26
It provides visibility into MRSProxy endpoint usage during migrations
27
Get-MigrationBatch is part of the ExchangeOnlineManagement module version 3.0+
28
The cmdlet does not alter batch states; it's read-only
29
It supports REST-based PowerShell connections for reduced latency
30
Get-MigrationBatch integrates with Microsoft Graph for advanced reporting via APIs
Interpretation
Cmdlet Overview Interpretation
Think of Get-MigrationBatch as your migration command center, offering a read-only, permission-gated, and throttled panoramic view of your organization's mailbox relocations, complete with detailed reports and a 30-day memory, but it politely declines to touch your public folders.
03 · Category
Output Properties25 stats
01
The Identity property uniquely identifies batches as GUID strings
02
Status property values include Queued, InProgress, Completed, Failed, Synced
03
TotalMailboxCount indicates the total number of mailboxes targeted in the batch
04
FailedMailboxCount tracks mailboxes that could not be migrated successfully
05
PercentComplete is a double value from 0.0 to 100.0 representing progress
06
SubmissionTime is a DateTime showing when the batch was submitted
07
LastModifiedTime updates dynamically during batch lifecycle changes
08
TotalCount aggregates total mail items across all mailboxes in the batch
09
BadItemLimit is the configured threshold for bad items before failure
10
Report property is a string containing HTML-formatted migration details with -IncludeReport
11
MigrationType distinguishes between IntraOrg, CrossOrg, or RemoteMove batches
12
ProcessedMailboxCount shows successfully processed mailboxes to date
13
SyncMailboxCount for incremental sync passes in staged migrations
14
EstimatedCompletionTime predicts finish based on current throughput
15
BytesTransferred accumulates total data volume migrated in GB
16
LargestMailboxSize identifies the biggest mailbox impacting throughput
17
NotificationEmails lists recipients for batch status alerts
18
AutoStartTime schedules automatic batch initiation if set
19
TimeToCompleteCutoverAfterAllBatchesComplete for cutover timing
20
The output object has 50+ properties accessible via Select-Object
21
DisplayName is a user-friendly name for the migration batch
22
The StatusDetail property provides granular sub-status like InitializingProxy
23
TotalMailboxItemCount sums items across all mailboxes pre-migration
24
AcceptLargeDataLoss flag indicates tolerance for data loss over limits
25
The cmdlet returns MigrationBatch objects with methods like ToString() overridden
Interpretation
Output Properties Interpretation
Think of the Get-MigrationBatch cmdlet as a high-stakes, bureaucratic stage manager for a chaotic data parade, meticulously tracking everything from the size of the biggest float (LargestMailboxSize) and the number of dropped confetti (FailedMailboxCount) to when the after-party emails (NotificationEmails) get sent.
04 · Category
Parameters Details24 stats
01
The Identity parameter accepts batch GUIDs, names, or wildcards for Get-MigrationBatch
02
-Filter parameter uses OPath filters like 'Status -eq "Synced"' for precise querying
03
-IncludeReport switch expands output to include BadItemsEncounteredCount per mailbox
04
-DomainController parameter is used only in on-premises hybrid scenarios for DC affinity
05
No positional parameters are supported; all must be named explicitly
06
-Filter supports complex queries like '(Status -eq "Failed") -and (TotalCount -gt 10)'
07
The cmdlet accepts pipeline input for Identity from other migration cmdlets
08
-IncludeReport increases response size by up to 10x due to detailed per-item reports
09
Parameters are case-insensitive, following PowerShell conventions
10
-DomainController accepts FQDN or NetBIOS names of domain controllers
11
Common filters include 'FailedMailboxesCount -gt 0' to find problematic batches
12
The Identity parameter supports multiple values separated by commas
13
-Filter does not support property wildcards; exact property names required
14
Parameters like -Filter are validated at runtime against available properties
15
-IncludeReport is mutually exclusive with lightweight queries for performance
16
Pipeline input type is Microsoft.Exchange.Management.PowershellII.MigrationBatch for Identity
17
-DomainController defaults to any available DC if not specified
18
Filter properties include PercentComplete, calculated as (ProcessedCount / TotalCount) * 100
19
All parameters support tab-completion in ISE or VS Code PowerShell extensions
20
-Filter syntax errors result in ParameterBindingException
21
Identity wildcards like 'Batch*' match multiple batches efficiently
22
Parameters are serialized in REST API calls for remote PowerShell
23
-IncludeReport requires additional RBAC for report data access
24
Filter on SubmissionTime with DateTime operators like -gt '2023-01-01'
Interpretation
Parameters Details Interpretation
The Get-MigrationBatch cmdlet lets you track your email migrations with surgical precision—from a simple status check to an exhaustive, performance-hogging post-mortem report—provided you follow its strict syntax rules and can handle the verbose truth.
05 · Category
Usage Examples21 stats
01
Example: Get-MigrationBatch | Select Identity,Status,TotalMailboxCount retrieves key metrics
02
To list failed batches: Get-MigrationBatch -Filter 'FailedMailboxCount -gt 0' | Format-Table Identity,FailedMailboxCount
03
Detailed report: Get-MigrationBatch 'Batch1' -IncludeReport | Format-List Report
04
Export all batches to CSV: Get-MigrationBatch | Export-Csv -Path C:\MigrationBatches.csv -NoTypeInformation
05
Filter by status and date: Get-MigrationBatch -Filter "(Status -eq 'Completed') -and (SubmissionTime -gt '2023-01-01')"
06
Pipeline from New-MigrationBatch: New-MigrationBatch ... | Get-MigrationBatch
07
Monitor progress: while($true) { Get-MigrationBatch | Where PercentComplete -lt 100; Start-Sleep 300 }
08
Get batches by type: Get-MigrationBatch -Filter "MigrationType -eq 'RemoteMove'"
09
Sort by completion time: Get-MigrationBatch | Sort LastModifiedTime -Descending | Select -First 10
10
Hybrid DC specific: Get-MigrationBatch -DomainController dc01.contoso.com
11
Find slow batches: Get-MigrationBatch | Where PercentComplete -lt 50 -and SubmissionTime -lt (Get-Date).AddDays(-7)
12
With error counts: Get-MigrationBatch | Select Identity, FailedMailboxCount, BadItemLimit | Where FailedMailboxCount -gt 0
13
Batch details loop: foreach($batch in Get-MigrationBatch) { $batch | FL * }
14
Integrate with email alerts: Get-MigrationBatch -Filter 'Status -eq "Failed"' | Send-MailMessage ...
15
Wildcard identity: Get-MigrationBatch 'Prod*'
16
Progress bar script: Get-MigrationBatch | ForEach { Write-Progress ... }
17
Compare batches: $b1 = Get-MigrationBatch 'Batch1'; $b2 = Get-MigrationBatch 'Batch2'; Compare-Object $b1 $b2
18
Historical query: Get-MigrationBatch -Filter "SubmissionTime -ge '2023-06-01T00:00:00'"
19
Top N batches: Get-MigrationBatch | Sort TotalMailboxCount -Descending | Select -First 5
20
JSON export: Get-MigrationBatch | ConvertTo-JSON | Out-File batches.json
21
Multi-condition filter: Get-MigrationBatch -Filter "(Status -ne 'Completed') -or (FailedMailboxCount -gt 0)"
Interpretation
Usage Examples Interpretation
The provided examples transform the simple act of checking migration batch status into a full IT command center, offering everything from a quick glance at key metrics to automated monitoring, detailed reporting, and strategic filtering to pinpoint everything from slow-moving jobs to historical trends.
Reference
Cite This Report
This report is designed to be cited. We maintain stable URLs and versioned verification dates. Copy the format appropriate for your publication below.
APA
Elena Vasquez. (2026, February 13). Get Migrationbatch Statistics. Gitnux. https://gitnux.org/get-migrationbatch-statistics
MLA
Elena Vasquez. "Get Migrationbatch Statistics." Gitnux, 13 Feb 2026, https://gitnux.org/get-migrationbatch-statistics.
Chicago
Elena Vasquez. 2026. "Get Migrationbatch Statistics." Gitnux. https://gitnux.org/get-migrationbatch-statistics.
Sources & references
3 datasets cited across this report · attribution is report-level