Share via

Purview PST Import stuck at 0%, Analysis Completed but Import never starts – No Cancel/Stop options available

Conqueror 10 Reputation points
2025-12-01T20:27:35.7233333+00:00

Hello,

We are experiencing an issue with PST Import (Network Upload) in Microsoft Purview. Several import jobs have been stuck at “Import in progress” at 0% for the last 5 days.

The jobs show Analysis Completed, but the import phase never starts. Additionally, for these jobs the Cancel / Stop / Delete buttons do not appear in the Purview portal, making the jobs impossible to manage (stuck/zombie state).

Details:

Purview path: Data Lifecycle Management → Import

Job status: Import in progress (0%)

Status Detail: 0 (no errors)

Analysis Status: Completed

Import phase has not moved for 5 days

I created a new SAS key and verified permissions (SAS is valid) -The weekly sas period is over, I recreated it.

PST files are fully uploaded to Azure Storage

CSV mapping file validated successfully

However, the jobs do not allow any management actions (no Cancel/Stop/Delete options)

This appears to be a backend queue or pipeline issue on the Purview side.

We kindly request assistance to clean up or restart the stuck jobs or apply a tenant-level fix.

I can provide the job IDs if needed.

Thank you.

Microsoft Security | Microsoft Purview
0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Q&A Assist
    2025-12-01T20:27:55.94+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    It seems that you are experiencing a common issue with PST import jobs in Microsoft Purview where the import phase gets stuck at 0% despite the analysis being completed. Here are a few points to consider:

    1. Job Management Options: If the Cancel/Stop/Delete options are not available, it may indicate that the job is in a state that prevents management actions. This can happen if the job is stuck in a backend queue or if there are transient issues with the service.
    2. Ingestion Rate: The ingestion rate for PST files is approximately 24 GB per day, but this is not guaranteed. If your PST files are large or if there are multiple files being imported into the same mailbox, it could affect the import process.
    3. Common Resolutions: Although you mentioned that the CSV mapping file has been validated and the PST files are uploaded, you might want to check the following:
      • Ensure that the PST files do not exceed the recommended size of 20 GB, as larger files can lead to delays.
      • If multiple PST files are being imported into the same mailbox, consider importing them sequentially into different mailboxes to improve performance.
    4. Contact Support: Since the jobs appear to be in a zombie state and you are unable to manage them, it may be best to contact Microsoft support for assistance. They can help clean up or restart the stuck jobs and apply any necessary tenant-level fixes.

    If you have job IDs available, providing them to support can expedite the troubleshooting process.

    References:

    0 comments
  2. Marexila 0 Reputation points
    2025-12-02T07:09:13.7566667+00:00

    Hello, I’m experiencing the same issue.

    All PST Import (Network Upload) jobs I started in Microsoft Purview are stuck at 0% and remain in “Analysis in progress”. Some of these jobs have been stuck since 29 November. Additionally, I do not have any management options available in the Purview portal — the Cancel / Stop / Delete buttons are missing — so I can’t cancel or remove the stuck jobs.image

  3. VRISHABHANATH PATIL 2,070 Reputation points Microsoft External Staff Moderator
    2025-12-03T07:09:09.1433333+00:00

    Hi @Conqueror **
    **
    Thank you for contacting to Microsoft QA.

    It sounds like you're running into some frustrating issues with the PST import in Microsoft Purview. When jobs get stuck at 0% and you don't have options to cancel or delete them, it can be really tricky to manage. Here are a few steps and considerations that might help:

    Troubleshooting Steps:

    Check the Size of PST Files: Ensure that the PST files you're trying to import are under 20 GB. Larger files can cause delays. If they exceed this recommendation, consider splitting them into smaller files.

    Integration Runtime: Since you're using Microsoft Purview, confirm that your integration runtime is correctly set up and functioning. You can verify this in the Management Center of Purview. If it's not configured properly, it could lead to issues with the import process.

    Log Review: Look for any backend errors or logs that can provide more information about why the import is stalled. Sometimes, errors can be silent or not visible in the UI.

    Reload Jobs: While it sounds like you've already investigated the job statuses, sometimes, reloading the jobs by signing out and back into the Purview portal can help to refresh the interface and potentially reveal actions that weren’t previously visible.

    Corrupted Items: If you suspect corrupt items within the PST, you might want to run Scanpst.exe to repair them. Then, re-upload the corrected PST files and create a new import job.

    Azure Support: If none of the above solutions work, it may be a deeper backend issue. In this case, having the job IDs will be crucial when reaching out to Azure Support to escalate the problem for a fix.

    Follow-Up Questions:

    To better assist you, here are some follow-up questions you might want to consider:

    • Can you confirm the sizes of the PST files you're importing?
    • Have you verified that the integration runtime is set up correctly in your Purview management settings?
    • What specific permissions do the users running this import job have?
    • Are there any logs or error messages you can check for more insight into this issue?

    Reference Documentation:

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.