Email Migration

Fix Microsoft Purview PST Import Stuck at 61 Percent During Analysis

Kushani NimanthikaKushani Nimanthika Oct 21, 2026 870 views

Question details

A Microsoft Purview PST import batch hangs at 61 percent progress during the analysis phase.

Fix Microsoft Purview PST Import Stuck at 61 Percent During Analysis
Product
Microsoft Purview
Device & OS
not provided
Scenario
Migrating email data using PST import batches in Microsoft Purview.
Observed behavior
The PST import batch process gets permanently stuck at 61 percent completion during the analysis stage, regardless of the batch size, even after clearing the browser cache.
Before you start

Ensure you have allowed sufficient time for Azure background processing to attempt an auto-recovery before manually canceling the import job.

Solution 1Recommended

Verify Import Details and Split the PST Batch

Check the exact point of failure in the mailbox details and reduce the PST batch size to bypass Azure processing bottlenecks.

Because the Microsoft Purview PST import process relies on background processing in Azure, large batches or specific corrupted items can sometimes cause the analysis phase to timeout or hang. Splitting the files mitigates this server-side issue.

1
View import details

Navigate to the Purview compliance portal, select your import job, and click 'View Details' to check the specific import status and identify any file errors.

2
Verify mailbox data

Sign in to the destination mailbox to check if any portion of the PST file has already been imported successfully before the freeze occurred.

3
Split PST files

If the batch is hopelessly stuck, cancel the current import job and split your large PST files into smaller, manageable groups for separate analysis.

4
Restart the analysis

Upload the newly separated PST batches and restart the analysis process for each one individually.

Verify Import Details and Split the PST Batch
Azure Backend Delays: Since processing occurs in the background on Azure servers, canceling and restarting can sometimes take time. Review Microsoft support guidance if the new smaller batches still experience delays.
Free Microsoft Office alternative

Looking for a Reliable Office Suite? Try WPS Office

While resolving Microsoft Purview and Azure backend migration issues can be time-consuming, managing your daily documents doesn't have to be. WPS Office is a free, lightweight, and user-friendly alternative to Microsoft Office that ensures seamless workflow and high compatibility without heavy resource usage.

  1. 1. Download WPS Office: Visit the official WPS website and click the free download button.
  2. 2. Install the application: Run the lightweight installer and follow the straightforward on-screen prompts.
  3. 3. Open your files: Launch WPS Office to immediately start working on your existing Word, Excel, and PowerPoint documents.
Seamlessly opens and edits Microsoft Office formats (DOCX, XLSX, PPTX) without compatibility issues.Lightweight application that avoids heavy background processes and installs quickly.Familiar tabbed interface makes migrating from Microsoft Office completely effortless.Includes a powerful built-in PDF toolkit and cloud collaboration features for free.
QA img-9

Frequently Asked Questions

Why does the Microsoft Purview PST import get stuck exactly at 61 percent?

The 61 percent mark typically represents a specific transition phase in Azure where the analysis of PST file items is queued or indexed. Delays at this exact percentage are often due to server-side backend processing bottlenecks or corrupted items within the batch.

Can I just restart the PST import process immediately after it hangs?

Since the processing occurs in the background on Azure, immediate restarts can be tricky and may fail to initialize properly. It is recommended to check 'View Details' first, wait for any background tasks to time out, and then attempt a restart.

How small should I make my PST batches to prevent the analysis from freezing?

While there is no strict rule, breaking large PST files down into smaller batches of 2 GB to 5 GB can significantly reduce processing errors and prevent the analysis from hanging during the Azure ingestion process.