Fix Teams Retention Policy Does Not Delete Messages in a Private Channel

When a retention policy fails to delete messages in a private channel, the expected cleanup never happens and your organization may face compliance risks. This usually occurs because the policy targets the standard channel message location but misses the private channel message location. In this article, you will learn the exact cause, the step-by-step fix, and how to verify that deletion actually occurs.

Private channels store their messages separately from standard channels, so a single retention policy cannot cover both. The fix requires creating a second retention policy that explicitly targets the private channel message location. You will also see how to test the policy and what to do if deletion still does not happen.

Why Teams Retention Policy Misses Private Channel Messages

Teams private channels are separate containers within a team. Each private channel has its own SharePoint site, its own mailbox, and its own set of messages. The retention engine treats private channel messages as a distinct location. When you create a retention policy for Teams channel messages, that policy applies only to standard channels. Private channel messages are not included unless you explicitly select the private channel message location.

The Microsoft Purview compliance portal offers two separate locations for Teams messages. One is called Teams channel messages and the other is called Teams private channel messages. If you only select the first location, the policy will never touch private channel content. This is the most common reason why messages in a private channel remain after the retention period ends.

Another factor is the delay in policy application. Retention policies can take up to seven days to process content after you create them. If you recently created the policy, you may think it is broken when it simply has not run yet. Also, the retention engine only processes content that existed when the policy was created. Messages created after the policy starts will be processed normally, but older messages may need a catch-up run.

How Retention Works for Private Channels

Each private channel message is stored in a hidden mailbox that is not visible in the standard Teams data map. The retention policy must target that hidden mailbox. The Purview portal abstracts this by offering the private channel location. When you select that location, the policy applies to all private channels in your organization.

Retention policies can either delete content after a period or preserve it for a period. For deletion, you must set the retention period to a specific number of days and choose the action Delete items automatically. If you choose a preservation action only, nothing will be deleted.

Steps to Fix Retention Policy Deletion in Private Channels

1. Open Microsoft Purview compliance portal
   Go to compliance.microsoft.com and sign in with an account that has the Compliance Administrator or Retention Management role. In the left navigation, select Data lifecycle management and then Retention policies.
2. Check existing policies for the private channel location
   Click on your existing Teams retention policy and review the Locations section. Confirm whether Teams private channel messages is listed. If it is not, you must create a new policy because you cannot add a location to an existing policy after it is saved.
3. Create a new retention policy for private channels
   Click New retention policy. Give the policy a clear name such as Private Channel Deletion – 30 Days. In the Locations step, expand Teams private channel messages and select the checkbox next to it. Do not select the standard Teams channel messages location here because you want to keep the policies separate.
4. Configure the retention period and action
   In the Retention settings step, choose Retain items for a specific period. Set the number of days to match your compliance requirement, for example 30 days. Under At the end of the retention period, select Delete items automatically. Click Next and then Submit.
5. Verify the policy with PowerShell
   Open Exchange Online PowerShell and run Get-RetentionCompliancePolicy -Identity "Private Channel Deletion – 30 Days" | Format-List. Check that the output includes TeamsPrivateChannelMessages in the EnabledLocations property. If it does not, the policy was not applied to private channels.
6. Wait for the policy to process
   Retention policies can take up to seven days to process existing content. New messages are usually processed within 24 hours. Do not expect immediate deletion right after creating the policy.
7. Test with a sample message
   Send a test message in a private channel. Wait at least 24 hours and then check if the message disappears after the retention period. If you set a 30-day period, you will need to wait 30 days for the test to complete. For faster testing, create a policy with a 1-day period and send a message, then wait 24 hours.

If Private Channel Messages Still Are Not Deleted

Teams Retention Policy Does Not Delete Messages in a Private Channel After 7 Days

If you waited more than seven days and deletion still has not occurred, check whether the policy is actually applied to the private channel location. Open the policy in the Purview portal and look at the Locations tab. If it shows Teams private channel messages with a status of On, the policy is active. If the status is Off or Pending, the policy may not have been fully applied. Edit the policy and re-select the location, then save it.

Also verify that the retention period is set to delete. A common mistake is to select Preserve items instead of Delete items automatically. If the policy preserves, nothing will ever be deleted.

Private Channel Messages Are Deleted But Not the Files in the Channel

Private channel files are stored in a separate SharePoint site. The Teams private channel message location does not cover files. To delete files, you must create a retention policy that includes the SharePoint site associated with the private channel. Each private channel has its own site URL. You can find it by going to the channel and clicking Files, then copying the URL. Add that URL to a SharePoint retention policy.

Retention Policy Works for Standard Channels But Not for Private Channels

This confirms that your standard channel policy is correct but the private channel location is missing. Follow the steps above to create a separate policy. Do not try to force the standard policy to cover private channels because the system does not allow that.

PowerShell Shows No Private Channel Location in the Policy

If Get-RetentionCompliancePolicy does not list TeamsPrivateChannelMessages, the policy was created without that location. This can happen if you used an older version of the compliance portal or if you selected only the standard channel location. Create a new policy and explicitly select the private channel location in the wizard.

Retention Policy for Standard Channels vs Private Channels: Key Differences

Item	Standard Channel Messages	Private Channel Messages
Location name in Purview	Teams channel messages	Teams private channel messages
Storage backend	Shared team mailbox	Hidden private channel mailbox
Files storage	Team SharePoint site	Separate private channel SharePoint site
Default coverage by a single policy	Yes	No – requires a separate policy
Deletion action	Delete items automatically	Delete items automatically

The table shows that the only way to delete private channel messages is to create a policy that explicitly targets the private channel location. A single policy cannot cover both types of messages, even if you select both locations in the same policy. The Purview wizard allows you to select both, but you must remember to check the private channel box.

You now know why private channel messages are not deleted and how to fix it. Create a separate retention policy that targets the private channel message location and set the deletion action. Verify the policy with PowerShell and wait up to seven days for processing. For files in private channels, add the associated SharePoint site to a separate policy. Use the Retention policy wizard in the Purview portal to manage both locations correctly.