Fix Error 500 When Publishing a Microsoft Purview Retention Label
Question details
The user needs to publish and open a Microsoft Purview retention label policy without receiving a server error.

- Product
- Microsoft Purview
- Device & OS
- not provided
- Scenario
- Publishing a retention label policy for Microsoft 365 locations.
- Observed behavior
- The RetentionCompliance API returns status code 500. The policy appears after refreshing, but opening it produces the same error. A different browser and private browsing did not resolve the issue.
Note the affected policy name, the time of the error, and the locations selected for the policy. Check the policy list before retrying, because the failed publishing attempt may have created an entry.
Check Microsoft Purview permissions and test another administrator account
Use this approach to rule out an account or role assignment issue before creating another policy.
In the Microsoft Purview portal, open Settings > Roles and scopes > Role groups and check that your account has the roles required to manage retention labels and policies.
Review Microsoft's documentation for retention management permissions and ask an administrator to correct any missing role assignment.
Sign in to the Microsoft Purview portal with another authorized administrator account, such as a global administrator with the required Purview access, and try opening the existing policy.

Test publishing with specific Microsoft 365 locations
Use a limited-scope test to determine whether the error is associated with a selected policy location.
Collect error details and contact Microsoft support
Escalate the issue if an authorized account and a limited-scope test still produce error 500.
Work with Office Documents in WPS Office
WPS Office is a free, lightweight alternative with a familiar interface for working with Microsoft Office documents. Its format compatibility helps you move existing files into your workflow. It does not manage Microsoft Purview retention policies or fix Purview service errors.

Frequently Asked Questions
Why does the policy appear even though publishing returned error 500?
The request may have created a policy entry before the error occurred. Check Data lifecycle management > Retention label policies before retrying to avoid creating a duplicate.
Which permissions should I check for retention label publishing?
In the Microsoft Purview portal, check Settings > Roles and scopes > Role groups. Compare the account's assigned roles with Microsoft's current retention management permissions documentation.
What if a different browser and private mode do not help?
Test with another authorized administrator account and, if permitted, a limited-scope policy. If the error continues, collect the exact error and contact Microsoft support through the Microsoft 365 admin center.
Can WPS Office fix the Purview retention policy error?
No. Microsoft Purview retention policies are managed in Microsoft 365, so the error must be investigated there. WPS Office can be used separately to work with compatible Office documents.




