Changing the behavior of MoveRequest cmdlets

Published Mar 25 2022 09:36 AM 11K Views

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 granular control given by using the MoveRequest cmdlets directly.  But as time goes on even the hardiest and most proven of tools need to be sharpened or have components replaced, and it is now time for the MoveRequest cmdlets to be refreshed a little.

We are taking this opportunity to bring these cmdlets more in line with some of our other cmdlets.  Most admins who use these cmdlets will notice little to no difference in how these cmdlets function, which is intentional on our part.  But some may have scripts break if they aren’t updated before the cmdlets are updated.  We plan to release the updated cmdlets starting April 30th, 2022.

  1. New-MoveRequest will change from returning a MoveRequestStatistics object to returning a MoveRequest object.  Most New-* cmdlets are expected to return a data object matching their noun, which New-MoveRequest didn’t historically follow.  The MoveRequest object contains less data than the MoveRequestStatistics object, but that is desirable in this case because most of the extra data is only relevant or interesting after the request has made progress.
  2. The MoveRequest data object that is returned from Get-MoveRequest (and now New-MoveRequest) will have a slightly smaller set of properties.  Compared to the old data object, it will remove several generic user properties that are not relevant to move requests in particular, which could lead to confusion.  Each of those properties should remain available as output from the Get-Recipient, Get-Mailbox, Get-MailUser, etc. cmdlets instead.
Maintained properties Alias, DisplayName, RecipientTypeDetails, SourceDatabase, SourceArchiveDatabase, TargetDatabase, TargetArchiveDatabase, RemoteHostName, IsOffline, SuspendWhenReadyToComplete, ExchangeGuid, Flags, BatchName, Status, Protect, Suspend, Direction, RequestStyle, OrganizationId, Identity, IsValid, ObjectState
Renamed properties User (previously “Id”), UserGuid (previously “Guid”)
Added properties RequestQueue
Removed properties AdministrativeUnits, ExtensionCustomAttribute1, ExtensionCustomAttribute2, ExtensionCustomAttribute3, ExtensionCustomAttribute4, ExtensionCustomAttribute5, ExternalDirectoryObjectId, LastExchangeChangedTime, RecipientType, Name, DistinguishedName, ExchangeObjectId, OrganizationalUnitRoot, OriginatingServer, WhenCreatedUTC

The rest of the cmdlet behavior should remain the same.

There may be some other pieces deprecated in the future, such as removing SuspendWhenReadyToComplete behavior in favor of CompleteAfter, but a timeline for that will be determined at a later time.

The Exchange Migration Team

8 Comments
%3CLINGO-SUB%20id%3D%22lingo-sub-3267026%22%20slang%3D%22en-US%22%3EChanging%20the%20behavior%20of%20MoveRequest%20cmdlets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3267026%22%20slang%3D%22en-US%22%3E%3CP%3EAlthough%20most%20migrations%20between%20on-premises%20Exchange%20Server%20and%20Microsoft%20365%20are%20performed%20using%20the%20Migration%20Service%E2%80%99s%20batching%20functionality%2C%20a%20few%20stalwart%20admins%20have%20held%20onto%20the%20more%20granular%20control%20given%20by%20using%20the%20MoveRequest%20cmdlets%20directly.%26nbsp%3B%20But%20as%20time%20goes%20on%20even%20the%20hardiest%20and%20most%20proven%20of%20tools%20need%20to%20be%20sharpened%20or%20have%20components%20replaced%2C%20and%20it%20is%20now%20time%20for%20the%20MoveRequest%20cmdlets%20to%20be%20refreshed%20a%20little.%3C%2FP%3E%0A%3CP%3EWe%20are%20taking%20this%20opportunity%20to%20bring%20these%20cmdlets%20more%20in%20line%20with%20some%20of%20our%20other%20cmdlets.%26nbsp%3B%20Most%20admins%20who%20use%20these%20cmdlets%20will%20notice%20little%20to%20no%20difference%20in%20how%20these%20cmdlets%20function%2C%20which%20is%20intentional%20on%20our%20part.%26nbsp%3B%20But%20some%20may%20have%20scripts%20break%20if%20they%20aren%E2%80%99t%20updated%20before%20the%20cmdlets%20are%20updated.%26nbsp%3B%20We%20plan%20to%20release%20the%20updated%20cmdlets%20starting%20April%2030%3CSUP%3Eth%3C%2FSUP%3E%2C%202022.%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3ENew-MoveRequest%20will%20change%20from%20returning%20a%20MoveRequestStatistics%20object%20to%20returning%20a%20MoveRequest%20object.%26nbsp%3B%20Most%20New-*%20cmdlets%20are%20expected%20to%20return%20a%20data%20object%20matching%20their%20noun%2C%20which%20New-MoveRequest%20didn%E2%80%99t%20historically%20follow.%26nbsp%3B%20The%20MoveRequest%20object%20contains%20less%20data%20than%20the%20MoveRequestStatistics%20object%2C%20but%20that%20is%20desirable%20in%20this%20case%20because%20most%20of%20the%20extra%20data%20is%20only%20relevant%20or%20interesting%20after%20the%20request%20has%20made%20progress.%3C%2FLI%3E%0A%3CLI%3EThe%20MoveRequest%20data%20object%20that%20is%20returned%20from%20Get-MoveRequest%20(and%20now%20New-MoveRequest)%20will%20have%20a%20slightly%20smaller%20set%20of%20properties.%26nbsp%3B%20Compared%20to%20the%20old%20data%20object%2C%20it%20will%20remove%20several%20generic%20user%20properties%20that%20are%20not%20relevant%20to%20move%20requests%20in%20particular%2C%20which%20could%20lead%20to%20confusion.%26nbsp%3B%20Each%20of%20those%20properties%20should%20remain%20available%20as%20output%20from%20the%20Get-Recipient%2C%20Get-Mailbox%2C%20Get-MailUser%2C%20etc.%20cmdlets%20instead.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CTABLE%20border%3D%221%22%20width%3D%22100%25%22%3E%0A%3CTBODY%3E%0A%3CTR%3E%0A%3CTD%20width%3D%2230%25%22%3EMaintained%20properties%3C%2FTD%3E%0A%3CTD%20width%3D%2270%25%22%3EAlias%2C%20DisplayName%2C%20RecipientTypeDetails%2C%20SourceDatabase%2C%20SourceArchiveDatabase%2C%20TargetDatabase%2C%20TargetArchiveDatabase%2C%20RemoteHostName%2C%20IsOffline%2C%20SuspendWhenReadyToComplete%2C%20ExchangeGuid%2C%20Flags%2C%20BatchName%2C%20Status%2C%20Protect%2C%20Suspend%2C%20Direction%2C%20RequestStyle%2C%20OrganizationId%2C%20Identity%2C%20IsValid%2C%20ObjectState%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%2230%25%22%3ERenamed%20properties%3C%2FTD%3E%0A%3CTD%20width%3D%2270%25%22%3EUser%20(previously%20%E2%80%9CId%E2%80%9D)%2C%20UserGuid%20(previously%20%E2%80%9CGuid%E2%80%9D)%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%2230%25%22%3EAdded%20properties%3C%2FTD%3E%0A%3CTD%20width%3D%2270%25%22%3ERequestQueue%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%2230%25%22%3ERemoved%20properties%3C%2FTD%3E%0A%3CTD%20width%3D%2270%25%22%3EAdministrativeUnits%2C%20ExtensionCustomAttribute1%2C%20ExtensionCustomAttribute2%2C%20ExtensionCustomAttribute3%2C%20ExtensionCustomAttribute4%2C%20ExtensionCustomAttribute5%2C%20ExternalDirectoryObjectId%2C%20LastExchangeChangedTime%2C%20RecipientType%2C%20Name%2C%20DistinguishedName%2C%20ExchangeObjectId%2C%20OrganizationalUnitRoot%2C%20OriginatingServer%2C%20WhenCreatedUTC%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3C%2FTBODY%3E%0A%3C%2FTABLE%3E%0A%3CP%3EThe%20rest%20of%20the%20cmdlet%20behavior%20should%20remain%20the%20same.%3C%2FP%3E%0A%3CP%3EThere%20may%20be%20some%20other%20pieces%20deprecated%20in%20the%20future%2C%20such%20as%20removing%20SuspendWhenReadyToComplete%20behavior%20in%20favor%20of%20CompleteAfter%2C%20but%20a%20timeline%20for%20that%20will%20be%20determined%20at%20a%20later%20time.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22author%22%3EThe%20Exchange%20Migration%20Team%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-3267026%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20wanted%20to%20tell%20you%20about%20changing%20in%20the%20behavior%20of%20MoveRequest%20cmdlets%20that%20we%20are%20working%20on.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-3267026%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAnnouncements%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMigration%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3295481%22%20slang%3D%22en-US%22%3ERe%3A%20Changing%20the%20behavior%20of%20MoveRequest%20cmdlets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3295481%22%20slang%3D%22en-US%22%3E%3CP%3ENotably%20absent%20from%20the%20properties%20list%20is%20%E2%80%9CRequestGuid%E2%80%9D.%20Will%20this%20property%20be%20maintained%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3294448%22%20slang%3D%22en-US%22%3ERe%3A%20Changing%20the%20behavior%20of%20MoveRequest%20cmdlets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3294448%22%20slang%3D%22en-US%22%3E%3CP%3EI%20agree%20with%20the%20above%20posts%20regarding%20'SuspendWhenReadyToComplete'%20(acknowledging%20that%20it%20is%20listed%20as%20a%20possible%20future%20deprecation).%20%26nbsp%3BWe%20use%20this%20feature%20extensively.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3290980%22%20slang%3D%22en-US%22%3ERe%3A%20Changing%20the%20behavior%20of%20MoveRequest%20cmdlets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3290980%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F81948%22%20target%3D%22_blank%22%3E%40CSU_Scott%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F158478%22%20target%3D%22_blank%22%3E%40Kreera%20House%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F604307%22%20target%3D%22_blank%22%3E%40martinthiem%3C%2FA%3E%2C%20I'm%20curious%20how%20SuspendWhenReadyToComplete%20is%20more%20useful%20than%20CompleteAfter%2C%20particularly%20when%20compared%20to%20using%20%22-CompleteAfter%20%24(%5BDateTime%5D%3A%3AMaxValue)%22.%20%26nbsp%3B%20%26nbsp%3BCompleteAfter%20automatically%20keeps%20the%20move%20healthy%20by%20running%20daily%20incremental%20syncs.%20%26nbsp%3BThen%20when%20you're%20actually%20ready%20to%20complete%2C%20simply%20remove%20CompleteAfter%3A%20%22-CompleteAfter%20%24null.%22%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOne%20common%20cause%20for%20escalations%20in%20the%20past%20was%20admins%20forgetting%20to%20run%20incremental%20syncs%20leaving%20removal%2Frecreation%20as%20the%20only%20way%20for%20a%20move%20to%20catch%20back%20up%20for%20high-churn%20mailboxes.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3284442%22%20slang%3D%22en-US%22%3ERe%3A%20Changing%20the%20behavior%20of%20MoveRequest%20cmdlets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3284442%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20they%20are%20removing%20suspendwhenreadytocomplete%2C%20I%20have%20to%20throw%20my%20voice%20in%20and%20say%20we%20used%20that%20feature%20extensively%20and%20hope%20that%20enough%20voices%20will%20change%20the%20direction.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3276237%22%20slang%3D%22en-US%22%3ERe%3A%20Changing%20the%20behavior%20of%20MoveRequest%20cmdlets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3276237%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F297961%22%20target%3D%22_blank%22%3E%40Djcarr%3C%2FA%3E%26nbsp%3BIt's%20mentioned%20in%20the%20fine%20print%20below%20the%20current%20changes%3A%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22KreeraHouse_0-1649150393441.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F361368i07637D7EDC09635B%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22KreeraHouse_0-1649150393441.png%22%20alt%3D%22KreeraHouse_0-1649150393441.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3276027%22%20slang%3D%22en-US%22%3ERe%3A%20Changing%20the%20behavior%20of%20MoveRequest%20cmdlets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3276027%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F604307%22%20target%3D%22_blank%22%3E%40martinthiem%3C%2FA%3Eand%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F158478%22%20target%3D%22_blank%22%3E%40Kreera%20House%3C%2FA%3E%26nbsp%3B%20SuspendWhenReadytoComplete%20is%20not%20currently%20listed%20as%20something%20that%20is%20being%20removed%20unless%20I%20am%20reading%20this%20after%20the%20post%20was%20updated.%20As%20of%204%2F4%2F2022%26nbsp%3B%3CSPAN%3ESuspendWhenReadyToComplete%20is%20in%20the%20maintained%20properties.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3274766%22%20slang%3D%22en-US%22%3ERe%3A%20Changing%20the%20behavior%20of%20MoveRequest%20cmdlets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3274766%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20here.%20SuspendWhenReadyToComplete%20is%20important%20for%20us%20to%20reduce%20impact%20on%20the%20users.%20It%20is%20much%20more%20useful%20than%26nbsp%3B%3CSPAN%3ECompleteAfter.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3274236%22%20slang%3D%22en-US%22%3ERe%3A%20Changing%20the%20behavior%20of%20MoveRequest%20cmdlets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3274236%22%20slang%3D%22en-US%22%3E%3CP%3EWhy%20do%20you%20want%20to%20remove%26nbsp%3B%3CSPAN%3ESuspendWhenReadyToComplete%3F%20We%20are%20excessively%20use%20this%20feature%20to%20optimize%20our%20migrations%E2%80%A6%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Co-Authors
Version history
Last update:
‎Mar 29 2022 02:54 PM
Updated by: