Understanding Copilot Personalization and Memory

🚀 Overview

Microsoft has introduced Copilot personalization and memory, currently in preview as part of the Frontier program. This feature allows the AI to develop a longitudinal understanding of a user’s preferences, specific workflows, and past interactions to provide more tailored and relevant responses. Unlike standard LLM interactions that treat every session as a “blank slate,” memory enables Copilot to recall specific user-provided instructions and inferred context from previous chat histories. For IT Administrators, understanding the storage, governance, and management of this data is critical for maintaining organizational compliance.

This functionality is not locked behind premium tiers; it is available to users utilizing Copilot Chat regardless of whether they hold a specific Microsoft 365 Copilot license. By default, these features are enabled to enhance the user experience, but they offer granular controls for both the tenant administrator and the individual end-user.

⚙️ Key Technical Details

Administration and Configuration

• Enhanced Personalization Control: This is the primary toggle for managing memory. It is enabled by default. If an administrator disables this at the tenant level, users will see personalization settings (Custom instructions, Saved memories, and Chat history) grayed out in their interface.
• Programmatic Management: For large-scale environments, admins can utilize the Microsoft Graph API to configure the enhancedPersonalizationSetting resource type via custom scripts.
• User-Level Autonomy: Even if enabled by the admin, users can independently toggle their specific memory settings within Settings > Personalization in the Copilot interface.

🛡️ Storage Architecture and Security

• Mailbox Integration: All “memories”—including explicit user instructions and inferred details—are stored directly within the user’s Exchange Online mailbox.
• Hidden Folder Structure: The data resides in a hidden folder within the mailbox. Specifically, these items are stored under the IPM.Contact item class in a folder labeled 'CopilotMemory'.
• Security Parity: Because the data is stored in the mailbox, it inherits the organization’s existing security posture. This includes encryption at rest and support for Customer Lockbox requests.

📅 Data Types and Retention Behavior

The lifecycle of Copilot memory varies based on the type of information stored:

• Custom Instructions: These are user-defined rules on how Copilot should behave. They remain indefinitely until the user manually removes them. Turning off personalization stops Copilot from using them but does not delete them.
• Saved Memories: Specific facts the user has asked Copilot to remember. These persist until the user explicitly deletes them. Deleting the chat session where the memory originated does not remove the saved memory itself.
• Chat History (Inferred): This is dynamic data. Copilot periodically updates or prunes these details based on utility. If a user deletes the source chat, the inferred memory is purged within 7 days. If the personalization feature is disabled by an admin, all chat history-based details are deleted after 30 days.
• Retention Policy Limitation: Standard Microsoft Purview retention labels or “delete after X days” policies do not currently apply to Copilot memory. There are currently no administrative controls to enforce specific retention periods for these mailbox-stored memories.

⚖️ Compliance and eDiscovery

• eDiscovery Support: Admins can use Microsoft Purview eDiscovery or Content Search to locate memory data. You must search for the IPM.Contact item class to find these records.
• Data Subject Requests (DSR): Admins can export and delete memory data via Microsoft Graph Explorer in conjunction with Purview tools to satisfy privacy requirements.
• Visibility: While saved memories and inferred history are discoverable via eDiscovery, Custom Instructions are currently not visible to admins through these tools and must be managed or exported by the user.
• Auditing: At this stage, personalization and memory management actions do not generate entries in the Purview audit logs.

⚠️ Impact

For Administrators: The primary impact is the shift in data residency. Since memory lives in the user’s mailbox, it simplifies the security model but complicates retention strategies. Admins must be aware that clearing chat history does not necessarily clear the “learned” persona of the AI unless specific memory folders are targeted or the personalization feature is disabled. Furthermore, temporary chats are still discoverable within Purview, ensuring that “off-the-record” sessions still meet corporate compliance standards.

For Users: Personalization significantly reduces prompt engineering overhead. Copilot can remember a user’s preferred tone, formatting requirements, or project contexts across different sessions. However, users maintain the burden of data hygiene for their “Saved Memories,” as these must be manually curated to remain accurate over time.

---

Read the full article on Microsoft.com