Microsoft dropped content migration batch XX of XXX. Migration package is not processed. (4376361)

Microsoft dropped content migration batch XX of XXX. Migration package is not processed.

During an ODM Quest migration, the task process failed to complete successfully, and the migration report indicated the error: "Microsoft dropped content migration batch XX of XXX. The migration package has not been processed."

The investigation, conducted in collaboration with Microsoft, determined that the problem originated from a third-party application which was utilizing an excessive amount of resources from the SharePoint Online service, resulting in throttling being applied to the organization's requests, including those from Quest.

It is advisable to initiate a support case with Microsoft to determine if the migration issues are due to high resource usage by a third-party application:

1. Open a Microsoft Support case:
   • Provide the details of the migration failures, including the error message "Microsoft dropped content migration batch XX of XXX. Migration package is not processed."
   • Explain that this issue was previously identified to be caused by a third-party application, and request Microsoft's assistance in determining if this is the root cause of the migration failures.
   • Ask Microsoft to check on their side if any of your organization's apps or third-party tools are being throttled or causing issues with Quest's migration process.
2. Provide additional information to Microsoft:
   • Share any relevant ODM logs or metrics that demonstrate the migration issues 
   • Offer to collaborate with Microsoft to further investigate the issue and identify potential mitigations.
3. Implement recommendations from Microsoft:
   • Based on Microsoft's analysis and recommendations, take the necessary actions to address the root cause of the migration failures.
   • This may involve working with the third-party application vendor to optimize the application's resource usage.
4. Monitor the migration process:
   • Closely monitor the migration progress and ensure that the issue has been resolved.
   • If the problem persists, work closely with Microsoft and Quest Support to further investigate and address the issue.

By following this approach and opening a support case with Microsoft, you can leverage their access to determine if a third-party application is the root cause of the migration failures and implement the appropriate resolution.