Compliance Problems

Fix a Duplicate Compliance Rule Error in Microsoft Purview Retention Policies

Huma Ashraf ChHuma Ashraf Ch Nov 14, 2026 869 views

Question details

Resolve a duplicate compliance rule error when creating a retention policy in Microsoft Purview.

Fix a Duplicate Compliance Rule Error in Microsoft Purview Retention Policies
Product
Microsoft Purview
Device & OS
not provided
Scenario
An administrator is creating a retention policy but cannot find an object with the conflicting name.
Observed behavior
Policy creation reports that a compliance rule with the specified name already exists, and the compliance API returns HTTP 500.
Before you start

Note the exact policy, rule, and label names in the error, and confirm that your account has the required Purview permissions. Install or update the ExchangeOnlineManagement PowerShell module if it is not available.

Solution 1Recommended

Check retention labels, policies, and rules for the conflicting name

Use Security & Compliance PowerShell to look for existing objects before retrying policy creation.

Retention labels, retention policies, and policy rules are different objects. A matching label may explain a label conflict, but removing one does not necessarily resolve a policy or rule conflict.

1
Connect to compliance PowerShell

Open PowerShell, run Connect-IPPSSession, and sign in with an account authorized to manage compliance objects.

2
List retention objects

Run Get-ComplianceTag | Format-List Name,Identity to inspect labels. Also run Get-RetentionCompliancePolicy | Format-List Name,Identity and Get-RetentionComplianceRule | Format-List Name,Identity to inspect policies and rules.

3
Investigate a matching object

Compare the results with the exact name in the error. If a label matches, check its purpose and dependencies in the Microsoft Purview portal before deciding whether it should be retained, renamed, or removed.

4
Retry the appropriate creation

Return to the retention policy creation workflow in the Microsoft Purview portal and retry. If you specifically need to create a retention label, you can use New-ComplianceTag -Name "LabelName" in the connected PowerShell session; this command creates a label, not a policy.

Do not remove an active label without review: Remove-ComplianceTag deletes a retention label and may be blocked or affect existing retention configurations. Review its use and applicable retention requirements before removing it.
Free Microsoft Office alternative

Work with Office Documents in WPS Office

WPS Office is a free, lightweight alternative with a familiar interface and support for common Microsoft Office formats, making it easy to move everyday document work. It does not manage or repair Microsoft Purview retention policies.

Open and edit Microsoft Word, Excel, and PowerPoint formatsUse a familiar interface for a smooth transition from Microsoft OfficeWork with documents referenced in retention workflowsUse a free, lightweight suite for everyday office tasks
microsoft office alternative - wps office

Frequently Asked Questions

How can I check whether a retention label already exists?

Connect with Connect-IPPSSession, then run Get-ComplianceTag | Format-List Name,Identity and compare the names with the one in the error.

Does New-ComplianceTag create a retention policy?

No. New-ComplianceTag creates a retention label. Create a retention policy through the appropriate Microsoft Purview portal workflow instead.

Should I delete a label with the conflicting name?

Not until you have reviewed its purpose, dependencies, and retention requirements. Remove-ComplianceTag deletes a label and may be blocked or affect existing configurations.

What should I send Microsoft support for the HTTP 500 error?

Include the exact error, time, tenant information, object name, and any request or correlation ID. A reviewed browser Network log of the failing request may also help.