(*) Strictly speaking, for hybrid migrations and EWS/mrsproxy.svc endpoint, it would work if the device supported NTLM pre-authentication. This is required because, for example, Exchange 2010 cannot proxy to Exchange 2016 in order to move an Exchange 2016 mailbox to or from Exchange Online through an Exchange 2010 MRSProxy endpoint. If you have an Exchange organization with Exchange 2013/2016 in coexistence with legacy Exchange servers (Exchange 2010), then you need to point the MRSproxy namespace to the newer Exchange version in your environment.TLS1.2 should be enabled in the on-premises infrastructure.For classic hybrid, a valid 3 rd party certificate is required for EWS / IIS.For classic hybrid, pre-authentication for EWS / Autodiscover virtual directories is not supported.(*).For classic hybrid – where we require inbound connectivity from Exchange Online to on-premises Exchange, allow all Exchange Online IP addresses to connect to on-premises EWS / Autodiscover.SSL offloading is not supported for MRSProxy.Any network load-balancing for Exchange 2010 MRSProxy servers requires IP persistence (affinity).You cannot offboard a remote mailbox without ExchangeGuid set on it.
More info on the types of holds can be found here. This is because Exchange 2010 doesn’t know about in-place hold which was introduced in Exchange 2013 or about organization-wide holds in Office 365. You cannot offboard to Exchange 2010 an Exchange Online Mailbox that has any hold other than Litigation Hold.On-premises migration admin needs to have the minimum required permissions and valid credentials.Maximum number of items per regular mailbox folder is 1 million and 3 million for the dumpster, reference here.Even if you have auto-expanding enabled in Exchange Online, as of this writing the maximum mailbox size for migration of main archive is still 100GB – reference here. Make sure your migration users are synchronized with AADconnect tool and corresponding mail users are provisioned correctly on the Exchange Online side for corresponding on-premises mailboxes (ExchangeGuid present, alias, recipient type correct, accepted domains for the email addresses and secondary smtp address Maximum storage quota in Exchange Online for both primary and archive mailbox is 100GB each.Exchange Online requires Negotiate (NTLM) authentication for MRSProxy.MRSProxy needs to be enabled and running on Exchange on-premises.Sometimes, resuming of the move can help, especially if there were some temporary issues on the Exchange Online side that were addressed.īefore getting into troubleshooting, I recommend you check the following ‘Minimum Requirements’ those are the things we know will break migrations (and we see them do so): The move is stopped and needs the administrator’s attention to investigate the reason of failure. What to do if a migration is Completed With Warnings (Part 5)Ĭontinuing the blog post series, we arrived at troubleshooting failed migrations.Ī ‘failed migration’ is when the status of the move request shows as ‘failed’, and we have one or more failures logged in the move report.Troubleshooting Slow Migrations (Part 4).
Exchange Hybrid Migrations: More Than Just a Pretty Face (Part 1).
This blog post is a part of a 5 post series consisting of: