Although most migrations between on-premises Exchange Server and Microsoft 365 are performed using the Migration Service’s batching functionality, a few stalwart admins have held onto the more granul...
Updated Mar 29, 2022
Version 3.0
Blog Post
The_Exchange_Team I believe this change is responsible for breaking the ability to pipe Get-MoveRequest into Get-MoveRequestStatistics. If you care to see more detail, private message me for the MS Support case I opened about this issue, which is now closed where there was no pathway for a ticket to report that kind of problem. TL;DR is that UserGuid needs to be an Alias on the -Identity parameter in the Get-MoveRequestStatistics cmdlet, and the User property in the output from Get-MoveRequest needs to be something more unique than the DisplayName of the user. It doesn't appear to be a nested property either, so it's not like we can drill in (e.g., $MR = Get-MoveRequest; $MR[0].User.<some-better-unique-property>).
Is it possible to find out here, is this 'breaking' part of this change intended or accidental and will it be repaired?
Thanks in advance.