Article ID: 2723127 - View products that this article applies to.
Not sure what release of Office 365 you're using? Go to the following Microsoft website:
Am I using Office 365 after the service upgrade?
You have a hybrid deployment of Microsoft Exchange Online in Microsoft Office 365 and of your on-premises Microsoft Exchange Server environment. When you try to use the New-MoveRequest Windows PowerShell cmdlet to move or offboard a mailbox from Office 365 to the on-premises environment, the mailbox isn't moved. Additionally, you may receive an error message that resembles the following:
The call to ‘https://webmail.domain.com/EWS/mrsproxy.svc’ timed out.
The operation has timed out
+ CategoryInfo : NotSpecified: (0:Int32) [New-MoveRequest], RemoteTransientException
+ FullyQualifiedErrorId : 725EBC5,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest
This issue may occur if incorrect syntax is used for domain names and host names in the New-MoveRequest cmdlet.
To resolve this issue, make sure that you use the correct syntax for domain names and host names in the New-MoveRequest cmdlet. The New-MoveRequest cmdlet requires all domain names and host names to be enclosed in single quotation marks (').
The following is an example of incorrect syntax:
The following is an example of correct syntax. (Note that this example uses single quotation marks around domain names and host names.)
'alias' | New-MoveRequest -Outbound -RemoteHostName webmail.contoso.com -RemoteCredential $onprem -RemoteTargetDatabase Database1 -TargetDeliveryDomain contoso.com
'alias' | New-MoveRequest -OutBound -RemoteTargetDatabase 'Database1' -RemoteHostName 'webmail.contoso.com' -RemoteCredential $onprem -TargetDeliveryDomain 'contoso.com'
For more information about how to use the New-MoveRequest cmdlet, go to the following Microsoft TechNet website:
Understanding Move Requests
Still need help? Go to the Office 365 Community
Article ID: 2723127 - Last Review: May 31, 2013 - Revision: 7.0