If you set a Teams retention policy to delete chat messages after a certain period, but messages from a recorded meeting remain in the chat history, the policy may not be applying correctly. This happens because recorded meetings generate transcript and recording files that are governed by separate retention settings. This article explains the technical reasons why the policy fails and provides step-by-step fixes to ensure messages are deleted as expected.
You will learn how to check your retention policy configuration, verify the policy assignment, and use PowerShell to force a cleanup. We also cover related failure patterns, such as messages lingering in channel chats or after a meeting owner leaves the organization.
Key Takeaways: Fixing Retention Policy for Recorded Meeting Messages
- Teams admin center > Retention policies: Confirm the policy applies to Teams channel messages and chats, not just files.
- Microsoft 365 compliance portal > Data lifecycle management: Check that the retention policy includes Teams collaboration content and has the correct deletion action.
- PowerShell Get-RetentionCompliancePolicy: Verify the policy scope and use Start-ManagedFolderAssistant to trigger immediate processing.
Why Retention Policy Does Not Delete Messages in a Recorded Meeting
Teams retention policies are designed to delete chat messages, channel messages, and files after a specified period. However, when a meeting is recorded, the meeting becomes a separate entity in the chat history. The recording and transcript are stored as files in the meeting chat, and these files may be subject to different retention rules than the text messages. As a result, the retention policy may delete the text messages but leave the recording file, which then appears as if the messages were not deleted.
Another common cause is that the retention policy is configured to apply only to Exchange mailboxes or SharePoint sites, not to Teams messages. The policy must explicitly include Teams channel messages and chats. If the policy is set to retain content for a period that is longer than the meeting recording retention, the messages may be retained longer than intended.
Additionally, the retention policy may not have been assigned to the correct user or group. If the meeting organizer is not included in the policy scope, the messages from that meeting will not be deleted. Finally, the retention process is not instantaneous. Teams checks for expired content periodically, and it may take up to 7 days for the deletion to occur.
Understanding the Role of Meeting Recordings
When you record a Teams meeting, the recording is saved to OneDrive or SharePoint and linked in the meeting chat. The chat messages themselves are stored in Exchange Online. The retention policy for Teams messages applies to the chat messages, but the recording file is a separate item. If the recording file has a different retention label or policy, it may remain after the chat messages are deleted, making it look like the policy failed.
Checking the Policy Scope
Before troubleshooting, verify that the retention policy includes Teams collaboration content. In the Microsoft 365 compliance portal, go to Data lifecycle management > Retention policies. Open your policy and confirm that the locations include Teams channel messages and Teams chats. If not, edit the policy to add these locations.
Steps to Diagnose and Fix the Retention Policy for Recorded Meeting Messages
Follow these steps to identify why the retention policy is not deleting messages and to apply the correct fix.
- Check the retention policy configuration
Sign in to the Microsoft 365 compliance portal at compliance.microsoft.com. Go to Data lifecycle management > Retention policies. Open the policy that should delete the messages. Ensure the Locations list includes Teams channel messages and Teams chats. If not, click Edit and add those locations. - Verify the retention period and action
In the same policy, check the retention period. If the period is set to 30 days, for example, messages older than 30 days should be deleted. Confirm that the action is set to Delete the content. If the action is Set to retain, change it to Delete. - Check the policy assignment
Go to the policy assignment tab. Verify that the user who organized the recorded meeting is included in the assigned users or groups. If not, add the user or group and save the policy. - Use PowerShell to verify the policy scope
Open PowerShell and connect to Exchange Online using Connect-ExchangeOnline. Run Get-RetentionCompliancePolicy -Identity “Your Policy Name” | Format-List. Check the Enabled and Mode properties. Ensure the policy is enabled and in Enforcement mode. - Trigger the retention process manually
Run Start-ManagedFolderAssistant -Identity “user@domain.com” in PowerShell to force the retention assistant to process the user’s mailbox. This can speed up the deletion of expired messages. - Wait for the deletion to complete
After running the assistant, wait up to 24 hours. Check the meeting chat again. If the messages are still present, review the policy again for any typos in the retention period or location selection.
If Teams Still Has Issues After the Main Fix
Sometimes the retention policy still does not delete messages even after following the steps above. Here are additional failure patterns and their solutions.
Messages in a Channel Chat Are Not Deleted
Channel messages are stored in the SharePoint site associated with the team. The retention policy must include SharePoint sites as a location. If the policy only includes Teams chats, channel messages will not be deleted. Edit the policy to add the SharePoint sites location and select the specific site for the team.
Recording File Remains After Messages Are Deleted
If the text messages are deleted but the recording file remains, the recording is governed by a separate retention label. Check if a retention label is applied to the recording file in OneDrive or SharePoint. If so, remove the label or adjust its retention period to match your needs.
Meeting Organizer Left the Organization
If the meeting organizer has left the organization, their mailbox may be in an inactive state. Retention policies can still apply, but the deletion may be delayed. Contact your Microsoft 365 administrator to ensure the inactive mailbox is included in the policy scope.
New Teams Desktop vs Teams on the Web: Retention Policy Behavior
| Item | New Teams Desktop | Teams on the Web |
|---|---|---|
| Retention policy application | Applies automatically to chat and channel messages | Applies automatically to chat and channel messages |
| Visibility of deleted messages | Deleted messages disappear after refresh | Deleted messages disappear after refresh |
| Recording file retention | Follows file retention label in OneDrive or SharePoint | Same as desktop |
| Admin override options | Available via compliance portal | Same as desktop |
Both clients behave the same because retention policy is server-side. The client only displays what is stored.
After applying the fixes, you can now verify that the retention policy deletes messages from recorded meetings. Check the compliance portal to confirm the policy is active and use PowerShell to trigger immediate processing. For advanced control, apply a retention label to meeting recordings so they expire at the same time as the chat messages.