Email Migration

How to Fix Microsoft 365 PST Import Stuck at 68% Quarantined

Huma Ashraf ChHuma Ashraf Ch Oct 22, 2026 870 views

Question details

The user needs to resolve a Microsoft 365 PST import job that has halted and been marked as quarantined.

How to Fix Microsoft 365 PST Import Stuck at 68% and Quarantined
Product
Microsoft 365
Device & OS
not provided
Scenario
Migrating email data via a PST import job within the Microsoft 365 environment.
Observed behavior
The PST import job remains stuck at 68 percent, waiting for job pickup. The import report states it was quarantined because Azure.Core could not be loaded due to an assembly manifest version mismatch.
Before you start

Ensure you have Microsoft 365 Global Administrator or Exchange Administrator privileges and have your detailed import report ready before attempting to resolve service-side issues.

Solution 1Recommended

Contact Microsoft Support for Service-Side Resolution

Since the error points to a backend failure loading the Azure.Core assembly, you must create a service request for Microsoft engineers to unblock the quarantined job.

The error message specifically indicates that the remote import service failed to load a required assembly. Because this represents a service-side failure within Microsoft's infrastructure rather than a user configuration error, additional backend tools and permissions are needed to investigate and clear the quarantine status.

1
Log in to the Admin Center

Navigate to the Microsoft 365 admin center at https://admin.microsoft.com and sign in with your administrator credentials.

2
Navigate to Support

Locate and select 'Support' from the left-hand navigation menu, then click on 'New service request'.

3
Search for the Issue

In the search bar, type a brief description of the issue, such as 'PST import job stuck at 68 percent and quarantined'.

4
Open a Support Ticket

Choose the 'Contact Support' option to open a direct ticket with Microsoft support engineers, providing them with the specifics of the Azure.Core error.

Contact Microsoft Support for Service-Side Resolution
Keep Your Import Report Handy: Attach the detailed import report to your support ticket. Specifically highlight the Azure.Core assembly manifest mismatch error to help the support engineer diagnose the problem faster.
Free Microsoft Office alternative

Looking for a Lightweight Alternative to Microsoft Office?

While you wait for Microsoft Support to resolve complex server-side email migration issues, keep your daily productivity flowing with WPS Office. It provides a familiar interface, powerful offline capabilities, and seamless document compatibility without requiring complicated cloud management.

  1. 1. Download the Software: Visit the official WPS Office website to download the latest free version for your operating system.
  2. 2. Install WPS Office: Run the downloaded installer and follow the simple on-screen instructions to complete the setup in minutes.
  3. 3. Open Your Documents: Double-click your existing Word, Excel, or PowerPoint files to open them directly in WPS Office with formatting perfectly preserved.
Maintain local productivity while Microsoft resolves remote server PST import issuesFully compatible with Microsoft Office file formats, including .docx, .xlsx, and .pptxLightweight architecture ensures fast installation and smooth operation on any deviceCompletely free to use for essential office tasks with a familiar user interface
microsoft office alternative - wps office

Frequently Asked Questions

Why does a Microsoft 365 PST import job get quarantined?

A PST import job is quarantined to protect the system when the remote import service encounters a fatal service-side error. In this specific scenario, it occurs because required backend components, like the Azure.Core assembly, fail to load properly.

Can I manually resume a PST import job stuck at 68 percent?

If the job is stuck due to a backend assembly error and flagged as quarantined, you generally cannot resume it manually. Microsoft Support must investigate the backend failure and release the job from quarantine.

Where do I find the import report detailing the Azure.Core error?

You can view the specific error details by navigating to the Data Lifecycle Management section in the Microsoft Purview compliance portal, selecting your import job, and downloading the associated status or failure report.