Microsoft Revamps Purview Retention Policies for Copilot

Interactions and Memories Processed by Separate Copilot Retention Policies

If your Microsoft 365 tenant uses Copilot, two important changes are coming to Purview retention policies in late October 2026. The first is described in message center notification MC1481313 (28 September 2026), which says that Microsoft is removing Copilot interactions from Teams retention policies. After introducing Copilot, Microsoft needed a method to capture interactions (prompts and responses) in compliance records. A quick and pragmatic solution was to store the Copilot compliance records in the TeamsMessagesData hidden folder in user mailboxes and apply the retention policies created for Teams chats to Copilot interactions.

As long ago as November 2024, Microsoft announced their intentions to separate the two types of compliance record. Microsoft duly implemented the change, allowing Purview to create separate retention policies for Teams and Copilot data. However, some tenants continued to use older policies that processed both types of compliance record.

What’s happening now is that Microsoft is removing Copilot processing from those policies. In a nutshell, if you have some older retention policies that process both Teams and Copilot interactions, you need to create a new retention policy for Copilot “experiences” (Figure 1). The policy covers interactions captured for both free and paid-for Copilot clients.

Configuring a Purview retention policy for Copilot interactions.

Copilot retention policies.
Figure 1: Configuring a Purview retention policy for Copilot interactions

The rollout for this change starts in late October 2026 and is due to complete by mid-November 2026.

Copilot Themes Going Away

In passing, I note that MC1492954 (9 October 2026) announces the retirement of Copilot themes in Outlook. Each time Outlook generated a new custom theme (based on the weather or location, for instance), the Microsoft 365 substrate created a Copilot compliance record. Removing the feature should therefore reduce the number of interactions Purview must process.

Capturing Teams Memories

The second change is described in message center notification MC1478965 (24 September 2026, Microsoft 365 Roadmap 569612) which discusses the introduction of Purview data lifecycle management support for Microsoft 365 Copilot memory. I like Copilot memory because the feature (accessible through settings) allows me to personalize how Copilot responds to my prompts. Figure 2 shows some of my current settings.

Copilot memory settings for a user account
Figure 2: Copilot memory settings for a user account

Microsoft says that “Copilot memory includes saved memories, details inferred from chat history, and custom instructions that help provide personalized and context-aware Copilot experiences.” Information about Copilot memory settings is stored in a hidden folder in the user’s Exchange Online mailbox.

The change revealed in MC1478965 is the introduction of Purview retention policies to process. Although Microsoft hasn’t revealed details of how Copilot memory files work, I assume that the settings are held in a JSON-formatted file, much like the AI-generated Teams meeting archive files. Rollout is scheduled for late September 2026 and is expected to complete by mid-October 2026.

Microsoft says that “Compliance teams will be able to access historical versions of Copilot memory items to understand how content changed over time.” Access is through eDiscovery searches and exports, but it’s fair to ask what a compliance officer would expect to find in a memory settings file.

I guess it’s possible that some information about people who use Copilot for illegal or malicious purposes might be gleaned from the information held in Copilot memory. We’ll have to see.

Programmatic Access to TeamsMessagesData

Speaking of analysis of contents, in the past my usual first step to investigate anything in an Exchange Online mailbox was to use the MFCMAPI utility. MFCMAPI is still an incredibly useful tool for tenant administrators, but apparently not for poking around sensitive hidden folders.

Unhappily, Microsoft blocked Graph access to non-IPM folders earlier this year (in the name of greater security, naturally) and have now blocked MFCMAPI access to the TeamsMessagesData folder. At least, MFCMAPI can see that the folder exists, but it cannot open the contents table to view items in the folder. Details of Copilot interactions can still be fetched through the aiInteractionHistory Graph API, but that’s a lot more effort when all you want to do is confirm that an item exists, like checking how well retention policies work. Oh well…


The nice thing about generative AI tools is that they can generate information based on what’s gone before. The bad thing about generative AI tools is that they can’t create new thinking or insights about how technology works (or doesn’t). When we write the Microsoft 365 for IT Pros eBooks, we depend on hundreds of years of real-world experience, knowledge, and intuition to analyze and explain how Microsoft 365 really works. If you understand the basic principles about Entra ID, Exchange Online, SharePoint Online, Teams, the Microsoft Graph, and more, you’ll be able to figure out the value of new features as Microsoft adds them to the platform. All for less than ten cups of black coffee.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.