Microsoft 365 Error Codes

How to Fix HTTP 500 Error on Microsoft Purview PST Import

Elise Williams Oct 21, 2026 868 views

Question details

The user needs to resolve an HTTP 500 internal server error encountered when attempting to access the Import tab in Microsoft Purview Data Lifecycle Management.

How to Fix an HTTP 500 Error on the Microsoft Purview PST Import Tab

Product: Microsoft Purview
Device & OS: not provided
Scenario: Attempting to import PST files into Microsoft 365 using the Data Lifecycle Management Import tab.
Observed behavior: The Import tab returns an HTTP 500 error, blocking the interface and preventing the PST import process from continuing.

Before you start

Log in to the Microsoft 365 Admin Center and review the Service Health dashboard to ensure there are no ongoing service incidents affecting Microsoft Purview or Exchange Online.

Solution 1Recommended

Verify Administrator Permissions and Exchange Roles

Ensure the executing account has the exact required permissions to perform PST imports across Microsoft 365.

Even Global Administrators must have specific Exchange roles explicitly assigned to perform PST imports without encountering server errors.

Check Compliance Administrator Role

Log in to the Microsoft 365 admin center as a Global Administrator, navigate to 'Role assignments', and confirm your account holds the 'Compliance Data Administrator' role.

Access Exchange Admin Center

Go to the Exchange Admin Center (EAC) and navigate to 'Roles' followed by 'Admin roles' in the left menu.

Assign Mailbox Import Export Role

Verify that the 'Mailbox Import Export' role is actively enabled and assigned to the appropriate Exchange role group containing your admin account.

Verify Administrator Permissions and Exchange Roles

Permission Propagation Time: After assigning new roles, allow up to 24 hours for the permission changes to propagate across all Microsoft 365 services before trying the import again.

Solution 2

Test with an Alternate Global Administrator Account

Rule out account-specific profile corruption or browser caching issues by using another admin account.

Solution 3

Open a Backend Support Request

Escalate the issue to Microsoft Engineers to investigate ingestion-service backend failures.

Free Microsoft Office alternative

Keep Your Workflow Moving with WPS Office

While cloud-based errors like the Microsoft Purview HTTP 500 issue require backend support to fix, your daily local productivity shouldn't be compromised. WPS Office provides a powerful, free alternative to Microsoft Office, ensuring you can continue editing and managing your documents without unexpected cloud interruptions.

Fully compatible with Microsoft Word, Excel, and PowerPoint file formats.Lightweight application that works reliably without heavy cloud dependencies.Free to use for your everyday document editing and management needs.Familiar user interface ensuring seamless and quick migration.

microsoft office alternative - wps office

Frequently Asked Questions

What causes an HTTP 500 error on the Microsoft Purview Import tab?

An HTTP 500 internal server error in Purview is typically caused by insufficient administrative permissions, unassigned Mailbox Import Export roles in Exchange, or a backend ingestion-service outage.

Do I explicitly need the Mailbox Import Export role for PST imports?

Yes. Even if your account is a Global Administrator, the specific Exchange 'Mailbox Import Export' role must be actively assigned to perform PST imports without encountering access or server errors.

Why can't public forum engineers resolve my backend ingestion error?

Public forum support staff have limited access to specific tenant data due to strict data security and compliance requirements. Only the backend technical support team can collect and review the detailed diagnostic logs needed to fix ingestion-service issues.

Microsoft Office Error Codes